A Database Specialist needs to define a database migration strategy to migrate an on-premises Oracle database to an Amazon Aurora MySQL DB cluster. The company requires near-zero downtime for the data

Question

Options

• ADump all the tables from the Oracle database into an Amazon S3 bucket using datapump
• BOrder an AWS Snowball appliance and copy the Oracle backup to the Snowball appliance. Once
• CUse the AWS Schema Conversion Tool (AWS SCT) to help rewrite database objects to MySQL
• DUse AWS Server Migration Service (AWS SMS) to import the Oracle virtual machine image as an

• A
  5% (2)
• B
  7% (3)
• C
  74% (31)
• D
  14% (6)

Explanation

Explanation

Option C is correct because the AWS Schema Conversion Tool (SCT) combined with AWS Database Migration Service (AWS DMS) is the purpose-built, cost-effective solution for heterogeneous database migrations (Oracle → MySQL). SCT converts the schema and stored procedures, while DMS handles the ongoing replication, enabling near-zero downtime through continuous change data capture (CDC) until cutover.

Why the distractors are wrong:

• Option A (S3 datapump dump) requires taking the database offline for the export/import process, causing significant downtime - violating the near-zero downtime requirement.
• Option B (AWS Snowball) is designed for large-scale physical data transfer to S3, not for live database migration with minimal downtime; it introduces delays waiting for physical device shipment.
• Option D (AWS SMS) is for migrating virtual machines/servers, not for database-level migrations; it doesn't handle Oracle-to-MySQL schema conversion or ongoing replication.

Memory Tip

Think of it as a two-step handshake: "SCT converts the structure, DMS moves the data continuously." Whenever you see a heterogeneous database migration (different engines) with near-zero downtime, always reach for the SCT + DMS combo - it's the AWS go-to pairing for cross-engine migrations.

No community discussion yet for this question.