Google Professional Cloud Database Engineer Question 211
Single answerGoogle Cloud PlatformYour company is planning to migrate a mission-critical on-premises transactional database to Google Cloud with minimal disruption to the business. The database is used 24/7 and cannot afford extended downtimes. Which strategy should you implement to achieve a near-zero downtime migration while ensuring data consistency?
- A
Use a lift-and-shift approach where the database is shut down, backed up, and restored in Google Cloud.
- B
Implement a two-phase migration strategy using Database Migration Service with continuous data replication.
- C
Perform a snapshot-based migration and apply the latest changes manually after the cutover.
- D
Migrate the database during a planned extended outage window to Google Cloud.
Show answer and explanation
Correct answer: B
Explanation
For a near-zero downtime migration, it is essential to maintain continuous data replication to synchronize changes between the source and target databases. Google Cloud's Database Migration Service supports this by replicating data in real-time, allowing a seamless cutover with minimal disruption to the business. The other options involve downtime or potential data loss and do not fulfill the requirement for a near-zero downtime migration.
- A. Incorrect.
A lift-and-shift approach requires shutting down the database, which causes significant downtime and is not suitable for near-zero downtime migrations.
- B. Correct.
Using Database Migration Service with continuous data replication allows real-time synchronization of changes, ensuring data consistency while minimizing downtime during the cutover.
- C. Incorrect.
Snapshot-based migration involves a significant time gap between the snapshot and the application of changes, which introduces potential data loss and is not ideal for near-zero downtime scenarios.
- D. Incorrect.
Migrating during an extended outage window causes downtime and does not meet the requirement for near-zero downtime.