Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Solutions Architect - Professional · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Option D achieves the result more directly by converting the RDS instance to Aurora in fewer steps: Step 1: Convert RDS MySQL to Aurora MySQL Step 2: Add eu-west-1 as a secondary Region Step 3: Enable write forwarding Option A is wrong bcuz — it's approach is unnecessarily complex: Creating an Aurora replica of RDS, pausing writes, promoting, and reconfiguring is a multi-step migration with risk and downtime The core Aurora Global + write forwarding architecture is the same, but A introduces unnecessary operational overhead.
Why Option D is Correct This solution meets all the requirements: ✅ Real-time data access: Aurora Global Database provides sub-1-second cross-Region replication latency ✅ Bi-directional writes: Write forwarding allows customers in Europe to write to the database, with changes automatically forwarded to the primary cluster in us-east-1 ✅ No stale data: Both US and European customers see updates in real-time through Aurora's global replication ✅ Low latency: European customers connect to a local Aurora endpoint in eu-west-1
A is the exact way to do it as of DEC2025. D is the way to describe is but without the lower level details of the exact steps that A actually contains. This is the misdirect - both are actually correct but A is accurate and D is right but not as much detail. Clue is the in D's wording "Convert" - there is not convert feature or function, there is a migration option that starts the process with "Create a replica" or the exact first step in A.