Multiple AWS Lambda functions require access to internal data science libraries and reference datasets. Different teams manage the libraries and the data and must be able to update them independently. The Lambda functions run in the company's central VPC. Which solution provides the Lambda functions access to the libraries and data?

Amazon EFS is the correct solution because it provides a scalable, shared file system that multiple Lambda functions can access concurrently. EFS mount targets can be placed within the central VPC, allowing Lambda functions configured for VPC access to seamlessly connect. The independent management of libraries and data by different teams is supported as EFS allows for granular permissions and updates to the file system without redeploying Lambda functions. EBS Multi-Attach is incorrect because EBS volumes are block storage, typically attached to EC2 instances, not directly to Lambda functions. The /tmp directory is incorrect because it's ephemeral, limited to 512 MB, and not suitable for persistent storage or sharing across multiple Lambda invocations or functions. Amazon FSx for Windows File Server is incorrect as it's designed for Windows-based workloads and not the most appropriate or cost-effective solution for Linux-based Lambda functions.