Question 690
The following database problem was corrected: A migration runbook declares cutover safe whenever lag reaches zero but does not verify application writes are paused. Which result demonstrates that the root cause was addressed?
Explanation
Correct Answer
The target contains every committed source transaction through the agreed boundary. The result directly checks whether the remedy worked: Coordinate write freeze, capture final replication position, and check reconciliation before switching. The cause was new transactions can appear after the last lag sample and escape the declared cutover boundary.
Incorrect Answers
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 the target contains every committed source transaction through the agreed boundary.
Even if this observation were recorded, it would support a case where a full database snapshot reports equal row counts but several customer balances differ after migration. It would not verify that the target contains every committed source transaction through the agreed boundary.
This finding relates to a situation in which a migrated database meets throughput goals but foreign-key relationships fail because dependent rows were loaded in the wrong order. The current remediation must instead show that the target contains every committed source transaction through the agreed boundary.