ANS-C01 Question 13
Select 3A media streaming application is hosted on AWS, serving users globally. The application faces latency issues for users in regions far from the origin server. To address this, the team decides to use Amazon CloudFront as a Content Delivery Network (CDN). Which design patterns should be implemented to optimize performance and cost efficiency?
- A
Configure Amazon CloudFront with multiple origin servers and implement cache behaviors to route requests based on URL patterns.
- B
Enable Amazon CloudFront's origin shield feature to reduce load on the origin and improve cache hit ratio.
- C
Set up CloudFront to forward all headers, cookies, and query strings to ensure maximum flexibility for dynamic content delivery.
- D
Use CloudFront's Lambda@Edge to customize responses at edge locations to reduce round-trip time for user requests.
- E
Disable CloudFront caching entirely for static content to ensure the most up-to-date files are always served.
Show answer and explanation
Correct answers: A, B, D
Explanation
To optimize performance and cost efficiency using Amazon CloudFront, it is crucial to implement design patterns such as configuring cache behaviors for efficient routing, enabling origin shield to reduce origin load, and leveraging Lambda@Edge for edge-level response customization. These patterns reduce latency for users and optimize the delivery of content globally. Avoiding unnecessary forwarding of headers and enabling caching for static content are also critical to achieving cost and performance goals.
- A. Correct.
Configuring CloudFront with multiple origin servers and cache behaviors allows you to serve content efficiently based on URL patterns, such as routing API requests to one origin and static content requests to another. This enhances performance and cost optimization.
- B. Correct.
Enabling the origin shield feature helps reduce the number of requests to the origin, improving the cache hit ratio and reducing latency for users. This is a recommended design pattern for cost efficiency.
- C. Incorrect.
Forwarding all headers, cookies, and query strings disables caching for many requests and increases latency and costs. This is not optimal for most use cases.
- D. Correct.
Using Lambda@Edge allows customization of responses at edge locations, reducing the round-trip time for user requests. This is a key design pattern for optimizing performance in global applications.
- E. Incorrect.
Disabling CloudFront caching for static content would lead to increased latency and higher costs as the origin server would be accessed for every request. This goes against the purpose of a CDN.