Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam DVA-C02 Topic 3 Question 37 Discussion

Actual exam question for Amazon's DVA-C02 exam
Question #: 37
Topic #: 3
[All DVA-C02 Questions]

A developer is creating an AWS Lambda function. The Lambda function needs an external library to connect to a third-party solution The external library is a collection of files with a total size of 100 MB The developer needs to make the external library available to the Lambda execution environment and reduce the Lambda package space

Which solution will meet these requirements with the LEAST operational overhead?

Show Suggested Answer Hide Answer
Suggested Answer: A

Lambda Layers:These are designed to package dependencies that you can share across functions.

How to Use:

Create a layer, upload your 100MB library as a zip.

Attach the layer to your function.

In your function code, import the library from the standard layer path.


Lambda Layers:https://docs.aws.amazon.com/lambda/latest/dg/configuration-layers.html

Contribute your Thoughts:

Loise
7 days ago
Can you imagine if the developer just tried to include the entire 100MB library directly in the Lambda function's code? Talk about a bloated package!
upvoted 0 times
...
Carmelina
16 days ago
I'm not sure, but I think option D could also work. Mounting an EFS volume in the Lambda function might be a good approach.
upvoted 0 times
...
Lorean
17 days ago
I agree with Staci. Using a Lambda layer seems like the most efficient way to handle the external library.
upvoted 0 times
...
Staci
20 days ago
I think option A is the best solution.
upvoted 0 times
...
Reena
27 days ago
Option D with EFS is an interesting choice, but it might be overkill for a 100MB library. Layers or S3 seem like more straightforward solutions to me.
upvoted 0 times
Wei
7 days ago
A: I think option A with Lambda layers is the way to go. It's simple and efficient.
upvoted 0 times
...
...
Lindy
28 days ago
Option C looks tempting, but I'm worried about the potential performance impact of loading the library from the /tmp directory during deployment. Better to keep it separate in my opinion.
upvoted 0 times
...
Cordell
30 days ago
I'd go with Option B. Storing the library in S3 and mounting the folder in the Lambda function seems like a good way to keep things modular and maintainable.
upvoted 0 times
...
Noah
1 months ago
Option A seems like the easiest way to go. Layers are designed for this exact use case, and it should reduce the deployment package size.
upvoted 0 times
Dominga
6 days ago
D) Create an Amazon Elastic File System (Amazon EFS) volume. Upload the external library to the EFS volume Mount the EFS volume in the Lambda function. Import the library by using the proper folder in the mount point.
upvoted 0 times
...
Trina
8 days ago
A sounds like the best option. It's straightforward and should help keep the Lambda package size down.
upvoted 0 times
...
Tyra
10 days ago
B) Create an Amazon S3 bucket Upload the external library into the S3 bucket. Mount the S3 bucket folder in the Lambda function Import the library by using the proper folder in the mount point.
upvoted 0 times
...
Ona
23 days ago
A) Create a Lambda layer to store the external library Configure the Lambda function to use the layer
upvoted 0 times
...
...

Save Cancel