Practise the standard verbs for cutting over to a new database safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ writes to the new database only after replication has fully caught up with the old one.'
We 'cut over' writes — the standard, established collocation for the final switch to a new system. The other options aren't the recognised term here.
2 / 5
Fill in: 'We ___ both databases in sync during the transition window using dual writes or a replication stream.'
We 'keep' databases in sync — the standard, simple collocation for maintaining consistency between two systems. The other options are less idiomatic here.
3 / 5
Fill in: 'A cutover performed without a verified backup can ___ data loss if something goes wrong midway.'
We say a rushed cutover will 'risk' data loss — the standard, natural collocation for exposing a system to danger. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ a rollback plan before the cutover so we can revert instantly if the new database misbehaves.'
We 'prepare a plan' — the standard, simple collocation for readying a procedure in advance. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the old database read-only for a short window after cutover instead of deleting it immediately.'
We 'leave' something in a state — the standard, natural collocation for keeping the old system available as a safety net. The other options aren't idiomatic here.