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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon DVA-C02 Exam - Topic 3 Question 56 Discussion

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

A developer created an AWS Lambda function to process data in an application. The function pulls large objects from an Amazon S3 bucket, processes the data, and loads the processed data into a second S3 bucket. Application users have reported slow response times. The developer checks the logs and finds that Lambda function invocations run much slower than expected. The function itself is simple and has a small deployment package. The function initializes quickly. The developer needs to improve the performance of the application. Which solution will meet this requirement with the LEAST operational overhead?

Show Suggested Answer Hide Answer
Suggested Answer: C

Configuring the Lambda function to use ephemeral storage and processing data in the /tmp directory improves performance by leveraging local storage during execution.

Why Option C is Correct:

Ephemeral Storage: Lambda provides temporary storage (up to 10 GB) in the /tmp directory for each invocation, which is faster than pulling data directly from S3 multiple times.

Performance Boost: Data can be downloaded to /tmp, processed locally, and uploaded to the destination S3 bucket, minimizing S3 network calls.

Low Overhead: This approach requires only minimal changes to the function's configuration.

Why Not Other Options:

Option A: Using Amazon EFS adds complexity and is unnecessary for this use case.

Option B: Scheduling the function does not address the root cause of slow performance.

Option D: Lambda layers improve deployment efficiency, not runtime performance for this scenario.


Using Ephemeral Storage in AWS Lambda

Best Practices for S3 and Lambda Performance

by Francisca at Oct 13, 2025, 01:06 PM

Limited Time Offer

25%

Off

Get Premium DVA-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Eleni
9 days ago
True, C has the least overhead. Let's go with that!
upvoted 0 times
...
Franklyn
14 days ago
But D still requires management. C is simpler.
upvoted 0 times
...
Shakira
19 days ago
I feel like D could help too. Layers can optimize dependencies.
upvoted 0 times
...
Kent
24 days ago
Option A seems heavy. EFS adds complexity.
upvoted 0 times
...
Valda
30 days ago
Totally agree with C, using /tmp can really speed things up!
upvoted 0 times
...
Ilene
1 month ago
Surprised that no one mentioned optimizing the code itself!
upvoted 0 times
...
Skye
1 month ago
D could help with dependencies, but is it really the best for performance?
upvoted 0 times
...
Hana
2 months ago
I think A might add more complexity than needed.
upvoted 0 times
...
Goldie
2 months ago
D) sounds like a good idea, but I think C) is the most straightforward solution.
upvoted 0 times
...
Kenny
2 months ago
Haha, I bet the developer wishes they had a magic wand to fix this performance issue!
upvoted 0 times
...
Carey
2 months ago
Hmm, I'm not sure. Storing the data in EFS might be a better long-term solution.
upvoted 0 times
...
Ahmad
2 months ago
I'm a bit confused on the best way to approach this. I'd want to do some more research on the tradeoffs of each option before deciding. Performance optimization can be tricky, so I'd want to make sure I fully understand the implications of each solution.
upvoted 0 times
...
Naomi
2 months ago
Option C sounds like a solid choice for speed!
upvoted 0 times
...
Elbert
3 months ago
I agree, C) seems like the best option to reduce overhead.
upvoted 0 times
...
Merri
3 months ago
I agree, C makes sense. It reduces latency by using /tmp.
upvoted 0 times
...
Deonna
3 months ago
I think option C is the best. Using ephemeral storage can speed things up.
upvoted 0 times
...
Denny
3 months ago
C) is the way to go. Using the /tmp directory is a great way to improve performance.
upvoted 0 times
...
Amber
3 months ago
I like the idea of using a Lambda layer for the dependencies. That could help streamline the function and reduce the overall package size. Might be worth trying that in combination with the /tmp directory approach.
upvoted 0 times
...
Ocie
4 months ago
The /tmp directory approach sounds promising. If the function is simple and the deployment package is small, that could be a good way to leverage the ephemeral storage and avoid the overhead of EFS or other external storage.
upvoted 0 times
...
Johnna
4 months ago
Hmm, I'm not sure about the EventBridge option. Scheduling invocations doesn't seem like it would address the root cause of the slow performance. I'd want to dig deeper into the function itself.
upvoted 0 times
...
Lizbeth
4 months ago
This is a tricky one. I'd want to look closely at the function's performance metrics to see where the bottleneck is. Storing data in EFS could help, but that might add more complexity than needed.
upvoted 0 times
...
Alease
4 months ago
I recall that Lambda layers are useful for managing dependencies, but I don’t think they directly improve performance. I wonder if that’s the right approach for this scenario.
upvoted 0 times
...
Starr
4 months ago
I’m leaning towards option C because it allows for temporary storage during execution, but I’m not entirely confident if it will significantly speed things up.
upvoted 0 times
...
Virgina
5 months ago
I think I practiced a similar question where we had to optimize Lambda performance. Using Amazon EFS seemed like a good choice, but it might add more complexity than just using the /tmp directory.
upvoted 0 times
...
Quentin
5 months ago
I remember reading about using ephemeral storage for Lambda functions. It might help with processing larger objects more efficiently, but I'm not completely sure if it’s the best option here.
upvoted 0 times
...

Save Cancel