Examkin

Question

Difficulty: MediumDisaster Recovery Strategies

A company hosts a microservices-based application on Amazon ECS (Fargate) with an Amazon Aurora MySQL database in the us-east-1 Region. The system administrator must design a disaster recovery (DR) strategy to a secondary region (us-west-2). The business requirements specify a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 22 minutes. The recovery plan must minimize ongoing running costs in the secondary region while meeting these SLAs.

Which disaster recovery strategy meets these requirements?

  1. Configure Amazon Aurora Global Database to replicate the database to the secondary region. Deploy the Application Load Balancer (ALB) and Amazon ECS Fargate services in the secondary region with the desired task count set to 0. During a disaster, promote the secondary Aurora cluster, scale up the ECS tasks, and update Amazon Route 53 to point to the secondary ALB.Answer
  2. B
    Configure an Amazon RDS Multi-AZ deployment across us-east-1 and us-west-2 to handle database failover. Deploy the ECS Fargate tasks in the secondary region behind an ALB, and configure Route 53 with an active-active latency routing policy to automatically shift traffic between regions.
  3. C
    Configure Amazon S3 Cross-Region Replication (CRR) to replicate database backup files from the primary to the secondary region's bucket without enabling versioning on the destination bucket. Use AWS CloudFormation to rebuild the ECS infrastructure and restore the database from backups during failover.
  4. D
    Configure a Cross-Region Read Replica for the Aurora database. Configure Amazon Route 53 with a failover routing policy that points to the read replica's endpoint as the secondary destination, relying on Route 53 to automatically promote the read replica to a primary database.

Answer

Configure Amazon Aurora Global Database to replicate the database to the secondary region, deploy the load balancer and ECS Fargate services with desired tasks set to 0, and promote the database and scale up the tasks during a disaster while updating Route 53.
The correct answer uses Amazon Aurora Global Database to replicate the database with sub-second replication latency, meeting the 2-minute RPO. Deploying the application resources (ECS Fargate and ALB) with a desired task count of 0 represents a cost-effective Pilot Light disaster recovery strategy. The tasks can be quickly spun up and Route 53 DNS updated within the 15-minute RTO.

Step-by-Step Solution

1
Analyze the business requirements for recovery objectives and cost constraints.
RTO is 1515 minutes, RPO is 22 minutes, and costs in the secondary region must be minimized.
Determines the appropriate disaster recovery strategy (e.g., Pilot Light vs. Warm Standby) and database replication mechanism.
2
Evaluate database replication options that meet the 2-minute RPO.
Aurora Global Database provides sub-second replication latency, satisfying the RPO requirement.
Standard backup and restore or cross-region snapshot copies take hours and cannot meet the 2-minute RPO.
3
Evaluate application tier deployment strategies to meet the 15-minute RTO while minimizing costs.
Deploying ECS Fargate tasks with a desired count of 0 (Pilot Light) minimizes active resource costs and can be scaled up in minutes during a failover.
Warm standby keeps tasks running continuously, which costs more. Pilot Light deploys the infrastructure but keeps compute resources off or at zero until needed.

Key Concept

Disaster Recovery Strategies
Estimated Time:1m 30s
Rate this question

Topics

Disaster Recovery Strategies

More questions from this topic