A solutions architect is optimizing a global news website. The application's static assets, such as CSS files and logos, are served from an Application Load Balancer (ALB) origin through an Amazon CloudFront distribution. During a performance review, the architect notices that the ALB continues to receive a high volume of requests for these static assets, causing unnecessary origin load. Investigation reveals that the CloudFront cache behavior for these assets has its Minimum TTL, Maximum TTL, and Default TTL all set to 0 seconds. Which configuration change should the solutions architect make to reduce the load on the origin ALB?
- Increase the Minimum TTL and Default TTL values in the cache behavior to allow CloudFront to cache the static assets at edge locations.Answer
- BKeep the TTL values set to 0 seconds in the cache behavior to ensure content freshness, and configure EC2 Auto Scaling to handle the origin request volume.
- CDeploy a NAT Gateway in the VPC to route CloudFront traffic to the Application Load Balancer, reducing the latency of origin fetches.
- DConfigure an Amazon Route 53 latency routing policy to direct user traffic directly to the Application Load Balancer, bypassing the CloudFront distribution.
Answer
Increase the Minimum TTL and Default TTL values in the cache behavior to allow CloudFront to cache the static assets at edge locations.
The correct option identifies that increasing the Minimum TTL and Default TTL settings enables CloudFront to cache static files. When these settings are configured with positive values, CloudFront stores the files at edge locations and serves them directly to users, eliminating unnecessary requests to the origin Application Load Balancer.
Step-by-Step Solution
Key Concept
Configuring Amazon CloudFront Time-to-Live (TTL) values to cache static content at edge locations and reduce load on origin servers.
Estimated Time:50s