AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company runs multiple Amazon EC2 Linux instances in a VPC across two Availability Zones. The instances host applications that use a hierarchical directory structure. The applications need to read and write rapidly and concurrently to shared storage.
What should a solutions architect do to meet these requirements?
Other
Community
UAnonymous
A
Create an Amazon S3 bucket. Allow access from all the EC2 instances in the VPC.
B
Create an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system from each EC2 instance.
C
Create a file system on a Provisioned IOPS SSD (io2) Amazon Elastic Block Store (Amazon EBS) volume. Attach the EBS volume to all the EC2 instances.
D
Create file systems on Amazon Elastic Block Store (Amazon EBS) volumes that are attached to each EC2 instance. Synchronize the EBS volumes across the different EC2 instances.
Explanation:
Explanation
Correct Answer: B - Create an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system from each EC2 instance.
Why EFS is the Best Solution:
-
Hierarchical Directory Structure: EFS provides a fully managed, scalable file system with a hierarchical directory structure, which is exactly what the applications require.
-
Concurrent Access: EFS supports concurrent access from multiple EC2 instances across multiple Availability Zones. Multiple instances can read and write to the same file system simultaneously.
-
Shared Storage: EFS is designed as a shared file storage service that can be mounted on multiple EC2 instances at the same time.
-
Rapid Read/Write: EFS provides low-latency performance suitable for applications that need rapid access to shared files.
-
Multi-AZ Deployment: The requirement mentions instances across two Availability Zones, and EFS can be accessed from instances in different AZs within the same region.
Why Other Options Are Incorrect:
A. Amazon S3:
- S3 is an object storage service, not a file system with hierarchical directory structure
- S3 doesn't provide the same file system semantics (POSIX compliance) that applications typically need
- Not designed for rapid concurrent read/write operations like a file system
C. Provisioned IOPS EBS Volume:
- EBS volumes can only be attached to one EC2 instance at a time (except for io2 Block Express volumes with specific configurations)
- Cannot be shared concurrently across multiple instances
- Would require complex clustering solutions for shared access
D. Multiple EBS Volumes with Synchronization:
- Would require complex synchronization mechanisms
- Could lead to data consistency issues
- Not a true shared storage solution
- Adds operational overhead and potential for conflicts
Key AWS Service Characteristics:
- EFS: Shared file system, POSIX-compliant, multi-AZ access, elastic scaling
- EBS: Block storage, single-instance attachment (generally), persistent storage
- S3: Object storage, HTTP/HTTPS access, eventual consistency model
For applications requiring concurrent access to shared file storage with hierarchical directory structure across multiple instances in different AZs, Amazon EFS is the most appropriate and fully managed solution.
Comments
Loading comments...