Database migrations are a critical and sometimes risky operation. Apply the migration, roll back the schema change, and seed the database are the precise collocations used in deployment runbooks, migration tools, and database engineering documentation. Build confidence in this vocabulary with these exercises.
0 / 5 completed
1 / 5
The CI pipeline is configured to automatically ___ when a new version is deployed.
Apply the migration is the standard database migration collocation used by tools like Flyway, Liquibase, Alembic, and Rails Active Record. 'Apply' specifically means executing migration changes against a database. 'Run' is also common but 'apply' is the idiomatic verb in migration tooling.
2 / 5
After discovering the index change caused query degradation, the DBA decided to ___ immediately.
Roll back the schema change is the professional database operations collocation. 'Roll back' is the standard term for restoring a previous database state — it mirrors the concept of a transaction rollback. 'Revert' is also used but 'roll back' is more common in database and deployment contexts.
3 / 5
The deployment automation is set to ___ as part of the release process.
Run the migration script is the standard engineering collocation for executing a database change script. 'Run' is the natural verb for scripts and commands in engineering contexts, used consistently in deployment runbooks and CI/CD configurations.
4 / 5
Before the staging environment was handed to QA, the team needed to ___ with representative test data.
Seed the database is the standard development and testing collocation for populating a database with initial data. 'Seed' is the universal term in web frameworks (Rails, Laravel, Django, Prisma) for this action. 'Populate' and 'load' are also used but 'seed' is the domain-specific standard.
5 / 5
After applying the migration to production, the team ran integration tests to ___ had completed successfully.
Validate the migration is the professional database operations collocation for systematically checking that a migration produced the expected schema and data state. 'Validate' implies a defined set of checks against expected outcomes — more rigorous than 'check' or 'confirm'.