Since no code change is permitted, below choice makes sense for the unix server's file sharing: C. Create an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system on all web servers.

Rehost the application webservers on EC2 and Create an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system on all web servers.

Since no code change is permitted, below choice makes sense for the unix server's file sharing:

Since no code change is permitted, below choice makes sense for the unix server's file sharing:

C is correct.

This solution satisfies the needs in the following ways: • EFS provides a fully managed elastic network file system that can be mounted on multiple EC2 instances concurrently. • The EFS file system appears as a standard file system mount on the Linux web servers, requiring no application changes. The servers can access shared files as if they were on local storage. • EFS is highly available, durable, and scalable, providing a robust shared storage solution.

No application changes are allowed and EFS is compatible with Linux

C is the answer: Create an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system on all web servers. To meet the requirements of providing a shared file store for Linux-based web servers without making changes to the application, using an Amazon EFS file system is the best solution. Amazon EFS is a managed NFS file system service that provides shared access to files across multiple Linux-based instances, which makes it suitable for this use case. Amazon S3 is not ideal for this scenario since it is an object storage service and not a file system, and it requires additional tools or libraries to mount the S3 bucket as a file system. Amazon CloudFront can be used to improve content delivery performance but is not necessary for this requirement. Additionally, Amazon EBS volumes can only be mounted to one instance at a time, so it is not suitable for sharing files across multiple instances.