Examkin

Soru

Zorluk: OrtaHigh Availability and Disaster Recovery Design

A company is designing a new multi-region web application that processes package tracking requests. The application tier runs on Amazon EC2 instances in an Auto Scaling group across two Availability Zones behind an Application Load Balancer (ALB) in the primary region (us-east-1). The application tier requires outbound internet connectivity to query external APIs for customs clearance updates. For disaster recovery, the database tier uses Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in the recovery region (us-west-2). The disaster recovery solution must achieve a Recovery Time Objective (RTO) of less than 10 minutes, a Recovery Point Objective (RPO) of less than 1 minute, and minimize resource costs during normal operations. Additionally, the outbound connectivity in the primary region must not have a single point of failure. Which architecture configuration should a solutions architect select to meet these requirements?

  1. A
    Deploy a single NAT Gateway in one Availability Zone in the primary region, pointing the route tables of all private subnets across both Availability Zones to this NAT Gateway. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing a single scaled-down db.t3.medium reader instance. Use Route 53 Failover routing policies with health checks linked to the regional ALBs.
  2. Deploy a NAT Gateway in each Availability Zone in the primary region, updating the route tables for each private subnet to point to its local NAT Gateway. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing a single scaled-down db.t3.medium reader instance. Use Route 53 Failover routing policies with health checks linked to the regional ALBs.Cevap
  3. C
    Deploy a NAT Gateway in each Availability Zone in the primary region, updating the route tables for each private subnet to point to its local NAT Gateway. Configure Amazon Aurora daily snapshot copies from us-east-1 to us-west-2, and restore the database to a new cluster in us-west-2 only during a disaster event. Use Route 53 Failover routing policies with health checks linked to the regional ALBs.
  4. D
    Deploy a NAT Gateway in each Availability Zone in the primary region, updating the route tables for each private subnet to point to its local NAT Gateway. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing a single scaled-down db.t3.medium reader instance. Create a Route 53 Private Hosted Zone for the database endpoint in the primary account's VPC but do not associate it with the recovery VPC. Use Route 53 Geolocation routing to route public web traffic.

Cevap

Deploy a NAT Gateway in each Availability Zone in the primary region, updating the route tables for each private subnet to point to its local NAT Gateway. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing a single scaled-down db.t3.medium reader instance. Use Route 53 Failover routing policies with health checks linked to the regional ALBs.
The correct architecture requires a NAT Gateway in each Availability Zone of the primary region to prevent outbound internet connectivity from becoming a single point of failure. It also requires Amazon Aurora Global Database to achieve the sub-minute RPO and sub-10-minute RTO, along with Route 53 Failover routing policies with health checks to automatically direct public traffic to the recovery region's Application Load Balancer in the event of a primary region outage.

Adım Adım Çözüm

1
Analyze the outbound connectivity requirements for high availability in the primary region.
Identify that outbound NAT Gateway redundancy is required. A NAT Gateway must be placed in each Availability Zone, and private subnet route tables must be updated to route traffic through their local NAT Gateway.
Prevents a failure in one Availability Zone from interrupting the outbound API connectivity of instances in the remaining healthy Availability Zone.
2
Evaluate the database replication strategy against RTO and RPO limits.
Select Amazon Aurora Global Database over snapshot copies, configuring a single scaled-down reader instance in the secondary region to minimize costs.
Aurora Global Database replication lag is under 1 second, meeting the sub-minute RPO constraint, and failover takes less than a few minutes, meeting the 10-minute RTO constraint.
3
Determine the proper Route 53 DNS routing policy for the multi-region configuration.
Select Route 53 Failover routing with health checks targeted at regional Application Load Balancers.
Failover routing is designed specifically for active-passive disaster recovery, ensuring that traffic automatically routes to the secondary region if the primary region's endpoints fail health checks.

Anahtar Kavram

High Availability and Disaster Recovery Design
Bu soruyu puanla

Konular

High Availability and Disaster Recovery Design

Bu konudan daha fazla soru