MySQL to Aurora MySQL Migration Methods for Minimal Downtime
A company is migrating a MySQL database to Amazon Aurora MySQL. The migration must be completed with minimal downtime. Which TWO methods can achieve this? (Choose two.)
Quick Answer
The answer is using AWS Database Migration Service with ongoing replication and setting up an Aurora read replica from an external MySQL instance via binlog replication. AWS DMS with ongoing replication continuously captures changes from the source MySQL database and applies them to Aurora, enabling a cutover with near-zero downtime. The Aurora read replica method works by configuring MySQL binlog replication from the external instance directly to Aurora, allowing the replica to stay synchronized until you promote it. On the AWS Certified Database Specialty DBS-C01 exam, this question tests your understanding of live migration strategies versus batch or snapshot-based approaches. A common trap is confusing an Aurora clone—which only works within existing Aurora clusters—with a cross-engine migration, or thinking that a snapshot restore alone achieves minimal downtime when it actually requires taking the source offline. Remember the memory tip: “DMS streams, binlog syncs—both keep the clock ticking during the switch.”
⚠ Common exam trap
Many candidates think enabling binlog replication alone (Option E) is sufficient for migration, but it is only a prerequisite; the actual migration requires a replication channel or a service like DMS to consume the binlog stream.
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
✓
Create an Aurora MySQL read replica from the external MySQL instance using binlog replication
You can set up an external MySQL instance as a replication source for an Amazon Aurora MySQL read replica using binary log (binlog) replication. This allows the Aurora cluster to stay synchronized with the source database with minimal downtime, as you only need to stop writes on the source and promote the Aurora replica when ready. Option D is correct because AWS Database Migration Service (AWS DMS) supports ongoing replication using change data capture (CDC) to keep the target Aurora database continuously synchronized with the source MySQL database, enabling a migration with minimal downtime. Options B, C, and E are incorrect: taking a physical backup and restoring (B) or creating an Aurora clone from the source (C) would require downtime; enabling binlog replication alone (E) is not sufficient—it must be used with a replication setup or a service like DMS.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create an Aurora MySQL read replica from the external MySQL instance using binlog replication
Why this is correct
This allows near-zero downtime replication.
- ✗
Take a physical backup of the source database and restore to Aurora
Why it's wrong here
This requires downtime during backup and restore.
- ✗
Create an Aurora clone from the source database
Why it's wrong here
Aurora clone is for cloning existing Aurora clusters, not for migration from MySQL.
- ✓
Use AWS Database Migration Service (AWS DMS) with ongoing replication
Why this is correct
DMS supports minimal downtime migration with CDC.
- ✗
Enable binlog replication on the source MySQL instance
Why it's wrong here
This is a prerequisite but not a complete migration method.
Visual reference
Go deeper
Related to this question
About these practice questions
This DBS-C01 question is part of Courseiva's 1,663-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
5 more ways 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 a 1 TB MySQL database to Amazon Aurora MySQL with minimal downtime. The database has a high write load. Which TWO options are valid approaches? (Choose two.)
medium- ✓ A.Use AWS DMS with full load and ongoing replication.
- B.Export to flat files, transfer via AWS Snowball, and import.
- C.Perform a mysqldump and restore to Aurora.
- ✓ D.Use MySQL native replication to replicate to Aurora MySQL.
- E.Use AWS SCT to convert the schema and then use DMS.
Why A: AWS DMS supports full load and ongoing change data capture (CDC) replication, which can migrate the 1 TB MySQL database to Aurora MySQL with minimal downtime by continuously applying changes from the source binary logs. This approach handles high write loads efficiently by using transactional replication to keep the target nearly synchronized until cutover.
Variation 2. A company is migrating a 500 GB MySQL database to Amazon Aurora MySQL. The migration must have minimal downtime and the source database is already using binary logging. Which migration approach should be used?
hard- A.Take a snapshot of the source database and restore to Aurora
- B.Use AWS DMS with full load only
- ✓ C.Set up binary log replication from the source to an Aurora MySQL cluster
- D.Use mysqldump to export the data and import into Aurora
Why C: MySQL native binary log replication can be set up directly from a source MySQL database to an Amazon Aurora MySQL cluster. Since binary logging is already enabled, the Aurora cluster can act as a replica, synchronizing continuously with minimal downtime. This approach allows a full load followed by ongoing replication, meeting the requirement for near-zero downtime migration.
Variation 3. A company is migrating a 200 GB MySQL database to Amazon Aurora MySQL. The migration must be completed within a 1-hour downtime window. Which TWO methods can achieve this?
easy- A.Use AWS SCT to convert the schema and then perform a data load.
- B.Use AWS DMS with full load only.
- ✓ C.Use Percona XtraBackup to create a physical backup, upload to S3, and restore to Aurora.
- ✓ D.Use mysqldump with parallel threads and import using mysql command.
- E.Create an RDS Read Replica of the on-premises database and promote it.
Why C: Percona XtraBackup creates a physical backup of the MySQL data files, which can be uploaded to Amazon S3 and then restored directly into an Aurora MySQL cluster. This method is significantly faster than logical backups for large databases (200 GB) because it bypasses SQL parsing and row-by-row insertion, making it feasible within a 1-hour downtime window.
Variation 4. A company is migrating a 100 GB MySQL database to Amazon Aurora MySQL. The migration must have minimal downtime and the source database is currently in use. Which approach should the company take?
easy- A.Create an Aurora Replica from the on-premises MySQL database and promote it.
- B.Export the database using mysqldump and import it into Aurora during a maintenance window.
- C.Take a physical backup of the MySQL database, upload to S3, and restore to Aurora.
- ✓ D.Use AWS DMS with ongoing replication from the source MySQL database to Aurora.
Why D: AWS DMS with ongoing replication (change data capture, CDC) is the correct approach because it allows a live migration with minimal downtime. DMS performs a full load of the 100 GB database and then continuously replicates incremental changes from the source MySQL to the target Aurora MySQL until you cut over, keeping the source fully operational throughout the process.
Variation 5. A company is migrating a 5 TB MySQL database to Amazon Aurora MySQL. The migration must have zero downtime and the source database is continuously written to. The team plans to use AWS DMS with ongoing replication. However, they notice that the target Aurora instance is not receiving all changes from the source. Which configuration change is most likely required to resolve this?
hard- A.Create an Amazon RDS read replica of the source database and use it as the source endpoint.
- B.Set the target table preparation mode to 'Do nothing' in the DMS task.
- ✓ C.Enable binary logging (binlog) on the source MySQL database with row-based logging.
- D.Configure a VPC endpoint for the DMS replication instance.
Why C: AWS DMS requires binary logging (binlog) with row-based logging on the source MySQL database to capture ongoing changes for continuous replication. Without binlog enabled, DMS cannot read the change data stream needed to replicate transactions to the target Aurora instance, causing missed changes. This is a mandatory prerequisite for any MySQL-to-Aurora migration using DMS with ongoing replication.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.