A company runs a web application across multiple Amazon EC2 instances that are distributed across several Availability Zones. The application needs to share a common set of configuration files and static assets that must be accessible concurrently and consistently from all instances. The company wants a fully managed, scalable file storage solution that does not require provisioning or managing underlying storage hardware. Which AWS service should the company use?
Correct. Amazon EFS provides a fully managed NFS file system that can be mounted on multiple EC2 instances across multiple Availability Zones simultaneously. It scales automatically and is designed for high availability and durability, making it ideal for shared file access.
Why this answer
Amazon EFS provides a fully managed, scalable, and shared file system that can be mounted concurrently by multiple EC2 instances across different Availability Zones. It uses the NFSv4.1 protocol, ensuring consistent access to configuration files and static assets without any provisioning or management of underlying storage hardware.
Exam trap
The trap here is that candidates often confuse Amazon S3's object storage capabilities with a shared file system, overlooking that S3 does not support POSIX file locking or concurrent mount-based access required for shared configuration files across EC2 instances.
Why the other options are wrong
Amazon EBS provides block-level storage volumes for use with a single EC2 instance, not shared concurrent access across multiple instances in different Availability Zones. It requires provisioning and managing storage hardware, and does not offer a fully managed, scalable file system for shared access.
Amazon S3 is an object storage service, not a file system. It does not provide a POSIX-compliant file system interface or support concurrent file-level locking, making it unsuitable for applications that require shared, consistent access to configuration files and static assets across multiple EC2 instances.
Amazon RDS is a managed relational database service, not a file storage solution. It cannot be used to share configuration files and static assets across EC2 instances as a shared file system.