Practise the standard verbs for rolling out and monitoring canary deployments.
0 / 5 completed
1 / 5
Fill in: 'We ___ a canary deployment to five percent of traffic first, rather than a release nobody's actually tested at small scale.'
We 'route traffic' — the standard, simple collocation for sending a small slice of requests to a canary release. The other options are less idiomatic here.
2 / 5
Fill in: 'Skipping the canary stage on a risky release can ___ every user hitting a bug nobody's actually caught on a small sample first.'
We say a skipped canary stage will 'leave' every user hitting an uncaught bug — the standard, natural collocation for the resulting blast radius. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ error-rate thresholds before promoting the canary, rather than a rollout nobody's actually gated on real metrics.'
We 'set thresholds' — the standard, simple collocation for defining pass criteria before widening a canary. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ canary metrics against the baseline before rolling out further, rather than a spike nobody's actually compared to normal.'
We 'compare metrics' — the standard, simple collocation for checking a canary's health against a known baseline. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ canary rollout progress on a live dashboard, rather than a percentage nobody's actually watching in real time.'
We 'monitor progress' — the standard, simple collocation for watching a canary deployment as it widens. The other options aren't idiomatic here.