Examkin

Question

Difficulty: Very hardDisaster Recovery Strategies

A company's production application runs in the us-east-1 Region. The application tier consists of stateless Amazon ECS tasks running on AWS Fargate behind an Application Load Balancer (ALB). The database tier uses a Multi-AZ Amazon Aurora PostgreSQL DB cluster. User documents are stored in an Amazon S3 bucket. A SysOps administrator must establish a disaster recovery (DR) strategy in the us-west-2 Region. The business requires a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 15 minutes while minimizing ongoing idle resource costs in the recovery region.

Which combination of actions will meet these requirements? (Select TWO.)

  1. Create an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Configure the secondary ECS service with a desired task count of zero, and use an AWS CloudFormation template to scale up the tasks during failover.Answer
  2. Enable S3 Versioning on both the source bucket in us-east-1 and the destination bucket in us-west-2, and configure Amazon S3 Cross-Region Replication (CRR) between the buckets.Answer
  3. C
    Set up a standard cross-region Aurora Read Replica in us-west-2. Rely on Amazon RDS automatic Multi-AZ failover to promote the cross-region replica and redirect application traffic during a regional outage.
  4. D
    Configure Amazon S3 Cross-Region Replication (CRR) from the source bucket to the destination bucket without enabling versioning on either bucket to minimize storage overhead.
  5. E
    Configure Amazon Route 53 with an active-active failover routing policy and associate health checks directly with the private database endpoints to automate regional traffic redirection.

Answer

Configure an Amazon Aurora Global Database for sub-second database replication, scale the recovery region's ECS Fargate tasks from zero to meet RTO cost-effectively, and configure Amazon S3 Cross-Region Replication with versioning enabled on both source and destination buckets.
Establishing an Amazon Aurora Global Database provides storage-level replication with lag under a second, meeting the 5-minute RPO. Keeping the ECS Fargate task desired count at zero minimizes idle compute costs, and the service can be scaled up quickly via CloudFormation templates or CLI commands to meet the 15-minute RTO limit during an actual failover. For static assets, configuring S3 Cross-Region Replication with versioning enabled on both source and destination buckets satisfies the replication requirements and ensures all files are safely copied to the recovery region.

Step-by-Step Solution

1
Configure database replication across regions.
Create an Aurora Global Database with the primary cluster in us-east-1 and the secondary in us-west-2 to meet the 5-minute RPO with storage-level replication.
Aurora Global Database replication lag is typically less than one second, which is well within the 5-minute RPO threshold.
2
Configure application tier scaling for disaster recovery.
Keep the ECS Fargate service task count in us-west-2 at zero during normal operations, and prepare a deployment workflow to scale tasks up when a failover occurs.
This Pilot Light strategy eliminates ongoing Fargate compute costs in the disaster recovery region while allowing tasks to launch within the 15-minute RTO.
3
Enable cross-region object replication.
Turn on S3 Versioning for both us-east-1 and us-west-2 buckets, then configure S3 Cross-Region Replication (CRR).
S3 Versioning is a strict prerequisite for S3 Cross-Region Replication.

Key Concept

Disaster recovery strategy design balancing RTO/RPO requirements and cost optimization using Aurora Global Databases, Pilot Light compute scaling, and S3 Cross-Region Replication.
Estimated Time:3m 0s
Rate this question

Topics

Disaster Recovery Strategies

More questions from this topic