Which solution will meet these requirements?
Create a mount target for the EFS file system in the VPC. Use the mount target to mount the file system on each of the instances.
Create a mount target for the EFS file system in one Availability Zone of the VPC. Use the mount target to mount the file system on the instances in that Availability Zone. Share the directory with the other instances.
Create a mount target for each instance. Use each mount target to mount the EFS file system on each respective instance.
Create a mount target in each Availability Zone of the VPC. Use the mount target to mount the EFS file system on the instances in the respective Availability Zone.
Explanations:
While creating a mount target for the EFS file system in the VPC allows access to the file system, it does not specify the need for multiple mount targets across different Availability Zones. This could lead to higher latency for instances located in different zones due to potential cross-zone traffic.
Creating a mount target in only one Availability Zone limits access to only the instances in that zone, causing higher latency for instances in other zones. This setup does not provide optimal access to the EFS file system across multiple Availability Zones.
Creating a mount target for each instance is unnecessary and inefficient. EFS is designed to be accessed by multiple instances simultaneously through shared mount targets, making this approach overly complex and not optimal for latency.
Creating a mount target in each Availability Zone ensures that each instance can access the EFS file system with the lowest possible latency, as the mount targets are located closer to the instances. This setup optimally supports high availability and low-latency access across multiple zones.
I structure that the answer is:
Create a mount target in each Availability Zone of the VPC. Use the mount target to mount the EFS file system on the instances in the respective Availability Zone.