DBS-C01 · Question #40
A retail company with its main office in New York and another office in Tokyo plans to build a database solution on AWS. The company's main workload consists of a mission-critical application that upd
The correct answer is D. Use an Amazon Aurora global database. Deploy the writer instance in the us-east-1 Region and. Explanation Amazon Aurora Global Database is the ideal solution because it is purpose-built for globally distributed applications, offering sub-second replication lag (typically under 1 second) between the primary writer region (us-east-1) and up to five read-only secondary regio
Question
A retail company with its main office in New York and another office in Tokyo plans to build a database solution on AWS. The company's main workload consists of a mission-critical application that updates its application data in a data store. The team at the Tokyo office is building dashboards with complex analytical queries using the application data. The dashboards will be used to make buying decisions, so they need to have access to the application data in less than 1 second. Which solution meets these requirements?
Options
- AUse an Amazon RDS DB instance deployed in the us-east-1 Region with a read replica instance
- BUse an Amazon DynamoDB global table in the us-east-1 Region with replication into the ap-
- CUse an Amazon RDS for MySQL DB instance deployed in the us-east-1 Region with a read
- DUse an Amazon Aurora global database. Deploy the writer instance in the us-east-1 Region and
How the community answered
(20 responses)- A15% (3)
- B10% (2)
- C30% (6)
- D45% (9)
Explanation
Explanation
Amazon Aurora Global Database is the ideal solution because it is purpose-built for globally distributed applications, offering sub-second replication lag (typically under 1 second) between the primary writer region (us-east-1) and up to five read-only secondary regions (including ap-northeast-1 for Tokyo). This allows the Tokyo team to run complex analytical queries against a local read replica without impacting the mission-critical write workload in New York.
Why the distractors fail:
- Option A (RDS with a read replica) uses standard RDS replication, which does not guarantee sub-second replication lag across regions - it can lag by minutes under heavy load.
- Option B (DynamoDB Global Tables) is excellent for key-value/document workloads with fast replication, but DynamoDB is not suited for complex analytical queries requiring SQL-style joins and aggregations.
- Option C (RDS for MySQL with a read replica) suffers the same problem as Option A - cross-region MySQL replication cannot reliably meet the under-1-second latency requirement for analytical workloads.
Memory Tip: Think of Aurora Global Database as the "globe-trotter" of AWS databases - it's the only managed relational database service specifically engineered to replicate across regions in under 1 second, making it the go-to answer whenever you see global + relational + low-latency replication.
Topics
Community Discussion
No community discussion yet for this question.