AWS Certified Solutions Architect – Associate (SAA-C02) — Question 376
A company is moving its on-premises Oracle database to Amazon Aurora PostgreSQL. The database has several applications that write to the same tables. The applications need to be migrated one by one with a month in between each migration Management has expressed concerns that the database has a high number of reads and writes. The data must be kept in sync across both databases throughout tie migration.
What should a solutions architect recommend?
Answer options
- A. Use AWS DataSync for the initial migration. Use AWS Database Migration Service (AWS DMS) to create a change data capture (CDC) replication task and a table mapping to select all cables.
- B. Use AWS DataSync for the initial migration. Use AWS Database Migration Service (AWS DMS) to create a full load plus change data capture (CDC) replication task and a table mapping to select all tables.
- C. Use the AWS Schema Conversion Tool with AWS DataBase Migration Service (AWS DMS) using a memory optimized replication instance. Create a full load plus change data capture (CDC) replication task and a table mapping to select all tables.
- D. Use the AWS Schema Conversion Tool with AWS Database Migration Service (AWS DMS) using a compute optimized replication instance. Create a full load plus change data capture (CDC) replication task and a table mapping to select the largest tables.
Correct answer: C
Explanation
Migrating between heterogeneous database engines (Oracle to PostgreSQL) requires the AWS Schema Conversion Tool (SCT) to convert the schema, which rules out AWS DataSync. Since the database experiences high read/write volume, a memory-optimized replication instance is necessary for AWS DMS to handle the heavy transaction load during full load and ongoing change data capture (CDC) replication. All tables must be selected to keep the entire database synchronized while applications are migrated over the course of several months.