A company is running an Amazon RDS for PostgeSQL DB instance and wants to migrate it to an Amazon Aurora PostgreSQL DB cluster. The current database is 1 TB in size. The migration needs to have…

Question

Options

• ACreate an Aurora PostgreSQL DB cluster. Set up replication from the source RDS for
• BUse the pg_dump and pg_restore utilities to extract and restore the RDS for PostgreSQL DB
• CCreate a database snapshot of the RDS for PostgreSQL DB instance and use this snapshot to
• DMigrate data from the RDS for PostgreSQL DB instance to an Aurora PostgreSQL DB cluster

• A
  4% (2)
• B
  8% (4)
• C
  14% (7)
• D
  73% (36)

Explanation

Explanation

Option D refers to using Aurora Migration Service / AWS Database Migration Service (DMS) with ongoing replication, which enables a live migration with minimal downtime by continuously replicating changes from the source RDS PostgreSQL instance to the Aurora PostgreSQL cluster while it catches up - allowing a near-zero downtime cutover. Option A (setting up manual replication) is slower to configure and more complex, making it not the fastest approach for this scale. Option B (pg_dump/pg_restore) requires taking the database offline or freezing writes during the dump of a 1 TB database, resulting in significant downtime and very slow transfer speeds. Option C (snapshot restore) creates a static point-in-time copy, meaning any changes after the snapshot are lost unless additional manual steps are taken, and the restore process for a 1 TB snapshot is time-consuming.

Memory Tip: Think "DMS = Drip Migration Strategy" - it continuously drips changes from source to target in real time, so when you're ready to cut over, the gap is tiny and downtime is minimal. For large databases with a minimal-downtime requirement, DMS with CDC (Change Data Capture) is almost always the AWS-preferred answer.

No community discussion yet for this question.