Examkin

Question

Difficulty: MediumResilient and Highly Available Storage Infrastructure

A fintech enterprise hosts a containerized loan processing platform on Amazon ECS across three Availability Zones. The platform generates and modifies loan agreements that must be concurrently accessible by multiple containers in an active-active configuration. The platform's disaster recovery SLA requires a Recovery Point Objective (RPO) of 44 hours and a Recovery Time Objective (RTO) of 11 hour. The storage solution must be highly resilient, durable, and support automatic failover across all three Availability Zones. Which combination of storage and backup configurations should a solutions architect implement to meet these requirements? (Select TWO.)

  1. Configure an Amazon EFS file system using the Regional storage class, and mount it on the Amazon ECS tasks across all three Availability Zones.Answer
  2. Create an AWS Backup plan with a backup rule that runs every 44 hours, backing up the filesystem to a backup vault.Answer
  3. C
    Provision Amazon EBS volumes with Multi-Attach enabled and mount the volumes to the ECS tasks across all three Availability Zones.
  4. D
    Archive the agreements to Amazon S3 Glacier Flexible Retrieval and use Standard retrieval to recover the data in the event of storage failure.
  5. E
    Deploy a Pilot Light environment in a secondary AWS Region with active, scaled-down ECS tasks running continuously to ensure near-zero recovery time for the shared storage during failover.

Answer

The correct configurations are mounting a Regional Amazon EFS file system on the ECS tasks and implementing an AWS Backup plan with a 44-hour schedule.
Mounting a Regional Amazon EFS file system provides concurrent, active-active file access across multiple Availability Zones, ensuring high availability and durability. Setting up AWS Backup to run every 44 hours ensures that recovery points are created frequently enough to satisfy the 44-hour RPO, and restores from AWS Backup can be completed well within the 11-hour RTO.

Step-by-Step Solution

1
Analyze shared storage and concurrency requirements across multiple Availability Zones.
Amazon EFS is selected because it supports active-active concurrent file access across multiple AZs, unlike Amazon EBS which is restricted to a single AZ or lacks multi-mount capabilities across AZs.
This establishes the high availability foundation required by the containerized ECS application.
2
Evaluate the RPO requirement of 44 hours.
AWS Backup is configured to take backups of the EFS filesystem every 44 hours.
This guarantees that the maximum data loss in a disaster scenario will not exceed the 44-hour threshold.
3
Evaluate the RTO requirement of 11 hour.
Confirming EFS restores via AWS Backup are fast enough to meet the 11-hour window, while rejecting Glacier Standard retrieval which takes 33 to 55 hours.
This ensures the recovery time remains within the SLA limits.

Key Concept

Designing highly available, multi-AZ shared file systems using Amazon EFS coupled with AWS Backup to meet specific RPO and RTO compliance metrics.
Rate this question

Topics

Resilient and Highly Available Storage Infrastructure

More questions from this topic