Practice the key verb+noun collocations used when planning, testing, and executing database schema migrations in English.
0 / 5 completed
1 / 5
Fill in: 'We need to ___ the migration in staging before touching production.'
We 'test a migration' — 'test' is the standard collocation for verifying that a schema change behaves correctly in a safe environment. 'Run' is the execution step; 'validate' is also acceptable but implies checking output; 'check' is too informal.
2 / 5
Fill in: 'If the deployment fails, we have a script ready to ___ the schema change immediately.'
We 'roll back a schema change' — 'roll back' is the database-standard collocation for reverting a migration. 'Undo' is informal; 'revert' is more common in version control; 'reverse' is mathematical and not idiomatic in DB contexts.
3 / 5
Fill in: 'After applying the migration, we must ___ data integrity across all joined tables.'
We 'validate data integrity' — 'validate' is the precise collocation for systematically confirming that data meets defined constraints. 'Check' is informal; 'verify' is close but more manual; 'confirm' implies a yes/no answer, not a systematic process.
4 / 5
Fill in: 'The DBA will ___ the migration plan with the team before the maintenance window.'
We 'apply a migration plan' — 'apply' is the standard collocation for executing the steps of a structured plan against a database. 'Execute' is also common but more formal; 'run' is informal; 'follow a plan' describes the process, not the action of running it.
5 / 5
Fill in: 'We will ___ the cutover at 02:00 UTC to minimise user impact.'
We 'execute a cutover' — 'execute' is the professional collocation for performing the final switch from old to new system. 'Perform a cutover' is also used; 'do a cutover' is informal; 'make a cutover' is not a standard phrase.