Examkin

Question

Difficulty: MediumHigh-Performing Content Delivery and Caching Solutions

A collaborative document editing platform hosts its application on AWS. Users access static UI assets (such as CSS, JavaScript, and images) and retrieve real-time document metadata stored in an Amazon DynamoDB table. Users in distant geographic regions report high latency when loading the application and retrieving metadata. The DynamoDB database is also experiencing read performance bottlenecks due to repetitive queries for the same metadata. Which combination of configurations should the solutions architect implement to reduce latency for both static assets and database queries? (Select TWO.)

  1. Configure Amazon CloudFront with an Amazon S3 origin to cache and deliver the static UI assets closer to the users.Answer
  2. Deploy Amazon DynamoDB Accelerator (DAX) to cache database read operations for the document metadata.Answer
  3. C
    Configure an Amazon CloudFront distribution for the static UI assets and set the cache behavior's Minimum TTL, Maximum TTL, and Default TTL to 0.
  4. D
    Switch the DynamoDB table capacity mode to provisioned capacity mode with high read capacity units (RCUs) to handle the spikes in metadata requests.
  5. E
    Configure Amazon Route 53 latency-based routing to distribute database queries across separate DynamoDB tables in different regions without configuring health checks.

Answer

Configure Amazon CloudFront with an Amazon S3 origin to cache and deliver the static UI assets closer to the users, and deploy Amazon DynamoDB Accelerator (DAX) to cache database read operations for the document metadata.
The correct combination uses Amazon CloudFront to cache static UI assets (such as CSS, JavaScript, and images) at Edge Locations closer to the users, and uses Amazon DynamoDB Accelerator (DAX) to provide an in-memory cache directly in front of the DynamoDB table, reducing read latency for repetitive document metadata queries to microseconds.

Step-by-Step Solution

1
Analyze the workload requirements for static assets and database queries.
Identified that static UI assets require edge caching to reduce geographic latency, and DynamoDB reads require inline query caching to prevent database bottlenecks.
Dividing the problem into content delivery (static) and database acceleration (dynamic) ensures both layers are optimized.
2
Select the appropriate caching solution for static assets.
Chose Amazon CloudFront paired with Amazon S3 as the origin to cache CSS, JavaScript, and images at edge locations.
CloudFront reduces latency by caching static assets close to users, offloading traffic from origin servers.
3
Select the appropriate caching solution for DynamoDB.
Chose Amazon DynamoDB Accelerator (DAX) to cache document metadata reads.
DAX is API-compatible and provides microsecond read latency directly in front of DynamoDB tables, reducing database CPU load and query response times.

Key Concept

Multi-tier caching using Amazon CloudFront for edge content delivery and Amazon DynamoDB Accelerator (DAX) for in-memory database query acceleration.
Estimated Time:2m 0s
Rate this question

Topics

High-Performing Content Delivery and Caching Solutions

More questions from this topic