Course menuSAP-C03

Exams / SAP-C03 / Choosing and scaling databases (Aurora, DynamoDB, global databases) / Question 1

SAP-C03 practice question: Choosing and scaling databases (Aurora, DynamoDB, global databases)

Architecture Design and Implementation Built for the Cloud A free question from our original SAP-C03 practice exam. Try it, then open the answer to see why each option is right or wrong.

Last verified against current AWS documentation ·How we write our questions

A car maker runs a dealer inventory system with dealers in North America, Europe and Asia-Pacific. Each dealer updates its own stock records, and those updates must finish in under 20 milliseconds in the dealer's Region, without a cross-Region round trip.

Every Region must be able to read the other Regions' stock records within about a second. If a Region fails, the other two must keep accepting updates for their own dealers. The team does not want to manage database replication software itself.

Which solution meets these requirements?

Choose one answer.

  1. A. Use an Amazon Aurora Global Database with its primary cluster in North America and read-only secondary clusters in the other Regions. Dealers in other Regions send writes through the secondary clusters.
  2. B. Create an Amazon RDS for MySQL instance with Multi-AZ in North America, and add cross-Region read replicas in Europe and Asia-Pacific that serve dealer reads.
  3. C. Deploy self-managed MySQL on EC2 instances in each Region and configure bidirectional replication between them, with the team running the replication software and failover scripts.
  4. D. Create an Amazon DynamoDB global table that replicates across the three Regions, with each dealer's items written in its local Region. Each Region keeps accepting writes if another Region fails.
Show the answer and explanation

Answer: D

  • A. Wrong: Writes from the secondary Regions are forwarded to the primary cluster, which adds a cross-Region round trip and misses the 20-millisecond requirement. A failed primary also stops writes until a failover is done.
  • B. Wrong: Cross-Region read replicas accept no writes, so dealers in Europe and Asia-Pacific would send updates to North America. That breaks the local-write requirement.
  • C. Wrong: Bidirectional replication can accept local writes, but the team would run and tune the replication and failover itself. That is the operational work the team wants to avoid.
  • D. Right: Correct. Global tables accept writes in every replica Region and replicate changes between them without the team managing replication, and dealer-specific items avoid most conflicting updates. A failed Region does not stop writes in the other two.

Explanation

DynamoDB global tables accept local writes in every Region and replicate them without operator effort. An Aurora global secondary forwards writes across Regions, read replicas accept no writes, and self-managed bidirectional replication adds operating work.

A DynamoDB global table with replicas in two Regions Users in each Region read and write their nearest table replica. DynamoDB replicates changes between the replicas in both directions, and each Region keeps working if the other fails. Region A Region B Nearby users Table replica reads and writes Nearby users Table replica reads and writes multi-Region replication, both ways
Every Region accepts writes for its own dealers and keeps working if another Region fails.

Study

Keep practicing

Answer questions with a score at the end, or practice just this topic with the explanation after each one. No sign-up needed.

Want more on Choosing and scaling databases (Aurora, DynamoDB, global databases)? The 5 full-length practice sets have 5 more Choosing and scaling databases (Aurora, DynamoDB, global databases) questions, 375 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets