Back to AWS Lambda

Lambda@Edge

5 minutes 5 Questions

Lambda@Edge is an extension of the AWS Lambda service that allows you to execute serverless functions at edge locations closer to your users. This reduces latency and enables you to perform real-time processing of HTTP requests and responses, tailoring the content delivered to users based on factor…

Test mode:
Start practice test
AWS Certified Solutions Architect - Lambda@Edge Example Questions

Test your knowledge of Lambda@Edge

Question 1

You are deploying a new Lambda@Edge function, but the deployment process fails consistently. After investigation, you discover that the function size is 55MB. What changes should you make to successfully deploy your Lambda@Edge function?

Correct Answer: Reduce code package size to 50MB or less

Lambda@Edge deployment restrictions include a maximum unzipped package size of 50MB. Reducing the package size to 50MB or less will solve the issue. The other options don't address the size limitation.

Question 2

You are required to serve different content types (HTML, CSS, Images) from the same Amazon S3 bucket using CloudFront and Lambda@Edge. How should you design the system?

Correct Answer: At the origin-request event, inspect Accept header and rewrite the URI to fetch the appropriate content file from the S3 bucket

Lambda@Edge supports rewriting the S3 object's URI at the 'origin-request' event, which can be used to fetch different content types from the same S3 bucket. The other alternatives involve creating multiple infrastructure components or modifying the URI at incorrect events.

Question 3

You are designing a content delivery system that uses CloudFront and Lambda@Edge. The application should process requests from different regions and serve geo-targeted content to users. Which Lambda@Edge event can be most efficiently used to implement this requirement?

Correct Answer: viewer-request

The 'viewer-request' event in Lambda@Edge allows for decision-based content processing and serves content specific to users' locations. The other events mentioned either happen after the content has been processed or are not valid Lambda@Edge events.

More Lambda@Edge questions
15 questions (total)
Start 15 question test