Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 566 discussion

Correct B. How is Amazon EFS different than Amazon S3? Amazon EFS provides shared access to data using a traditional file sharing permissions model and hierarchical directory structure via the NFSv4 protocol. Applications that access data using a standard file system interface provided through the operating system can use Amazon EFS to take advantage of the scalability and reliability of file storage in the cloud without writing any new code or adjusting applications. Amazon S3 is an object storage platform that uses a simple API for storing and accessing data. Applications that do not require a file system structure and are designed to work with object storage can use Amazon S3 as a massively scalable, durable, low-cost object storage solution.

https://aws.amazon.com/efs/when-to-choose-efs/

hierarchical structure =EFS

Not A because S3 does not allow a "hierarchical directory structure" Not C because Multi-attach does not work "across two Availability Zones" Not D because we need "shared", not synchronized, storage.

hierarchical directory structure, read and write rapidly and concurrently to shared storage = Amazon Elastic File System

Amazon EFS simultaneously supports on-premises servers using a traditional file permissions model, file locking, and hierarchical directory structure through the NFS v4 protocol.

The key reasons: EFS provides a scalable, high performance NFS file system that can be concurrently accessed from multiple EC2 instances. It supports the hierarchical directory structure needed by the applications. EFS is elastic, growing and shrinking automatically as needed. It can be accessed from instances across AZs, meeting the shared storage requirement. S3 object storage (option A) lacks the file system semantics needed by the apps. EBS volumes (options C and D) are attached to a single instance and would require replication and syncing to share across instances. EFS is purpose-built for this use case of a shared file system across Linux instances and aligns best with the performance, concurrency, and availability needs.

Going with b

C and D involve using Amazon EBS volumes, which are block storage. While they can be attached to EC2 instances, they might not provide the same level of shared concurrent access as Amazon EFS. Additionally, synchronizing EBS volumes across different EC2 instances (as in option D) can be complex and error-prone. Therefore, for a scenario where multiple EC2 instances need to rapidly and concurrently access shared storage with a hierarchical directory structure, Amazon EFS is the best solution.

s3 is flat structure. EBS multi mount only for same available zone

Because Amazon EBS Multi-Attach enables you to attach a single Provisioned IOPS SSD (io1 or io2) volume to multiple instances that are in the same Availability Zone. The infra contains 2 AZ's.

B is the correct answer https://docs.aws.amazon.com/efs/latest/ug/whatisefs.html

B is the correct answer https://docs.aws.amazon.com/efs/latest/ug/whatisefs.html

I think that C is the best option coz io2 can share storage and multi attach.