A Database Specialist is designing a new database infrastructure for a ride hailing application. The application data includes a ride tracking system that stores GPS coordinates for all rides…

Question

Options

• AUse Amazon RDS for MySQL as the database and use Amazon ElastiCache
• BUse Amazon DynamoDB as the database and use DynamoDB Accelerator
• CUse Amazon Aurora MySQL as the database and use Aurora's buffer cache
• DUse Amazon DynamoDB as the database and use Amazon API Gateway

• A
  7% (2)
• B
  55% (16)
• C
  24% (7)
• D
  14% (4)

Explanation

Explanation

Option B is correct because DynamoDB is a fully managed NoSQL database purpose-built for high-throughput, low-latency workloads like GPS tracking and real-time lookups, and DynamoDB Accelerator (DAX) is an in-memory caching layer specifically designed for DynamoDB that delivers microsecond latency - exactly matching the stated requirement - with minimal operational overhead since AWS manages everything.

• Option A (RDS + ElastiCache) is incorrect because while ElastiCache can provide low latency, the combination requires significantly more operational overhead to manage, configure, and maintain two separate services alongside a relational database not optimized for this use case.
• Option C (Aurora + buffer cache) is incorrect because Aurora's buffer cache is an internal database memory feature, not a dedicated caching solution, and it cannot reliably guarantee microsecond-level latency for real-time statistics at scale.
• Option D (DynamoDB + API Gateway) is incorrect because API Gateway is an API management service, not a caching or performance accelerator - it adds latency rather than reducing it.

Memory Tip

Think "DAX = DynamoDB Accelerator = microseconds" - whenever an exam question mentions DynamoDB with microsecond latency requirements, DAX is almost always the answer. If the question mentions millisecond latency, standard DynamoDB may suffice.

No community discussion yet for this question.