Examkin

Soru

Zorluk: ZorHigh Availability and Disaster Recovery Design

A global logistics and fleet tracking platform is designing a new multi-region disaster recovery (DR) and high availability architecture for its core routing and dispatch system. The application is deployed across eu-west-1 (Primary) and eu-central-1 (Secondary). The business requires a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 1 minute.

The application layer consists of containerized microservices running on Amazon ECS on Fargate in private subnets. These microservices must make outbound API calls to external traffic mapping services, which must remain highly available even if an entire Availability Zone (AZ) in the active region experiences an outage. The database layer uses Amazon Aurora PostgreSQL. For internal service discovery, the microservices use a Route 53 Private Hosted Zone.

Which of the following architectures meets these requirements with the lowest operational complexity?

  1. Configure Amazon Aurora Global Database with the primary cluster in eu-west-1 and a secondary cluster in eu-central-1. Deploy the ECS tasks across three Availability Zones in both regions, and deploy a NAT Gateway in each Availability Zone of the VPCs. Configure Route 53 with Failover routing policies, creating a primary record pointing to the Application Load Balancer (ALB) in eu-west-1 and a secondary record pointing to the ALB in eu-central-1, both associated with Route 53 active application health checks. Associate the Route 53 Private Hosted Zone with the VPCs in both regions.Cevap
  2. B
    Configure Amazon Aurora Global Database with the primary cluster in eu-west-1 and a secondary cluster in eu-central-1. Deploy the ECS tasks across three Availability Zones in both regions, and deploy a single NAT Gateway in the first Availability Zone of each region's VPC. Configure Route 53 with Failover routing policies, creating a primary record pointing to the Application Load Balancer (ALB) in eu-west-1 and a secondary record pointing to the ALB in eu-central-1, both associated with Route 53 active application health checks. Associate the Route 53 Private Hosted Zone with the VPCs in both regions.
  3. C
    Configure Amazon Aurora Global Database with the primary cluster in eu-west-1 and a secondary cluster in eu-central-1. Deploy the ECS tasks across three Availability Zones in both regions, and deploy a NAT Gateway in each Availability Zone of the VPCs. Configure Route 53 with Failover routing policies, creating a primary record pointing to the Application Load Balancer (ALB) in eu-west-1 and a secondary record pointing to the ALB in eu-central-1, both associated with Route 53 active application health checks. Associate the Route 53 Private Hosted Zone only with the VPC in eu-west-1.
  4. D
    Configure Amazon Aurora PostgreSQL in eu-west-1 with Multi-AZ enabled, and configure hourly cross-region snapshot replication to eu-central-1. Deploy the ECS tasks across three Availability Zones in both regions, and deploy a NAT Gateway in each Availability Zone of the VPCs. Configure Route 53 with Failover routing policies, creating a primary record pointing to the Application Load Balancer (ALB) in eu-west-1 and a secondary record pointing to the ALB in eu-central-1, both associated with Route 53 active application health checks. Associate the Route 53 Private Hosted Zone with the VPCs in both regions.

Cevap

Configure Amazon Aurora Global Database across the primary and secondary regions, deploy a NAT Gateway in each Availability Zone for private subnet outbound connectivity, use Route 53 Failover routing policies with active health checks to manage region failover, and associate the Route 53 Private Hosted Zone with the VPCs in both regions.
The correct architecture leverages Amazon Aurora Global Database for sub-second cross-region replication, complying with the RPO of under 1 minute. Redundant NAT Gateways across all Availability Zones ensure outbound connectivity survives a single zone outage. Route 53 active health checks combined with Failover routing records automatically redirect traffic during an outage, meeting the RTO of under 15 minutes. Associating the Private Hosted Zone with both VPCs ensures service discovery remains functional in both regions.

Adım Adım Çözüm

1
Select a database replication mechanism that meets the RPO.
Amazon Aurora Global Database provides typical replication latency of less than 1 second, meeting the RPO of less than 1 minute.
Standard snapshot replication or cross-region backups are insufficient to meet an RPO under 1 minute.
2
Design highly available outbound network paths for the application tier.
Deploying a NAT Gateway in each Availability Zone ensures that ECS Fargate tasks in remaining zones retain outbound internet access if one zone fails.
A single NAT Gateway creates a single point of failure for outbound traffic across all Availability Zones.
3
Configure internal DNS resolution for the multi-region environment.
Associate the Route 53 Private Hosted Zone with both the primary and secondary VPCs.
If the Private Hosted Zone is not associated with the secondary VPC, the application will experience internal resolution failures during DR failover.
4
Implement automatic external client redirection.
Configure Route 53 Failover routing records for the primary and secondary Application Load Balancers with health checks.
Failover routing automatically shifts public traffic when health checks fail, keeping the recovery process within the 15-minute RTO.

Anahtar Kavram

Multi-region high availability and disaster recovery design using Route 53, Aurora Global Database, redundant NAT Gateways, and cross-VPC Private Hosted Zone associations.
Bu soruyu puanla

Konular

High Availability and Disaster Recovery Design

Bu konudan daha fazla soru