A large gaming company is creating a centralized solution to store player session state for multiple online games. The workload required key-value storage with low latency and will be an equal mix…

Question

Options

• AAmazon RDS for MySQL with multi-Region read replicas
• BAmazon Aurora global database
• CAmazon RDS for Oracle with GoldenGate
• DAmazon DynamoDB global tables

• A
  3% (1)
• B
  7% (2)
• C
  10% (3)
• D
  80% (24)

Explanation

DynamoDB Global Tables is the right fit because it is a fully managed, serverless key-value store that natively supports multi-Region active-active replication - meaning writes can land in any Region and automatically sync globally with no replication infrastructure to manage.

Why the distractors fail:

• A (RDS for MySQL with read replicas) - read replicas are read-only in remote Regions, so you cannot write closest to the user; this is a read-scaling tool, not a global write solution.
• B (Aurora global database) - also only supports writes in one primary Region; secondary Regions are read-only, so geographically distributed writes are not possible.
• C (RDS for Oracle with GoldenGate) - GoldenGate can do multi-master replication, but it is complex to operate, expensive, and adds significant management overhead - the opposite of what the question requires.

Memory tip: Whenever you see the combo of key-value, low latency, global writes, and minimal management, think DynamoDB Global Tables - it is the only AWS-native, fully managed service that checks all four boxes simultaneously. RDS/Aurora options are relational (not key-value) and lack active-active global write capability out of the box.

No community discussion yet for this question.