Question 710
A database team repairs this problem: A migration dashboard turns green immediately after cutover, but user transactions soon accumulate errors from missing indexes. Which measured outcome validates the correction?
Explanation
Correct Answer
Postcutover transactions meet baseline targets and missing indexes are corrected. This distinguishes actual recovery from a merely healthy-looking console. The targeted correction was: Run representative production-like queries and observe latency and errors during a guarded stabilization window.
Incorrect Answers
Even if this observation were recorded, it would support a case where a parallel-run comparison flags mismatches because the same transaction is captured at different times in source and target snapshots. It would not verify that postcutover transactions meet baseline targets and missing indexes are corrected.
This finding relates to a situation in which a migration runbook declares cutover safe whenever lag reaches zero but does not verify application writes are paused. The current remediation must instead show that postcutover transactions meet baseline targets and missing indexes are corrected.
This finding relates to a situation in which a managed destination database is provisioned with less storage than the source's live tables and planned index overhead. The current remediation must instead show that postcutover transactions meet baseline targets and missing indexes are corrected.