Question 1,267 of 1,663
MySQL Migration to RDS with Heavy Writes: Native Replication
A company wants to migrate an on-premises MySQL database to Amazon RDS for MySQL. The database is 500 GB and experiences heavy write traffic. They need to minimize downtime and ensure no data loss. Which approach should they take?
Quick Answer
The correct answer is to set up MySQL replication from the on-premises database to Amazon RDS, then promote the RDS instance when ready. This approach is ideal for a MySQL migration with heavy writes and zero data loss because native replication continuously streams binary log changes from the source to the target, capturing every transaction as it happens. On the AWS Certified Database Specialty DBS-C01 exam, this scenario tests your understanding of how to achieve near-zero downtime migration without requiring the source to be read-only, which is a common trap—many candidates mistakenly choose a dump and reload, forgetting that heavy write traffic would cause data loss during the lock. Another frequent pitfall is assuming AWS DMS with full load alone can handle ongoing changes, but it misses writes after the initial load unless you also configure ongoing replication. Remember the memory tip: “Replicate, don’t dump; keep the writes pumping.”
⚠ Common exam trap
Watch out — candidates often confuse AWS DMS's ongoing replication (CDC) with a full load task, or mistakenly think RDS read replicas can be created from external databases, leading them to choose options that either risk data loss or are technically impossible.
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
✓
Set up MySQL replication from the on-premises database to RDS, then promote the RDS instance when ready.
Setting up native MySQL replication from the on-premises database to Amazon RDS for MySQL allows continuous synchronization with minimal downtime. When ready, you simply stop replication and promote the RDS instance, ensuring zero data loss since all transactions are replicated in near real-time.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use AWS DMS with a full load task, then cut over the application to RDS.
Why it's wrong here
Full load only does not capture changes made during the migration, leading to data loss.
- ✓
Set up MySQL replication from the on-premises database to RDS, then promote the RDS instance when ready.
Why this is correct
Replication captures ongoing changes, minimizing downtime and ensuring data consistency.
- ✗
Create an RDS read replica of the on-premises database, then promote it to a standalone instance.
Why it's wrong here
RDS read replicas cannot be created from an external MySQL instance; they only work within RDS.
- ✗
Use mysqldump to export the database and mysql command to import into RDS during a maintenance window.
Why it's wrong here
This requires the source database to be offline during export, causing downtime.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on DBS-C01
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. A company wants to migrate an on-premises MySQL database to Amazon RDS for MySQL with minimal downtime. The database is 500 GB and has moderate write activity. Which approach is MOST suitable?
medium- ✓ A.Use AWS Database Migration Service (DMS) with a full load and ongoing replication.
- B.Use mysqldump to export the database, then import into RDS.
- C.Use AWS Server Migration Service (SMS) to migrate the database server.
- D.Create a read replica of the on-premises database and promote it to RDS.
Why A: AWS DMS with full load and ongoing replication is the most suitable approach because it supports continuous change data capture (CDC) from the on-premises MySQL source to the Amazon RDS target, enabling minimal downtime. The full load transfers the initial 500 GB dataset, while ongoing replication applies incremental changes until cutover, meeting the requirement for minimal downtime with moderate write activity.
Last reviewed: Jul 4, 2026
This DBS-C01 practice question is part of Courseiva's free Amazon Web Services 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 DBS-C01 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.