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 solutions architect needs to design a system to store client case files. The files are core company assets and are important. The number of files will grow over time. The files must be simultaneously accessible from multiple application servers that run on Amazon EC2 instances. The solution must have built-in redundancy. Which solution meets these requirements?
Other
Community
UAnonymous
A
Amazon Elastic File System (Amazon EFS)
B
Amazon Elastic Block Store (Amazon EBS)
C
Amazon S3 Glacier Deep Archive
D
AWS Backup
Explanation:
Explanation
Amazon Elastic File System (Amazon EFS) is the correct solution because:
-
Simultaneous access from multiple EC2 instances: Amazon EFS provides a shared file system that can be mounted concurrently by multiple EC2 instances across multiple Availability Zones. This is a key requirement for the client case files that need to be accessible from multiple application servers.
-
Built-in redundancy: Amazon EFS is designed with built-in redundancy and high availability. It stores data and metadata across multiple Availability Zones within an AWS Region, providing automatic failover and data durability.
-
Scalability: EFS automatically scales storage capacity up or down as files are added or removed, meeting the requirement that "the number of files will grow over time."
-
File system semantics: EFS provides standard file system semantics, making it suitable for storing important client case files that need to be accessed like regular files.
Why the other options are incorrect:
-
B. Amazon Elastic Block Store (Amazon EBS): EBS volumes are block storage devices that can only be attached to a single EC2 instance at a time. They do not support simultaneous access from multiple EC2 instances.
-
C. Amazon S3 Glacier Deep Archive: This is a low-cost archival storage class designed for long-term data retention with retrieval times of 12 hours. It's not suitable for active file access from multiple application servers.
-
D. AWS Backup: This is a backup service for centralizing and automating data protection across AWS services. It's not a primary storage solution for active file access.
Key AWS Services Comparison:
| Service | Multiple EC2 Access | Built-in Redundancy | Use Case |
|---|---|---|---|
| Amazon EFS | ✅ Yes | ✅ Yes | Shared file storage across multiple instances |
| Amazon EBS | ❌ No (single instance) | ✅ Yes (with replication) | Block storage for single instances |
| S3 Glacier | ❌ No | ✅ Yes | Long-term archival storage |
| AWS Backup | ❌ No | ✅ Yes | Backup and recovery service |
Comments
Loading comments...