Question 600
After an incident where a MySQL migration can load initial rows but replication fails because the selected source requires encrypted connections, which recurring control would best prevent the same defect?
Explanation
Correct Answer
Test source TLS requirements for both initial copy and CDC sessions. The recurring risk is the migration connection lacks the appropriate trusted TLS settings or certificate chain. This check makes that risk visible before another incident.
Incorrect Answers
This control would use offline dumps only when the agreed downtime and write-freeze window permit them; it responds to the risk in which 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. It would not address the current root cause: the migration connection lacks the appropriate trusted TLS settings or certificate chain.
The proposed check would use peak write windows to stress-test continuous migration capacity, helping with cases where a managed migration reports low steady-state lag but a nightly batch produces a huge backlog and threatens cutover. The recurring exposure described here is that the migration connection lacks the appropriate trusted TLS settings or certificate chain.
The failure in the question arises because the migration connection lacks the appropriate trusted TLS settings or certificate chain. A safeguard to verify identity and sequence state after every relational data load serves situations where an Oracle application's sequence-generated invoice IDs collide with target rows after importing data into PostgreSQL rather than this one.