Examkin

Question

Difficulty: MediumHigh-Performing Content Delivery and Caching Solutions

A global multiplayer gaming platform hosts player profile statistics in an Amazon RDS for PostgreSQL database and stores downloadable game patch files in an Amazon S3 bucket. The game client retrieves profile statistics via read-heavy API queries and downloads patch files whenever a new update is released. Player traffic is highly distributed globally and spikes unpredictably. A solutions architect needs to design a high-performing content delivery and caching solution that minimizes latency for both assets and queries while reducing load on the database. Which two configurations should the solutions architect implement to meet these requirements? (Select TWO.)

  1. Configure an Amazon CloudFront distribution with the Amazon S3 bucket as the origin to cache and serve the game patch files closer to users.Answer
  2. Implement an Amazon ElastiCache for Redis cluster in front of the Amazon RDS database to cache frequent and repetitive query results for player profiles.Answer
  3. C
    Configure an Amazon CloudFront distribution for the Amazon S3 bucket, and set the cache behavior's Minimum TTL, Maximum TTL, and Default TTL to 0 seconds.
  4. D
    Deploy Amazon RDS Read Replicas to cache query results, and configure them to automatically promote to the primary write database during an Availability Zone outage.
  5. E
    Migrate the player statistics to Amazon DynamoDB and use the player's last login date (YYYY-MM-DD) as the partition key to distribute write and query loads evenly.

Answer

To optimize performance, the solutions architect should configure an Amazon CloudFront distribution to cache static game patch files from the Amazon S3 bucket and deploy an Amazon ElastiCache for Redis cluster to cache read-heavy player profile queries from the Amazon RDS database.
The correct solution involves combining edge caching for static patch files via Amazon CloudFront and database query caching using Amazon ElastiCache for Redis. CloudFront brings static assets closer to the users, while ElastiCache speeds up repetitive database read queries, lowering overall latency and origin load.

Step-by-Step Solution

1
Analyze the requirements for static assets (patch files) and query latency.
Identify that the patch files are static and accessed globally, making them ideal for edge caching with Amazon CloudFront.
CloudFront reduces latency by caching files at edge locations closer to global users and prevents S3 from being overloaded.
2
Analyze the requirements for database read performance.
Identify that player profile queries are read-heavy and repetitive, which can be accelerated by an in-memory caching layer like Amazon ElastiCache.
ElastiCache handles high-throughput, low-latency reads, reducing the direct load on the Amazon RDS for PostgreSQL instance.
3
Evaluate the remaining options for design flaws or misconfigurations.
Discard options containing zero TTL configurations, incorrect read replica failover roles, and hot-key database partition designs.
These options introduce latency bottlenecks, violate proper failover architecture patterns, or cause operational throttling.

Key Concept

Multi-tier caching separates static content caching at the edge using CloudFront from database query acceleration using an in-memory database cache like ElastiCache.
Rate this question

Topics

High-Performing Content Delivery and Caching Solutions

More questions from this topic