AWS Certified Developer – Associate (DVA-C02) — Question 409

A developer has AWS Lambda functions that need to access a company's internal data science libraries and reference data. Separate teams manage the libraries and the data. The teams must be able to update and upload new data independently. The Lambda functions are connected to the company's central VPC.

Which solution will provide the Lambda functions with access to the libraries and data?

Answer options

• A. Attach an Amazon Elastic Block Store (Amazon EBS) volume to the Lambda functions by using EBS Multi-Attach in the central VPC. Update the Lambda function execution roles to give the functions to access the EBS volume. Update the Lambda function code to reference the files in the EBS volume.
• B. Compress the libraries and reference data in a Lambda /tmp folder. Update the Lambda function code to reference the files in the /tmp folder.
• C. Set up an Amazon Elastic File System (Amazon EFS) file system with mount targets in the central VPConfigure the Lambda functions to mount the EFS file system. Update the Lambda function execution roles to give the functions to access the EFS file system.
• D. Set up an Amazon FSx for Windows File Server file system with mount targets in the central VPC. Configure the Lambda functions to mount the Amazon FSx file system. Update the Lambda function execution roles to give the functions to access the Amazon FSx file system.

Correct answer: C

Explanation

Amazon EFS natively integrates with AWS Lambda, allowing functions to mount a shared file system securely within a VPC where multiple teams can independently update files. Amazon EBS volumes cannot be attached to AWS Lambda functions, and Lambda does not natively support mounting Amazon FSx for Windows File Server. The local /tmp directory is ephemeral and not designed for concurrent, independent updates by external teams.