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 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

Contribute your Thoughts:

Johnna
2 days 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
8 days 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
13 days 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
19 days 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
24 days 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
1 month 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