Practise the standard verbs for preparing and triggering safe migration rollbacks.
0 / 5 completed
1 / 5
Fill in: 'We ___ a database migration rollback the moment the deploy fails a health check, rather than a schema nobody's actually reverted cleanly.'
We 'trigger a rollback' — the standard, simple collocation for reverting a failed migration. The other options are less idiomatic here.
2 / 5
Fill in: 'A migration without a tested rollback script can ___ the database stuck in a broken state nobody's actually able to revert quickly.'
We say a missing rollback script will 'leave' the database stuck — the standard, natural collocation for the resulting outage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a rollback script before every migration ships, rather than a revert nobody's actually written until it's urgent.'
We 'write a script' — the standard, simple collocation for preparing a rollback path ahead of a migration. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every rollback against a staging copy before running it in production, rather than a script nobody's actually tested for real.'
We 'test a rollback' — the standard, simple collocation for validating a revert script before it's needed live. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ every rollback in the incident log for the postmortem, rather than a revert nobody's actually documented afterward.'
We 'log a rollback' — the standard, simple collocation for recording a database revert for later review. The other options aren't idiomatic here.