DVA-C02 · Question #614
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
The correct answer is C. Configure the function to use ephemeral storage. Upload the objects and process data in the /tmp. Configuring the Lambda function to use ephemeral storage and processing data in the /tmp directory improves performance by leveraging local storage during execution. Ephemeral Storage: Lambda provides temporary storage (up to 10 GB) in the /tmp directory for each invocation, whic
Question
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?
Options
- AStore the data in an Amazon EFS file system. Mount the file system to a local directory in the
- BCreate an Amazon EventBridge rule to schedule invocations of the function every minute.
- CConfigure the function to use ephemeral storage. Upload the objects and process data in the /tmp
- DCreate a Lambda layer to package the function dependencies. Add the layer to the function.
How the community answered
(45 responses)- A11% (5)
- B22% (10)
- C62% (28)
- D4% (2)
Explanation
Configuring the Lambda function to use ephemeral storage and processing data in the /tmp directory improves performance by leveraging local storage during execution. 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.
Community Discussion
No community discussion yet for this question.