A records bureau must copy a large on-premises database to AWS and keep it in sync until cutover. Which migration approach pattern best fits that need?
Select an answer to reveal the explanation.
Short Explanation
Copy the books while the office is still open, keep updates flowing, then flip the sign at go-live. Database replication with ongoing sync is the migration pattern for that. Deleting first, printing everything, or guessing the data after killing the network are disasters waiting to happen.
Full Explanation
A common cloud migration approach for databases is to replicate data to AWS and maintain ongoing synchronization until cutover, which reduces downtime and data loss risk. Tools and patterns in the AWS migration portfolio support continuous replication for many database engines. Destroying the source before copying, relying on paper rescans, or disconnecting networks without a controlled transfer are not appropriate migration strategies.