Deployment decisions are communicated with precise technical language. These exercises focus on the collocations DevOps engineers and release managers use when planning canary releases, rollbacks, and feature gates.
0 / 5 completed
1 / 5
The team decided to ___ incrementally, starting with internal users only.
Roll out changes is the standard DevOps collocation for a staged, progressive deployment. 'Roll out' implies a controlled, phased release. 'Release' is broader; 'push' and 'send' are informal and do not convey the staged nature of the deployment.
2 / 5
Before a full release, the team will ___ to expose one percent of traffic to the new service version.
Run a canary is the standard deployment strategy collocation. A canary deployment is something you run — it is an active, time-limited process. 'Test' conflates the strategy with QA; 'launch' and 'do' are too informal for deployment documentation.
3 / 5
Once the canary shows healthy metrics, the pipeline will automatically ___ across all regions.
Promote to production is the canonical CI/CD collocation for advancing a build from a staging or canary state to the production environment. 'Promote' implies it passed validation gates. 'Push' and 'send' lack the validation connotation; 'move' implies manual intervention.
4 / 5
When the error rate spiked after the deployment, the on-call engineer had to ___ immediately.
Roll back a release is the standard incident response collocation in deployment engineering. 'Roll back' is the formal term in CI/CD systems and runbooks. 'Revert' is used for code, not deployments; 'undo' is too informal; 'cancel' implies stopping something in progress, not reversing it.
5 / 5
The team uses LaunchDarkly to ___ for specific user segments before a general release.
Gate a feature is the feature-flag collocation for conditionally controlling access to functionality. A feature flag gates a feature, allowing selective exposure. 'Hide' and 'block' imply permanent suppression; 'hold' lacks the conditional-release connotation.