New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon DVA-C02 Exam - 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:

0/2000 characters
Yvonne
3 months ago
A is the best option for reducing package size with minimal hassle!
upvoted 0 times
...
Barrett
3 months ago
C seems like a hacky solution, not ideal for production.
upvoted 0 times
...
Regenia
3 months ago
Wait, can you really use EFS with Lambda? That sounds complicated.
upvoted 0 times
...
Miles
4 months ago
I disagree, B could work too, especially for larger libraries.
upvoted 0 times
...
Lilli
4 months ago
A is definitely the way to go! Lambda layers are super convenient.
upvoted 0 times
...
Laila
4 months ago
EFS sounds like a good option for larger files, but I remember it can be more complex to set up. I wonder if the operational overhead is really the least with option D.
upvoted 0 times
...
Shawna
4 months ago
I vaguely recall that the /tmp directory has size limitations, so option C might not be ideal for a 100 MB library. It seems risky.
upvoted 0 times
...
Muriel
4 months ago
I'm not entirely sure, but I think using S3 could add more complexity than necessary. I feel like we practiced a similar question where layers were the answer.
upvoted 0 times
...
Suzi
5 months ago
I remember discussing Lambda layers in class, and I think they are designed specifically for this kind of situation. So, option A seems like the best choice.
upvoted 0 times
...
Franchesca
5 months ago
I'm not sure about the performance implications of mounting an S3 bucket or EFS volume in the Lambda function. Option C with the /tmp directory might be the most efficient in terms of execution time.
upvoted 0 times
...
Wynell
5 months ago
I'm leaning towards Option D with the Amazon EFS volume. That way the library is stored in a separate, scalable storage system and can be easily accessed by the Lambda function.
upvoted 0 times
...
Bulah
5 months ago
Option A with the Lambda layer seems like the simplest and most straightforward solution. It keeps the library separate from the Lambda function code and should be easy to manage.
upvoted 0 times
...
Gearldine
5 months ago
This looks like a pretty straightforward AWS Lambda question. I think the key is to find the solution that minimizes operational overhead while still meeting the requirements.
upvoted 0 times
...
Madelyn
5 months ago
Hmm, I'm a bit confused about the different options here. I'm not sure which one would have the least operational overhead. I'll need to think this through carefully.
upvoted 0 times
...
Evangelina
5 months ago
I think 3D privacy masking might refer to how the mask changes shape, like option B. I'm not entirely sure though.
upvoted 0 times
...
Loise
1 year 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
Kina
1 year ago
C: It's important to optimize the package size to improve performance and reduce operational overhead.
upvoted 0 times
...
Jackie
1 year ago
B: That would definitely help reduce the Lambda package size and keep things organized.
upvoted 0 times
...
Ocie
1 year ago
A: A) Create a Lambda layer to store the external library Configure the Lambda function to use the layer
upvoted 0 times
...
...
Carmelina
1 year 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
1 year ago
I agree with Staci. Using a Lambda layer seems like the most efficient way to handle the external library.
upvoted 0 times
...
Staci
1 year ago
I think option A is the best solution.
upvoted 0 times
...
Reena
1 year 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
Cordelia
1 year ago
C: Yeah, I think using the /tmp directory during deployment is a bit messy. Layers or S3 would be cleaner solutions.
upvoted 0 times
...
Sarina
1 year ago
B: I agree, using S3 also seems like a good option for this scenario.
upvoted 0 times
...
Wei
1 year ago
A: I think option A with Lambda layers is the way to go. It's simple and efficient.
upvoted 0 times
...
...
Lindy
1 year 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
1 year 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 year 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
1 year 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
1 year ago
A sounds like the best option. It's straightforward and should help keep the Lambda package size down.
upvoted 0 times
...
Tyra
1 year 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
1 year ago
A) Create a Lambda layer to store the external library Configure the Lambda function to use the layer
upvoted 0 times
...
...

Save Cancel