Question

Difficulty: MediumResilient and Highly Available Storage Infrastructure

An energy utility company's smart grid platform processes real-time telemetry from millions of meters. The ingestion layer runs on a fleet of Amazon EC2 instances distributed across three Availability Zones. This tier requires a shared, highly available file storage layer that supports concurrent read/write access. Additionally, the company must retain raw data logs for 77 years to meet regulatory compliance, with an administrative requirement to retrieve any archived log within 1515 minutes.

Which combination of AWS storage configurations will meet these requirements? (Select TWO.)

  1. Configure an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class to mount on the EC2 instances.Answer
  2. Store compliance logs in Amazon S3 and implement an S3 Lifecycle policy to transition objects to Amazon S3 Glacier Instant Retrieval.Answer
  3. C
    Provision an Amazon EBS gp3 volume with Multi-Attach enabled and mount it across all EC2 instances in the three Availability Zones.
  4. D
    Store compliance logs in Amazon S3 and implement an S3 Lifecycle policy to transition objects to Amazon S3 Glacier Deep Archive using standard retrieval.
  5. E
    Deploy an Amazon RDS Multi-AZ DB instance with read replicas in each Availability Zone to act as the shared file repository for the EC2 fleet.

Answer

The correct configurations are to mount an Amazon Elastic File System (Amazon EFS) file system using the EFS Standard storage class on the EC2 instances, and to store compliance logs in Amazon S3 with an S3 Lifecycle policy transitioning them to Amazon S3 Glacier Instant Retrieval.
The correct configurations involve using Amazon Elastic File System (Amazon EFS) and Amazon S3 Glacier Instant Retrieval. Amazon EFS provides a serverless, fully managed, shared file system that can be accessed concurrently by EC2 instances across multiple Availability Zones, ensuring high availability and resilience. For the archiving requirement, storing logs in Amazon S3 and transitioning them to Amazon S3 Glacier Instant Retrieval ensures the logs are cost-effectively stored for 77 years while maintaining the ability to retrieve them in milliseconds, meeting the RTO of 1515 minutes.

Step-by-Step Solution

1
Analyze the file sharing requirement for the compute tier.
The EC2 fleet is distributed across three Availability Zones and requires concurrent read/write access to a shared file system.
This establishes that a regional shared file storage service like Amazon EFS is required, as standard EBS volumes cannot be shared across multiple Availability Zones.
2
Evaluate the compliance log retention and retrieval requirements.
Logs must be stored for 77 years with a retrieval time limit (RTO) of 1515 minutes.
This eliminates cold archive options like S3 Glacier Deep Archive standard retrievals, which take up to 1212 hours, and directs the solution toward S3 Glacier Instant Retrieval which offers millisecond access.
3
Verify service compatibility and limitations for the selected options.
Amazon EFS natively supports multi-AZ concurrent mounts. Amazon S3 Glacier Instant Retrieval satisfies both the long-term archiving requirement and the low RTO retrieval requirement.
This confirms that combining Amazon EFS and S3 Glacier Instant Retrieval provides a highly available, resilient, and compliant architecture.

Key Concept

Designing a resilient, multi-AZ shared file storage layer combined with a compliant, fast-retrieval archive solution.
Estimated Time:2m 0s
Rate this question