Examkin

Soru

Zorluk: ZorHigh Availability and Disaster Recovery Design

An international flight dispatch and crew scheduling platform is designing a new multi-region disaster recovery (DR) architecture. The application is deployed across VPCs in us-east-1 (Primary) and us-west-2 (Secondary). The platform has a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 11 minute. Outbound internet communication from application servers in private subnets must remain highly available in the event of an Availability Zone (AZ) outage. The system must minimize operational costs during idle periods, while ensuring that database failover meets the target recovery metrics. Which two of the following configurations should the solutions architect implement to meet these requirements? (Select TWO.)

  1. Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy a single db.r6g.large reader instance in the secondary cluster to minimize idle database costs, and use automated scripting or AWS Application Recovery Controller to initiate failover and database promotion during a disaster event.Cevap
  2. In both the us-east-1 and us-west-2 VPCs, deploy a NAT Gateway in each Availability Zone. Configure the route table for each private subnet to route outbound traffic to the NAT Gateway in its respective Availability Zone.Cevap
  3. C
    Deploy a single NAT Gateway in the primary Availability Zone of each VPC, and configure the route tables of all private subnets across all Availability Zones to route outbound internet traffic through this single NAT Gateway.
  4. D
    Configure Route 53 with an Active-Active Latency routing policy pointing to Application Load Balancers in both regions, and rely on Route 53 health checks to automatically redirect write traffic to us-west-2 without database promotion if us-east-1 experiences an outage.
  5. E
    Configure Amazon Aurora Serverless v2 in us-east-1 and set up Amazon RDS Multi-AZ replication to a standby db.r6g.large instance in us-west-2 to serve read-only queries and scale dynamically.
  6. F
    Create a Route 53 Private Hosted Zone (PHZ) in the primary AWS account to resolve internal service endpoints, and configure a Route 53 Resolver endpoint in the secondary account to forward DNS queries across regions without associating the PHZ to the VPC in us-west-2.

Cevap

Configure an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 running a single db.r6g.large reader instance, while using automated scripting or AWS Application Recovery Controller to initiate failover. Additionally, deploy a NAT Gateway in each Availability Zone in both regions and configure subnet route tables to route outbound traffic locally.
The correct configurations combine Amazon Aurora Global Database for low-latency asynchronous replication (achieving RPO < 11 minute) with a single small instance in the secondary region to optimize costs, and deploy multi-AZ NAT Gateways to ensure outbound internet routes remain resilient to Availability Zone failures.

Adım Adım Çözüm

1
Evaluate the database replication strategy to satisfy the target recovery metrics.
Using Amazon Aurora Global Database provides cross-region replication lag of less than 11 second (meeting the 11-minute RPO). Keeping a single small reader instance in the secondary cluster minimizes operational costs during normal operations.
An unplanned failover can be initiated programmatically within minutes, well within the 1515-minute RTO limit, without paying for duplicate primary capacity in the secondary region.
2
Design highly resilient outbound internet connectivity to prevent single points of failure.
A NAT Gateway must be deployed in each Availability Zone of both VPCs, with subnet route tables directing 0.0.0.0/00.0.0.0/0 traffic to the local zone's NAT Gateway.
NAT Gateways are zone-redundant resources; a single NAT Gateway deployment exposes all private subnets in other Availability Zones to outage risks if that specific zone fails.
3
Eliminate invalid options based on architectural limitations and cross-region DNS constraints.
Ensure Private Hosted Zones are associated directly with the target VPCs rather than relying on cross-account forwarding rules, and reject cross-region RDS Multi-AZ replication proposals since Multi-AZ does not cross regional boundaries.
This guarantees that DNS endpoints resolve correctly after failover and that database replication behaves according to AWS product capabilities.

Anahtar Kavram

Designing cost-optimized, multi-region disaster recovery (DR) architectures using Aurora Global Database combined with zone-redundant NAT Gateway topologies to achieve target RTO/RPO metrics.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

High Availability and Disaster Recovery Design

Bu konudan daha fazla soru