Question 550
A database team wants evidence that it fixed this issue: A source database continues accepting writes faster than change replication can apply them and the cutover window never closes. Which result would verify success?
Explanation
Correct Answer
Lag declines to the cutover threshold within a planned interval. This is the intended effect of: Measure CDC backlog and tune supported transfer resources or reduce write volume ahead of cutover. The original defect was replication capacity was not sized to the sustained source change rate.
Incorrect Answers
That result would matter when an old billing database uses a locale-specific case-insensitive collation that is not identical on the new engine. It does not establish that lag declines to the cutover threshold within a planned interval, which is the evidence needed here.
That result would matter when a company's fallback procedure simply restarts the source after ten hours of new writes on the target. It does not establish that lag declines to the cutover threshold within a planned interval, which is the evidence needed here.
This finding relates to a situation in which developers keep changing table definitions during a production continuous migration and the target schema drifts from the source. The current remediation must instead show that lag declines to the cutover threshold within a planned interval.