Question

Difficulty: MediumHigh-Performing Content Delivery and Caching Solutions

A global multiplayer gaming platform uses Amazon API Gateway, AWS Lambda, and an Amazon DynamoDB table to store and serve live game leaderboards. During peak tournament events, users experience high latency when retrieving leaderboard standings, and the DynamoDB table experiences read throttling. The company needs a caching solution to reduce response latency to milliseconds and offload read queries from the database. Which two actions should the solutions architect take to meet these requirements? (Choose two.)

  1. Deploy an Amazon DynamoDB Accelerator (DAX) cluster to cache read queries to the leaderboard table.Answer
  2. Deploy an Amazon CloudFront distribution in front of the API Gateway, and configure a cache behavior for the leaderboard API resource with a positive Default TTL.Answer
  3. C
    Deploy an Amazon CloudFront distribution in front of API Gateway, and set the Minimum TTL, Maximum TTL, and Default TTL values to 0 for the leaderboard API cache behavior.
  4. D
    Transition the DynamoDB table from on-demand mode to provisioned capacity mode with high Read Capacity Units (RCUs) to handle the peak spikes, while disabling all caching layers.
  5. E
    Redesign the DynamoDB table to use a monotonically increasing tournament timestamp as the partition key to aggregate leaderboard reads, and query the table directly.

Answer

Deploying an Amazon DynamoDB Accelerator (DAX) cluster to cache read queries to the leaderboard table, and deploying an Amazon CloudFront distribution in front of API Gateway with a cache behavior configured with positive TTLs.
Deploying Amazon DynamoDB Accelerator (DAX) directly in front of DynamoDB handles database query caching, returning cached results in microseconds and reducing database read load. Deploying Amazon CloudFront in front of Amazon API Gateway with positive TTL values caches API responses at the edge, reducing both Lambda executions and API Gateway hits for global clients.

Step-by-Step Solution

1
Analyze the application architecture and requirements.
Identified that the leaderboard API is hosted on API Gateway, Lambda, and DynamoDB, and requires low latency and database offloading during peak events.
Understanding the bottleneck locations (API Gateway/Lambda compute and DynamoDB reads) helps target the right caching levels.
2
Select a database caching solution.
Choose DynamoDB Accelerator (DAX) to cache database read operations directly in front of DynamoDB.
DAX provides microsecond latency for cached reads and prevents cache misses or other database clients from overloading the table.
3
Select an edge caching solution.
Choose Amazon CloudFront with positive TTL values to cache API responses at edge locations.
CloudFront reduces latency globally and prevents repetitive requests from hitting API Gateway and Lambda.

Key Concept

Multi-tier caching using Amazon CloudFront and Amazon DynamoDB Accelerator (DAX)
Rate this question