1 / 5
Fill in: 'We ___ a down migration for every schema change so a bad release can always be reverted cleanly.'
-
-
-
-
We 'write a migration' — the standard, simple collocation for authoring a schema-change script. The other options are less idiomatic here.
2 / 5
Fill in: 'A migration without a tested rollback path can ___ a team stuck mid-incident with no safe way back.'
-
-
-
-
We say an untested rollback will 'leave' a team stuck — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every rollback script against a staging copy of production data before trusting it in an incident.'
-
-
-
-
We 'test a script' — the standard, simple collocation for validating it before relying on it. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a destructive migration behind a backward-compatible expand-and-contract sequence instead of one big change.'
-
-
-
-
We 'split' a migration — the standard collocation for breaking a risky change into safer, smaller steps. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ a rollback plan before running any migration against production, not after something goes wrong.'
-
-
-
-
We 'prepare a plan' — the standard, simple collocation for readying a procedure in advance. The other options are less idiomatic here.