Question 570
The following database problem was corrected: A PostgreSQL source continues running, but migration change capture stops after a source maintenance task. Which result demonstrates that the root cause was addressed?
Explanation
Correct Answer
The destination receives new committed changes and lag returns within limits. The result directly checks whether the remedy worked: Inspect supported PostgreSQL logical replication settings and resume from a valid state. The cause was the logical replication slot or WAL retention prerequisites changed during maintenance.
Incorrect Answers
The result would be meaningful for a problem where a database migration moves tables but dozens of stored procedures continue using source-engine functions. For this question, closure depends on confirming that the destination receives new committed changes and lag returns within limits.
Even if this observation were recorded, it would support a case where a MySQL migration can load initial rows but replication fails because the selected source requires encrypted connections. It would not verify that the destination receives new committed changes and lag returns within limits.
This finding belongs with a situation in which engineers choose a source database version for managed migration that is outside the service's supported compatibility range. The required acceptance finding here is that the destination receives new committed changes and lag returns within limits.