A company uses a service to collect metadata from applications that the company hosts on premises. Consumer devices such as TVs and internet radios access the applications. Many older devices do not support certain HTTP headers and exhibit errors when these headers are present in responses. The company has configured an on-premises load balancer to remove the unsupported headers from responses sent to older devices, which the company identified by the User-Agent headers. The company wants to migrate the service to AWS, adopt serverless technologies, and retain the ability to support the older devices. The company has already migrated the applications into a set of AWS Lambda functions. Which solution will meet these requirements?
Select one answer.
Marked answer: A
Community Discussion
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Chose A1
Option A - is most cost effective and fast compared to Lambda@Edge, It's over kill.
Chose D2
D. CloudFront + ALB + Lambda@Edge AWS Lambda@Edge can modify response headers dynamically based on User-Agent Works perfectly for conditional header removal at the edge Even though ALB is included, this design is commonly accepted in AWS exam context for Lambda integration Most importantly: meets the header manipulation requirement correctly
Chose D1
Amazon CloudFront + Lambda@Edge is the right combo. Lambda@Edge can: Inspect User-Agent Modify response headers Execute at viewer response phase Application Load Balancer can route to Lambda functions (serverless backend ) This exactly replicates the current behavior: Detect older devices via User-Agent Strip unsupported headers Serve clean responses
Keyboard:←→previous / next·A–Echoose·Entercheck, then next
