Examkin

Soru

Zorluk: Çok zorHigh Availability and Disaster Recovery Design

A financial technology organization is designing a high-volume transaction ledger platform. The application must achieve a recovery time objective (RTO) of under 1010 seconds and a recovery point objective (RPO) of under 55 seconds for cross-region disaster recovery between us-east-1 and us-west-2. The data layer requires active-active multi-region write capability to prevent regional write bottlenecks. For internal communications, microservices must resolve a shared private DNS namespace across the VPCs in both regions. Additionally, all outbound transaction compliance reports sent to external financial clearinghouses must originate from static, whitelisted public IP addresses from both regions. Which of the following architectures meets these requirements while ensuring high availability and compliance?

  1. Deploy Amazon DynamoDB Global Tables replicated between us-east-1 and us-west-2. In both regions, deploy active application servers in Auto Scaling groups behind Application Load Balancers (ALBs). Configure Route 53 with an Active-Active Latency-based routing policy associated with health checks. Associate the Route 53 Private Hosted Zone (PHZ) for the internal DNS namespace with the VPCs in both regions. Deploy redundant NAT Gateways across multiple Availability Zones in both VPCs, allocating Elastic IP addresses for outbound traffic.Cevap
  2. B
    Deploy Amazon DynamoDB Global Tables replicated between us-east-1 and us-west-2. In us-east-1, deploy active application servers in Auto Scaling groups behind an ALB. In us-west-2, deploy an ALB but keep the application servers scaled down to zero instances, configured to scale out during a failover event. Configure Route 53 with an Active-Passive Failover routing policy. Associate the Route 53 Private Hosted Zone (PHZ) for the internal DNS namespace with the VPCs in both regions. Deploy redundant NAT Gateways across multiple Availability Zones in both VPCs, allocating Elastic IP addresses for outbound traffic.
  3. C
    Deploy Amazon DynamoDB Global Tables replicated between us-east-1 and us-west-2. In both regions, deploy active application servers in Auto Scaling groups behind ALBs. Configure Route 53 with an Active-Active Latency-based routing policy associated with health checks. Associate the Route 53 Private Hosted Zone (PHZ) for the internal DNS namespace only with the us-east-1 VPC. Deploy redundant NAT Gateways across multiple Availability Zones in both VPCs, allocating Elastic IP addresses for outbound traffic.
  4. D
    Deploy Amazon DynamoDB Global Tables replicated between us-east-1 and us-west-2. In both regions, deploy active application servers in Auto Scaling groups behind ALBs. Configure Route 53 with an Active-Active Latency-based routing policy associated with health checks. Associate the Route 53 Private Hosted Zone (PHZ) for the internal DNS namespace with the VPCs in both regions. Deploy a single NAT Gateway in each region's primary Availability Zone to minimize network gateway costs, allocating Elastic IP addresses for outbound traffic.

Cevap

The correct architecture uses Amazon DynamoDB Global Tables for active-active multi-region replication to satisfy the sub-5 second RPO. Deploying active application instances behind ALBs in both regions and utilizing Route 53 Latency-based routing meets the sub-10 second RTO requirement. Redundant NAT Gateways across multiple Availability Zones ensure high availability for outbound traffic, while associating the Private Hosted Zone with both VPCs enables internal name resolution in both regions.
The correct architecture uses Amazon DynamoDB Global Tables for active-active multi-region replication to satisfy the sub-5 second RPO. Deploying active application instances behind ALBs in both regions and utilizing Route 53 Latency-based routing meets the sub-10 second RTO requirement. Redundant NAT Gateways across multiple Availability Zones ensure high availability for outbound traffic, while associating the Private Hosted Zone with both VPCs enables internal name resolution in both regions.

Adım Adım Çözüm

1
Evaluate the database tier against the RPO and active-active write requirements.
Amazon DynamoDB Global Tables provide fully managed active-active replication with sub-second replication latency, satisfying the sub-5 second RPO target and preventing write bottlenecks.
Relational options (like Aurora Global Database) only support a single primary writer region in standard configurations, which does not satisfy the active-active multi-region write requirement.
2
Evaluate the compute tier and Route 53 routing against the RTO requirement.
Deploying active application instances behind ALBs in both regions with Route 53 Latency-based routing enables near-instant routing shifts, satisfying the sub-10 second RTO.
A pilot light or warm standby setup that scales from zero cannot provision and bootstrap compute resources within 10 seconds.
3
Assess the internal DNS name resolution requirement across regions.
Associate the Route 53 Private Hosted Zone (PHZ) with the VPCs in both us-east-1 and us-west-2.
A Private Hosted Zone must be explicitly associated with each VPC that needs to resolve those internal DNS records.
4
Assess the outbound NAT gateway configuration against the high availability and compliance constraints.
Deploy redundant NAT Gateways across multiple Availability Zones in each VPC and associate Elastic IP addresses to them.
A single NAT Gateway per VPC creates a single point of failure. Redundant gateways are required to ensure continuous outbound flow during a zone failure.

Anahtar Kavram

Multi-Region Active-Active High Availability and DNS routing coordination
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

High Availability and Disaster Recovery Design

Bu konudan daha fazla soru