Migrating RDS MySQL to Aurora PostgreSQL with DMS

SAA-C03 By islever Editorial Last updated

Short answer

AD Use AWS DMS Schema Conversion to transform the database objects and define a DMS task with change data capture (CDC) to migrate the data.

Question

A company runs a three-tier application in a VPC. The database tier uses an Amazon RDS for MySQL DB instance. The company plans to migrate the RDS for MySQL DB instance to an Amazon Aurora PostgreSQL DB cluster. The company needs a solution that replicates the data changes that happen during the migration to the new database. Which combination of steps will meet these requirements? (Choose two.)
  1. Use AWS Database Migration Service (AWS DMS) Schema Conversion to transform the database objects. Correct Answer
  2. Use AWS Database Migration Service (AWS DMS) Schema Conversion to create an Aurora PostgreSQL read replica on the RDS for MySQL DB instance.
  3. Configure an Aurora MySQL read replica for the RDS for MySQL DB instance.
  4. Define an AWS Database Migration Service (AWS DMS) task with change data capture (CDC) to migrate the data. Correct Answer
  5. Promote the Aurora PostgreSQL read replica to a standalone Aurora PostgreSQL DB cluster when the replica lag is zero.

Key Takeaways

The question tests heterogeneous migration capabilities of AWS DMS, where the common trap is confusing homogeneous replication methods with heterogeneous schema conversion and CDC requirements.

This page explains how to migrate an Amazon RDS for MySQL instance to an Amazon Aurora PostgreSQL cluster using AWS Database Migration Service (DMS) and Schema Conversion Tool. It establishes that schema conversion and CDC tasks are the required steps to handle heterogeneous database migrations.

Common mistake: Many users incorrectly choose options involving read replicas or confuse Aurora MySQL with Aurora PostgreSQL, failing to recognize that DMS Schema Conversion is necessary for different engines.

Expert Analysis

Why the Answer Is Correct

To migrate from RDS for MySQL to Aurora PostgreSQL, you must address both the data structure differences and the ongoing data synchronization. Option A is correct because AWS DMS Schema Conversion (SCT) is specifically designed to convert the schema objects from MySQL to PostgreSQL syntax. Option D is correct because defining a DMS task with Change Data Capture (CDC) allows for continuous replication of changes from the source MySQL instance to the target PostgreSQL cluster during the migration process.

Why the Other Options Are Wrong

Option B is incorrect because Schema Conversion does not create read replicas; it converts schemas. Option C is incorrect because you cannot create an Aurora MySQL read replica from an RDS for MySQL instance; read replicas are typically within the same engine family or specific supported cross-engine scenarios that don't fit this direct path without DMS. Option E is incorrect because promoting a read replica is part of a homogeneous failover or replication strategy, not the primary method for converting schemas between different database engines like MySQL and PostgreSQL.

Community Comment Notes

Community consensus strongly supports AD. As user h0ng97 noted, SCT handles the conversion while CDC captures changes. Some users initially questioned if BE was possible, but E relies on a read replica which isn't the standard tool for heterogeneous schema conversion in this context. The comment about lag never being zero highlights why relying solely on replica promotion timing is risky compared to DMS CDC.

Official Reference

Exam Strategy

When migrating between different database engines (heterogeneous), always look for AWS DMS Schema Conversion first. Then, pair it with a DMS task using CDC to ensure data consistency during the cutover phase.

Frequently Asked Questions

Why can't I just use a read replica for MySQL to PostgreSQL migration?

Read replicas generally replicate within the same engine. For different engines like MySQL to PostgreSQL, you need DMS to translate the schema and data types.

What is the role of CDC in this migration?

CDC captures ongoing changes in the source database, allowing you to keep the target synchronized until you switch applications over.

More SAA-C03 FAQ →

Community Votes

AD
100%

100% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 6 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 6

  1. h0ng97_spare_002 👍 8
    A: Correct. because need convert from MySQL to PostgreSQL B: Wrong. Schema Conversion does not create an Aurora read replica C: Wrong. Company wants to migrate to Aurora PostgreSQL, not Aurora MySQL D: Correct. CDC task helps to capture ongoing change from source data store E: Wrong. Although using Aurora Read Replica is an option for DB migration within the same Region, this question is asking for "combination of steps", which this option does not have another compatible option to pair with Therefore, answer is "AD"
  2. mestule 👍 6
    AD makes sense to me, but I am not sure if that's the best answer.
  3. haci 👍 4
    It's quite similar with Q.235, based on that discussion A-D makes more sense.
  4. xBUGx 👍 2
    Lag many never be zero, then it will ne er be promoted to primary
  5. Andy_09 👍 4
    Correct answer BE
Show 1 more comment
  1. Scheldon 👍 2
    AnswerAD

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide