Exam AWS-SysOps topic 1 question 603 discussion

Agree C is correct. Look at the requirements: - Multiple EC2 Instances use >> NFS Share - Consistent view of persistent data >> Requires data consistency. - Read frequently >> High I/O - Items will be expired according to age and content type >> Lifecycle schedule Multiple Amazon EC2 instances can access an Amazon EFS file system at the same time, providing a common data source for workloads and applications running on more than one instance or server. Amazon EFS provides file system access semantics, such as strong data consistency and file locking >> So changes can be done without conflict. Amazon EFS is designed to provide the throughput, IOPS, and low latency needed for a broad range of workloads. https://docs.aws.amazon.com/efs/latest/ug/whatisefs.html Amazon EFS lifecycle management automatically manages cost-effective file storage for your file systems. When enabled, lifecycle management migrates files that have not been accessed for a set period of time to the Infrequent Access (IA) storage class. https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html

Reviewed the question again, EFS makes more sense https://dzone.com/articles/confused-by-aws-storage-options-s3-ebs-amp-efs-explained You can mount EFS onto several EC2 instances at the same time.

Amazon EFS (Elastic File System) provides a scalable and managed file storage service that can be mounted to multiple EC2 instances concurrently. It offers a consistent view of the file system data across instances, making it suitable for applications that require a consistent view of persistent data.

S3 now also support strong consistency. So this question need to be updated by AWS.

Correct Answer: C often require partial changes without conflict => EFS

C is the answer

Answer is "C" Fleet of EC2 instances with high I/O means EFS is best choice.

C. Amazon EFS and a scheduled process to delete files based on age and extension.

A. Amazon S3 buckets with lifecycle policies to delete old objects. - WRONG as Conflicting Consistency B. Amazon RDS PostgreSQL and a job that deletes rows based on age and file type columns. - WRONG (varying sizes suggest unstructured data) C. Amazon EFS and a scheduled process to delete files based on age and extension. - CORRECT D. An EC2 instance store synced on boot from a central Amazon EBS-backed instance. - Not Persistent

Not A - Lifecycle policies just work on age, not on content/age Not B - The varying sizes suggest this isnt structured data that would fit well in PostgreSQL Not D - This works well for READ activities, but not Write/Update Only option is C

I'll go with C

C. Amazon EFS and a scheduled process to delete files based on age and extension.

How about B

C: keywords here multiple instances, persistent storage, read frequently

C is correct The question says a "fleet" of EC2 instances

it says "...and content type" so C

I think C is correct one