Practise the standard verbs for running safe MySQL online schema changes.
0 / 5 completed
1 / 5
Fill in: 'We ___ an online schema change tool for altering a large table so the migration doesn't hold a blocking lock for the duration of the whole rewrite.'
We 'run' a migration tool — the standard, simple collocation for executing an online schema-change utility. The other options are less idiomatic here.
2 / 5
Fill in: 'Running a plain ALTER TABLE on a huge production table can ___ every write blocked for the entire duration of the underlying table rebuild.'
We say a blocking ALTER will 'leave' writes stalled — the standard, natural collocation for the resulting outage. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ replication lag during an online schema change closely, since the shadow table's triggers can slow writes enough to fall visibly behind.'
We 'monitor' lag — the standard collocation for ongoing observation of replication delay during a risky operation. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ the shadow table's row count against the original before the final cutover swap, so a silently dropped row isn't discovered only after the switch.'
We 'validate' a row count — the standard, simple collocation for confirming two datasets match before trusting a swap. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ an online schema change immediately if replication lag crosses a safe threshold, rather than letting the migration keep running unattended.'
We 'abort a migration' — the standard, established collocation for halting a risky operation on a failed guardrail. The other options aren't the recognised term here.