Examkin

Question

Difficulty: HardMulti-AZ, Multi-Region Architectures and Disaster Recovery (DR)

A global travel reservation platform hosts its application in the `us-east-1` Region. The architecture consists of an Amazon Aurora MySQL database cluster and a fleet of Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The platform needs to establish a disaster recovery (DR) plan in the `us-west-2` Region. The DR solution must achieve a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 22 minutes, while minimizing ongoing running costs in the secondary region.

Which combination of actions should a solutions architect perform to 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`. In the event of a primary region outage, promote the secondary cluster to a standalone primary cluster.Answer
  2. Deploy an Application Load Balancer and an Auto Scaling group in `us-west-2` with minimum and desired capacities set to 11. Configure Amazon Route 53 with failover routing and health checks to route traffic to the secondary load balancer.Answer
  3. C
    Configure daily snapshots of the database cluster, copy them to Amazon S3 in `us-west-2`, and transition them to Amazon S3 Glacier Flexible Retrieval to minimize storage costs.
  4. D
    Configure Amazon Route 53 with latency-based routing to split client traffic equally between `us-east-1` and `us-west-2` without health checks, and maintain identical EC2 running capacity in both regions.
  5. E
    Deploy a standard Amazon RDS for MySQL database in `us-east-1` with a Read Replica in `us-west-2`, and rely on Amazon RDS to automatically fail over and redirect application write traffic to the Read Replica during a regional outage.

Answer

Create an Amazon Aurora Global Database to replicate the database, and maintain a scaled-down Pilot Light compute tier in the secondary region with Route 53 failover routing.
Aurora Global Database replicates data across regions with latency under 11 second, satisfying the 22-minute RPO. In a disaster, the secondary cluster can be promoted to a standalone primary cluster in less than 11 minute. Maintaining a scaled-down Auto Scaling group (Pilot Light) with a capacity of 11 in the secondary region minimizes ongoing costs while ensuring the infrastructure is ready to scale up within the 1515-minute RTO when Route 53 routes traffic there.

Step-by-Step Solution

1
Determine the database replication mechanism that meets the RPO of 22 minutes.
Aurora Global Database provides asynchronous replication with typical latency of less than 11 second, which fits the requirement.
Choosing a high-performing database replication technology is necessary to ensure data is constantly synchronized without violating the recovery point objective.
2
Determine the compute recovery strategy that meets the RTO of 1515 minutes while minimizing running costs.
A Pilot Light strategy with an Auto Scaling group having a minimum/desired capacity of 11 keeps costs low while allowing rapid scaling when DNS failover is triggered.
Maintaining active but scaled-down services ensures that the endpoint infrastructure is online, which speeds up failover compared to building from backups.
3
Configure Amazon Route 53 failover routing with health checks.
DNS requests will resolve to the primary region under normal conditions and automatically redirect to the secondary region if the primary region becomes unhealthy.
Automatic failover requires health monitoring and dynamic DNS resolution routing policies to minimize manual intervention and meet the RTO.

Key Concept

Disaster Recovery (DR) strategies using Aurora Global Database and Pilot Light compute scaling across AWS Regions.
Rate this question

Topics

Multi-AZ, Multi-Region Architectures and Disaster Recovery (DR)

More questions from this topic