PCDE Migrate data solutions Practice Question
During a cutover from MySQL to Cloud SQL, the team must minimize downtime. Which THREE steps are essential for a successful cutover with minimal data loss?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Verify that DMS replication lag is zero.
Quiesce writes to stop changes, verify replication lag is zero to ensure all changes are applied, then promote the destination to make it writable. Updating connection strings and testing are also needed but the three essential steps for data integrity are quiescing, verifying lag, and promoting.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Verify that DMS replication lag is zero.
Why this is correct
Ensures all changes are replicated before promotion.
- ✓
Quiesce all write operations to the source database.
Why this is correct
Stops new changes from being generated.
- ✓
Promote the destination Cloud SQL instance.
Why this is correct
Makes destination writable and completes migration.
- ✗
Enable point-in-time recovery on the destination.
Why it's wrong here
Not essential for cutover; can be done later.
- ✗
Take a full backup of the source after quiescing.
Why it's wrong here
Unnecessary; DMS already replicated data.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PCDE question from scratch — 1,446 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
6 more ways this is tested on PCDE
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. During a cutover from an on-premises Oracle database to Cloud SQL for PostgreSQL, the team needs to minimize downtime. They have set up continuous replication using a custom tool. Which sequence of steps should they follow to perform the cutover with minimal data loss?
hard- A.Quiesce writes, promote destination, verify lag, update connection strings.
- ✓ B.Quiesce writes, verify lag is 0, promote destination, update connection strings, verify application.
- C.Promote destination, quiesce writes, verify lag, update connection strings, verify application.
- D.Update connection strings, quiesce writes, verify lag, promote destination.
Why B: The correct sequence: quiesce writes to source (stop application writes), verify replication lag is zero (all changes replicated), promote destination (make it writable), update connection strings, then verify the application. Rolling back involves keeping source read-only.
Variation 2. A team is migrating a MySQL database to Cloud SQL using DMS with continuous CDC. They want to minimize downtime during cutover. Which three actions should they take as part of the cutover plan? (Choose 3)
medium- ✓ A.Quiesce write operations on the source database.
- B.Delete the migration job immediately after promotion.
- ✓ C.Promote the destination Cloud SQL instance.
- ✓ D.Confirm DMS replication lag is 0.
- E.Disable binary logging on the source.
Why A: During cutover, the steps are: quiesce writes on source, confirm DMS lag is 0, promote the destination, update application connection strings, and keep the source available for rollback. Disabling binary logging or deleting the source prematurely are not part of a safe cutover.
Variation 3. An organization needs to continuously replicate data from an on-premises PostgreSQL database to AlloyDB with minimal downtime during cutover. They have set up DMS continuous migration. During the cutover phase, what is the correct sequence of steps?
medium- A.Update connection strings first, then promote destination, then verify lag.
- B.Stop source database, promote destination, then update connection strings.
- ✓ C.Quiesce writes to source, confirm DMS lag is 0, promote destination, update connection strings, verify application, keep source running read-only.
- D.Promote target immediately, then verify lag, then update connection strings.
Why C: The standard cutover: quiesce writes, verify DMS lag is 0, promote (stop replication), update connection strings, verify app, and keep source for rollback.
Variation 4. A company is planning a cutover from an on-premises MySQL database to Cloud SQL after a DMS continuous migration. To ensure minimal downtime and a successful cutover, which TWO actions should be part of the cutover procedure? (Choose TWO.)
medium- ✓ A.Stop all writes to the source database.
- B.Increase the source database's CPU.
- C.Delete the DMS migration job immediately.
- D.Enable binary logging on Cloud SQL.
- ✓ E.Verify that DMS replication lag is zero.
Why A: Before cutover, quiesce writes to source and confirm DMS lag is zero to avoid data loss.
Variation 5. A company wants to migrate a self-managed PostgreSQL database to AlloyDB with minimal downtime. They plan to use Database Migration Service with continuous CDC. The source database is in a different region. Which THREE steps should they include in their cutover plan? (Choose 3 correct answers.)
hard- A.Run a full performance test on AlloyDB before cutover.
- ✓ B.Quiesce writes to the source database.
- ✓ C.Confirm replication lag is zero.
- D.Delete the source database immediately after promotion.
- ✓ E.Promote the AlloyDB destination to make it the primary.
Why B: Cutover plan: quiesce writes to source, confirm replication lag is 0, promote the destination, update connection strings, and keep source running read-only for rollback. Testing before cutover is important but not part of the cutover plan step. DMS can work across regions but may have increased lag. Deleting the source immediately is risky.
Variation 6. A team is planning the cutover for a DMS continuous migration. They want to minimize downtime. What is the correct cutover procedure?
easy- A.Update connection strings to point to destination, then promote.
- B.Promote destination immediately, then stop source.
- C.Stop source, promote destination, update connection strings.
- ✓ D.Quiesce writes, confirm lag 0, promote destination, update connection strings, verify.
Why D: The standard cutover: quiesce writes to source, verify DMS lag is 0, promote the destination, update application connection strings, then verify. Keeping source read-only allows rollback.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCDE exam.