Examkin

Soru

Zorluk: ZorHigh Availability and Disaster Recovery Design

A logistics company is designing a high-availability tracking and route optimization backend for a global maritime cargo fleet. The application runs on Amazon EC2 instances in private subnets across three Availability Zones in the `us-east-1` Region, with a replication target in `us-west-2` for disaster recovery. The database layer uses Amazon Aurora MySQL. The company has the following requirements:
- Maximum tolerable downtime (RTO) is 15 minutes.
- Maximum tolerable data loss (RPO) is 2 minutes.
- Outbound API calls from the EC2 instances to external weather services must remain highly available even if an Availability Zone fails, without routing traffic across Availability Zones.
- Global client requests must be routed to the closest Region to minimize latency, with automatic redirect to the surviving Region if a regional outage occurs.

Which of the following architectures meets these requirements while minimizing operational complexity and cost?

  1. A
    Deploy a Multi-AZ Amazon RDS MySQL DB instance in `us-east-1`, directing read-heavy application traffic to the standby replica to scale query performance. Deploy a cross-region read replica in `us-west-2` for disaster recovery. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the cross-region read replica to primary.
  2. B
    Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both Regions, deploy a single NAT Gateway in one Availability Zone to handle all outbound traffic from the private subnets across all zones. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the Aurora secondary database cluster to primary.
  3. Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside, and update private subnet route tables to direct outbound traffic to the local NAT Gateway. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the Aurora secondary database cluster to primary.Cevap
  4. D
    Deploy an Amazon Aurora cluster in `us-east-1` and configure an AWS Backup plan to perform daily snapshots, copying them to `us-west-2`. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside, and update private subnet route tables. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, restore the database from the copied snapshot in `us-west-2`.

Cevap

Deploy an Amazon Aurora Global Database with the primary cluster in `us-east-1` and a secondary cluster in `us-west-2`. In both Regions, deploy a NAT Gateway in each Availability Zone where the EC2 instances reside. Configure Amazon Route 53 with Latency-based routing records for the application endpoint, and associate Route 53 health checks with each record. In a disaster recovery event, manually promote the Aurora secondary database cluster.
The correct architecture leverages Amazon Aurora Global Database to achieve cross-region replication lag of under 1 second, fulfilling the 2-minute RPO. Promoting the secondary cluster takes only a few minutes, meeting the 15-minute RTO. A NAT Gateway deployed in each Availability Zone ensures that a single zone failure does not disrupt outbound traffic from the remaining zones, avoiding cross-AZ charges. Finally, Route 53 Latency-based routing with health checks routes users to the lowest-latency Region and automatically reroutes them during a failure.

Adım Adım Çözüm

1
Select the database replication strategy.
Amazon Aurora Global Database provides replication lag under 1 second and a promotion time under 15 minutes, fulfilling both the RPO of 2 minutes and RTO of 15 minutes.
Traditional backup restore methods take too long and result in high data loss, while cross-region RDS replica promotion is more complex and slow.
2
Configure highly available outbound NAT routing.
A NAT Gateway is deployed in each Availability Zone where the private subnets are located.
This setup prevents outbound traffic disruption if a single Availability Zone experiences an outage, and it prevents cross-AZ network traffic charges.
3
Set up Route 53 routing policies for latency and regional failover.
Latency-based routing records are configured pointing to each region's load balancer, with Route 53 health checks associated with each record.
This routes global client traffic to the nearest healthy Region to minimize latency, and automatically shifts traffic to the surviving Region if health checks fail.

Anahtar Kavram

Multi-region disaster recovery and high availability design combining low-latency global routing, cross-region database replication, and localized NAT gateway redundancy.
Bu soruyu puanla

Konular

High Availability and Disaster Recovery Design

Bu konudan daha fazla soru