Practise the standard verbs for splitting traffic safely with Istio.
0 / 5 completed
1 / 5
Fill in: 'We ___ a VirtualService rule to split traffic between two versions of a service during a canary rollout.'
We 'define a rule' — the standard, established Istio collocation for declaring routing behaviour. The other options aren't the recognised term here.
2 / 5
Fill in: 'A misconfigured weight split can ___ all live traffic to the untested new version by accident.'
We say a bad weight will 'route' all traffic wrongly — the standard, natural collocation for the resulting misdirection. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the traffic weight gradually from 5% to 100% as confidence in the new version grows.'
We 'shift weight' — the standard, established collocation for gradually changing a traffic split. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ error rates per subset closely during a split so a bad version gets caught before it takes full traffic.'
We 'monitor' rates — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ a DestinationRule alongside the VirtualService so Istio knows which pods belong to each subset.'
We 'configure a rule' — the standard collocation for setting up a routing resource. The other options aren't idiomatic here.