Examkin

Question

Difficulty: Very hardResilient and Highly Available Storage Infrastructure

A maritime fleet management company is designing a high-availability telemetry processing system on AWS. The application runs on Amazon ECS containers across multiple Availability Zones in the primary region (`eu-west-1`). The containers require concurrent read/write access to a shared POSIX-compliant file system. The architecture must support a multi-region disaster recovery (DR) plan in `eu-central-1` with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 10 minutes. During failover, the file system in the recovery region must be immediately writable without latency or performance degradation. Which combination of configurations will meet these requirements? (Select TWO.)

  1. Create an Amazon Elastic File System (Amazon EFS) file system in `eu-west-1` using the Regional storage class, and configure Amazon EFS Replication to a destination file system in `eu-central-1`.Answer
  2. In the disaster recovery region (`eu-central-1`), configure the ECS task definitions to mount the replica EFS file system using its native mount target when initiating failover.Answer
  3. C
    Store the telemetry files in Amazon S3 in `eu-west-1`, configure S3 Cross-Region Replication (CRR) to an S3 Glacier Flexible Retrieval bucket in `eu-central-1`, and use Standard retrievals during failover.
  4. D
    Implement a Pilot Light disaster recovery strategy by deploying active, fully running ECS tasks in `eu-central-1` that continuously mount the `eu-west-1` EFS file system via an inter-region VPC peering connection.
  5. E
    Configure an Amazon Aurora PostgreSQL Global Database with write forwarding enabled in the primary database cluster in `eu-west-1` to act as the shared POSIX-compliant mount target for the ECS containers.

Answer

Deploying an Amazon EFS file system in the primary region with replication configured to the secondary region, and configuring the secondary region's ECS tasks to mount the replicated EFS file system.
Deploying Amazon EFS with native replication guarantees that files are automatically copied across regions with low latency, satisfying the 15-minute RPO. In the event of a failover, mounting the local replicated file system in the secondary region allows ECS containers to start up and begin executing operations instantly, comfortably staying within the 10-minute RTO.

Step-by-Step Solution

1
Determine the storage access requirement.
The application requires concurrent read/write POSIX-compliant access, which makes Amazon Elastic File System (EFS) the ideal choice over object storage or block storage.
Amazon EFS supports concurrent access from multiple container instances and complies with standard POSIX directory structures and permissions.
2
Assess replication and RPO compliance.
Enable Amazon EFS Replication from the primary region to the disaster recovery region.
EFS Replication transfers data asynchronously across regions and typically updates the replica within minutes, satisfying the 15-minute RPO.
3
Determine recovery procedures to meet the RTO.
Configure ECS container tasks in the secondary region to mount the replicated EFS file system.
When a failover occurs, the secondary EFS is immediately available for read and write operations. The ECS tasks can mount the local replica with minimal latency, ensuring the 10-minute RTO is met.

Key Concept

Multi-Region shared storage resilience utilizing Amazon EFS Replication to achieve low recovery metrics.
Rate this question

Topics

Resilient and Highly Available Storage Infrastructure

More questions from this topic