DBS-C01 Question #43: Real Exam Question with Answer & Explanation

Question

A media company is running a critical production application that uses Amazon RDS for PostgreSQL with Multi-AZ deployments. The database size is currently 25 TB. The IT Director wants to migrate the database to Amazon Aurora PostgreSQL with minimal effort and minimal disruption to the business. What is the best migration strategy to meet these requirements?

Options

• AUse the AWS Schema Conversion Tool (AWS SCT) to copy the database schema from RDS for
• BCreate a script to continuously back up the RDS for PostgreSQL instance using pg_dump, and
• CCreate a read replica from the existing production RDS for PostgreSQL instance. Check that the
• DCreate an Aurora Replica from the existing production RDS for PostgreSQL instance. Stop the

Explanation

Explanation

Option D is correct because Amazon RDS supports the native Aurora Read Replica feature, which allows you to create an Aurora PostgreSQL replica directly from an existing RDS for PostgreSQL instance with minimal effort - the replication is managed by AWS, keeps data in sync continuously, and allows a clean failover by simply promoting the Aurora replica, resulting in minimal downtime and disruption.

Why the distractors are wrong:

• Option A (AWS SCT) is designed for heterogeneous migrations (e.g., Oracle to PostgreSQL), not same-engine migrations like RDS PostgreSQL to Aurora PostgreSQL - it adds unnecessary complexity.
• Option B (pg_dump scripting) is a manual, error-prone approach that would cause significant downtime and complexity for a 25 TB database, far from "minimal effort."
• Option C (RDS Read Replica) creates a standard RDS read replica, not an Aurora replica - you'd still need additional steps to migrate to Aurora, making it less efficient than Option D.

💡 Memory Tip: Think "Aurora Replica = Native Bridge." When migrating from RDS PostgreSQL to Aurora PostgreSQL, AWS gives you a direct bridge via the Aurora Replica feature - no third-party tools, no dumps, just replicate and promote. If the engine family is the same, always look for the native AWS replication path first.

No community discussion yet for this question.