DVA-C02 · Question #460
A developer adds new dependencies to an existing AWS Lambda function. The developer cannot deploy the Lambda function because the unzipped deployment package exceeds the maximum size quota for the…
The correct answer is D. Create and deploy a Lambda container image with all the dependencies. AWS Lambda supports deploying functions as container images, which allows developers to include larger dependencies or custom binaries. Container images can be up to 10 GB in size, which is significantly larger than the maximum size limit for zipped Lambda deployment packages…
Question
A developer adds new dependencies to an existing AWS Lambda function. The developer cannot deploy the Lambda function because the unzipped deployment package exceeds the maximum size quota for the Lambda function. The instruction set architecture of the Lambda function is x86_64. The developer must implement a solution to deploy the Lambda function with the new dependencies. Which solution will meet these requirements?
Options
- ACreate a snapshot of all the dependencies. Configure the Lambda function to use the snapshot.
- BChange the instruction set architecture of the Lambda function to use an arm64 architecture.
- CAssociate an Amazon Elastic Block Store (Amazon EBS) volume with the Lambda function. Store
- DCreate and deploy a Lambda container image with all the dependencies.
How the community answered
(28 responses)- A4% (1)
- B7% (2)
- C4% (1)
- D86% (24)
Explanation
AWS Lambda supports deploying functions as container images, which allows developers to include larger dependencies or custom binaries. Container images can be up to 10 GB in size, which is significantly larger than the maximum size limit for zipped Lambda deployment packages (250 MB). This solution enables the developer to package the Lambda function with all its dependencies and deploy it without exceeding the size limitations of traditional deployment
Community Discussion
No community discussion yet for this question.