Answer-first summary for fast verification
Answer: Configure Amazon CloudFront to cache multiple versions of the content., Configure a Lambda@Edge function to send specific objects to users based on the User-Agent header.
## Explanation **Correct Answers: A and C** **A. Configure Amazon CloudFront to cache multiple versions of the content.** - This is correct because: - CloudFront is a content delivery network (CDN) that caches content at edge locations globally - It can cache different versions of content based on device detection - This improves performance by serving cached content from edge locations closer to users **C. Configure a Lambda@Edge function to send specific objects to users based on the User-Agent header.** - This is correct because: - Lambda@Edge allows running code at CloudFront edge locations - The User-Agent header contains information about the user's device/browser - Lambda@Edge can inspect the User-Agent header and serve different content versions accordingly - This enables dynamic content adaptation based on device type **Why other options are incorrect:** **B. Configure a host header in a Network Load Balancer to forward traffic to different instances.** - Incorrect because: - Network Load Balancer (NLB) operates at Layer 4 (transport layer) and doesn't inspect HTTP headers like host headers - Host-based routing is a feature of Application Load Balancer (ALB), not NLB - The scenario already uses an Elastic Load Balancer (likely ALB), but device detection requires more than host-based routing **D. Configure AWS Global Accelerator. Forward requests to a Network Load Balancer (NLB). Configure the NLB to set up host-based routing to different EC2 instances.** - Incorrect because: - Global Accelerator improves performance by routing traffic over AWS's global network - However, NLB doesn't support host-based routing (that's an ALB feature) - This solution doesn't address device detection requirements **E. Configure AWS Global Accelerator. Forward requests to a Network Load Balancer (NLB). Configure the NLB to set up path-based routing to different EC2 instances.** - Incorrect because: - Similar to option D, NLB doesn't support path-based routing - Path-based routing is an ALB feature - This approach doesn't solve the device detection problem **Key Concepts:** 1. **CloudFront + Lambda@Edge** is the optimal solution for global content delivery with device-specific adaptations 2. **User-Agent header** contains device information that can be used for content adaptation 3. **NLB vs ALB**: NLB operates at Layer 4 (TCP/UDP), while ALB operates at Layer 7 (HTTP/HTTPS) with header inspection capabilities 4. **Global Accelerator** is for improving network performance, not for content adaptation based on device type
Ultimate access to all questions.
No comments yet.
Author: LeetQuiz Editorial Team
A company recently announced the deployment of its retail website to a global audience. The website runs on multiple Amazon EC2 instances behind an Elastic Load Balancer. The instances run in an Auto Scaling group across multiple Availability Zones.
The company wants to provide its customers with different versions of content based on the devices that the customers use to access the website.
Which combination of actions should a solutions architect take to meet these requirements? (Choose two.)
A
Configure Amazon CloudFront to cache multiple versions of the content.
B
Configure a host header in a Network Load Balancer to forward traffic to different instances.
C
Configure a Lambda@Edge function to send specific objects to users based on the User-Agent header.
D
Configure AWS Global Accelerator. Forward requests to a Network Load Balancer (NLB). Configure the NLB to set up host-based routing to different EC2 instances.
E
Configure AWS Global Accelerator. Forward requests to a Network Load Balancer (NLB). Configure the NLB to set up path-based routing to different EC2 instances.