Question 610
A database team reports a successful correction for this problem: A project copies a large SQL database using a single logical dump while the source remains very busy and export time exceeds its outage window. What evidence supports closing the incident?
Explanation
Correct Answer
The target reaches the cutover position without a prolonged writer shutdown. The observed state validates the proposed fix: Choose a supported managed or staged migration path with initial load plus change replication. It addresses this cause: A bulk offline dump is being used despite the availability requirement for incremental synchronization.
Incorrect Answers
That result would matter when a managed migration reports low steady-state lag but a nightly batch produces a huge backlog and threatens cutover. It does not establish that the target reaches the cutover position without a prolonged writer shutdown, which is the evidence needed here.
That result would matter when a migration connection fails after a source password rotation, while ordinary applications continue using new credentials. It does not establish that the target reaches the cutover position without a prolonged writer shutdown, which is the evidence needed here.
The result would be meaningful for a problem where a hospital plans to move a heavily used PostgreSQL database with five-minute downtime tolerance but has budgeted only one weekend export. For this question, closure depends on confirming that the target reaches the cutover position without a prolonged writer shutdown.