Examkin

Soru

Zorluk: KolayDesigning Migration Plans and Data Transfer Strategies

An e-commerce enterprise is planning to migrate its on-premises relational database to Cloud SQL for MySQL with minimal operational downtime using GCP Database Migration Service (DMS). Place the following database migration steps in the correct chronological execution order from first to last.

  1. 1Provision the target Cloud SQL instance and apply the database schema definitions.
  2. 2Configure continuous Change Data Capture (CDC) replication job parameters in Database Migration Service.
  3. 3Execute the initial full baseline data snapshot migration from the source database to Cloud SQL.
  4. 4Stop application write traffic to the source database, verify zero CDC replication lag, and switch application endpoints to Cloud SQL.

Cevap

The correct execution order is: 1) Provision the target Cloud SQL instance and apply database schema definitions, 2) Configure continuous Change Data Capture (CDC) replication job parameters in Database Migration Service, 3) Execute the initial full baseline data snapshot migration from the source database to Cloud SQL, 4) Stop application write traffic to the source database, verify zero CDC replication lag, and switch application endpoints to Cloud SQL.
The correct sequence follows standard database migration best practices: first provision destination resources and schema, then establish CDC replication pipelines, perform the initial baseline bulk load, and finally pause write traffic to verify zero replication lag before switching application connection strings.

Adım Adım Çözüm

1
Prepare target environment
Destination Cloud SQL instance created with appropriate schema structures ready to accept data
Data cannot be streamed into a destination that has not been provisioned with matching target schemas.
2
Establish continuous replication framework
DMS connection profile and CDC replication pipeline configured
Setting up the CDC pipeline beforehand ensures change logging is tracking transaction logs during data transfer.
3
Transfer historical baseline data
Full data snapshot copied to Cloud SQL while ongoing changes accumulate in replication stream
A baseline copy of existing data is required before incremental changes can be applied to align the target with the source.
4
Promote destination and cut over application endpoints
Downtime window minimized and Cloud SQL becomes the active production database
Pausing source write traffic ensures no new transactions occur while verifying zero CDC lag before updating application connection strings.

Anahtar Kavram

Minimal-Downtime Database Migration Cutover Sequencing
Bu soruyu puanla

Konular

Designing Migration Plans and Data Transfer Strategies