Examkin

Soru

Zorluk: Çok zorEnhancing Reliability and Disaster Recovery

An enterprise runs a multi-tier application across several VPCs in us-east-1 with database workloads on Amazon Aurora PostgreSQL Serverless v2. The internal microservices rely on a Route 53 Private Hosted Zone (PHZ) managed in a centralized Shared Services account. Currently, all outbound internet traffic from the private application subnets is routed through a single NAT Gateway in us-east-1's Availability Zone A.

To improve reliability and implement a disaster recovery (DR) strategy in us-west-2, the Solutions Architect must design a solution meeting an RTO of 1515 minutes and an RPO of 55 minutes. The strategy must resolve existing single points of failure in the network path and ensure internal microservices resolution works seamlessly in both regions during a failover.

Which combination of actions will meet these requirements while minimizing operational complexity?

  1. A
    Deploy a NAT Gateway in each Availability Zone in us-east-1 and update the respective private subnet route tables. Configure hourly Amazon Aurora snapshot copies to us-west-2 and script the restoration of the cluster on-demand using AWS CloudFormation during a failover event. Associate the centralized Route 53 Private Hosted Zone (PHZ) in the Shared Services account with the new VPCs in us-west-2. Configure an active-passive Route 53 Failover routing policy pointing to the Application Load Balancers in both regions, and attach Route 53 active health checks that monitor end-to-end application health.
  2. B
    Deploy a NAT Gateway in each Availability Zone in us-east-1 and update the respective private subnet route tables. Create an Amazon Aurora Global Database with a secondary cluster in us-west-2 containing Serverless v2 instances. Create a duplicate Route 53 PHZ with the same domain name in the us-west-2 VPCs to handle local resolution, and replicate records using an AWS Lambda function. Configure an active-passive Route 53 Failover routing policy pointing to the Application Load Balancers in both regions, and attach Route 53 active health checks that monitor end-to-end application health.
  3. Deploy a NAT Gateway in each Availability Zone in us-east-1 and update the respective private subnet route tables. Create an Amazon Aurora Global Database with a secondary cluster in us-west-2 containing Serverless v2 instances. Associate the centralized Route 53 PHZ in the Shared Services account with the new VPCs in us-west-2. Configure an active-passive Route 53 Failover routing policy pointing to the Application Load Balancers in both regions, and attach Route 53 active health checks that monitor end-to-end application health.Cevap
  4. D
    Maintain the single NAT Gateway in Availability Zone A for both primary and secondary region configurations. Create an Amazon Aurora Global Database with a secondary cluster in us-west-2 containing Serverless v2 instances. Associate the centralized Route 53 PHZ in the Shared Services account with the new VPCs in us-west-2. Configure a Route 53 Failover routing policy pointing to the Application Load Balancers in both regions, but do not associate any health check to the primary record, relying instead on client-side retry logic and manual DNS routing adjustments during an outage.

Cevap

Deploy a NAT Gateway in each Availability Zone in us-east-1 and update route tables. Create an Amazon Aurora Global Database with a secondary cluster in us-west-2. Associate the centralized Route 53 Private Hosted Zone (PHZ) in the Shared Services account with the new VPCs in us-west-2. Configure an active-passive Route 53 Failover routing policy with active health checks.
The correct answer provides a comprehensive disaster recovery and reliability enhancement plan. It resolves the network single point of failure by adding redundant NAT Gateways per Availability Zone. It guarantees the 5-minute RPO using Amazon Aurora Global Database, which offers low-latency asynchronous cross-region replication. It resolves cross-region internal service resolution by associating the central Route 53 Private Hosted Zone with the DR VPCs. Lastly, it implements automated failover using active health checks with a Route 53 Failover policy to satisfy the 15-minute RTO.

Adım Adım Çözüm

1
Address the single point of failure in the egress network path by deploying a NAT Gateway in each Availability Zone in the primary region.
Outbound internet access is made redundant across all Availability Zones, preventing a single zone outage from disrupting traffic in the other zones.
Routing all private subnet traffic through a single NAT Gateway creates a critical single point of failure.
2
Set up an Amazon Aurora Global Database with a primary cluster in us-east-1 and a secondary cluster in us-west-2.
Physical storage replication is performed asynchronously with latency typically under 1 second.
This setup allows the database tier to achieve an RPO of less than 5 minutes and supports promotion to primary within minutes to satisfy the 15-minute RTO.
3
Associate the centralized Route 53 Private Hosted Zone (PHZ) from the Shared Services account with the VPCs in us-west-2.
The application servers in us-west-2 can immediately resolve internal microservices endpoints.
This establishes cross-account VPC association with the central host zone, avoiding DNS resolution failures or duplicate zone maintenance overhead.
4
Configure a Route 53 Failover routing policy with active health checks pointing to the Application Load Balancers in both regions.
Traffic automatically shifts to the disaster recovery region when the primary region's ALBs or underlying applications become unhealthy.
Active health checks are required to trigger automated failover within the 15-minute RTO window.

Anahtar Kavram

Multi-region disaster recovery requires redundant network egress, cross-region database replication, proper multi-account private DNS association, and automated DNS failover with health checks.
Bu soruyu puanla

Konular

Enhancing Reliability and Disaster Recovery