Zero-Downtime Migration Language: English Collocations
Zero-downtime migrations require precise engineering communication — from shifting traffic to rehearsing rollback procedures. This exercise focuses on the collocations professionals use in migration planning documents, architecture reviews, and incident briefings.
0 / 5 completed
1 / 5
The engineering team plans to ___ the database schema without taking the service offline.
Migrate the schema is the correct collocation in zero-downtime discussions — it implies a structured transition from one state to another. 'Alter' is a SQL keyword used at query level; 'update' and 'change' don't carry the process-oriented meaning that 'migrate' does.
2 / 5
We need to ___ traffic gradually to the new service to avoid impacting users.
Shift traffic is the natural collocation in zero-downtime migration language — it implies a deliberate, controlled movement of load. 'Route' is also valid in networking contexts; 'redirect' implies a forced change; 'move' is too informal.
3 / 5
The team will ___ a feature flag to control which users access the new database path.
Toggle a feature flag is the most precise collocation — it means switching the flag on or off, which is exactly how feature flags control traffic during migrations. 'Enable' only goes in one direction; 'use' and 'set' are too vague.
4 / 5
Before cutting over fully, we should ___ the rollback procedure with the on-call team.
Rehearse the rollback procedure is the professional collocation in migration planning — it implies running through the steps as a simulation before the real event. 'Practise' is close but informal; 'test' implies a technical validation; 'review' is reading, not doing.
5 / 5
We'll ___ both old and new schemas in parallel during the transition window.
Maintain both schemas in parallel is the precise collocation — it implies active upkeep and compatibility during the dual-write phase. 'Run' is also common but more operational; 'support' implies a help function; 'keep' is informal.