Soru

Zorluk: OrtaHigh Availability and Disaster Recovery Design

An automated inventory fulfillment platform is designing a disaster recovery strategy for its core supply chain database and API on AWS. The application currently runs in a primary AWS Region with an Amazon Aurora PostgreSQL DB cluster and Amazon EC2 instances inside private subnets using NAT Gateways. The disaster recovery strategy must achieve a Recovery Time Objective (RTO) of 1515 minutes and a Recovery Point Objective (RPO) of 22 minutes. The architecture must minimize ongoing running costs while ensuring that the infrastructure in the secondary Region can be scaled up rapidly during a failover event.

Which two configuration steps should the solutions architect implement to meet these requirements? (Select TWO.)

  1. A
    Configure AWS Backup to replicate database snapshots to the secondary Region every 22 hours, and restore the cluster from the latest snapshot during a failover event.
  2. Deploy an Amazon Aurora Global Database with the primary cluster in the active Region and a secondary cluster in the recovery Region to support sub-second data replication.Cevap
  3. Configure Route 53 active-passive failover routing pointing to the active Region Application Load Balancer (ALB) as primary and the recovery Region ALB as secondary, associated with an active health check.Cevap
  4. D
    Set up Route 53 Latency-based routing to both Regions without active health checks, allowing client traffic to route to the lowest-latency Region automatically.
  5. E
    Provision a single NAT Gateway in the recovery Region's public subnet and configure the route tables of all private subnets across multiple Availability Zones to route outbound internet traffic through it.
  6. F
    Configure Amazon Aurora Auto Scaling in the recovery Region to scale up the instance size of the primary writer instance when CPU utilization exceeds 70%70\%.

Cevap

Implementing an Amazon Aurora Global Database with a secondary cluster in the recovery Region, and configuring Route 53 active-passive failover routing pointing to the active and recovery Region Application Load Balancers with an active health check.
To meet the recovery goals of an RTO of 1515 minutes and RPO of 22 minutes, the database must replicate with low latency and the routing layer must automatically shift user traffic. Deploying an Amazon Aurora Global Database offers sub-second replication to the secondary Region and can be promoted to a writer within minutes during a failover. Configuring Route 53 active-passive failover routing with health checks ensures that traffic automatically shifts away from the unhealthy primary Region to the secondary Region within the RTO envelope.

Adım Adım Çözüm

1
Evaluate the database replication strategy to meet the 22-minute RPO.
Implement Amazon Aurora Global Database.
Aurora Global Database uses fast physical replication with latency typically under 11 second, which easily meets the 22-minute RPO.
2
Choose the routing policy to automate failover within the 1515-minute RTO.
Configure Route 53 Active-Passive failover routing with health checks.
Route 53 can automatically route traffic to the secondary Region ALB when the primary Region's endpoint fails the health check.
3
Verify supporting network and database scaling configurations for high availability.
Identify invalid or non-HA options such as single NAT gateways or invalid dynamic writer scaling configurations.
Ensuring outbound connectivity redundancy and avoiding unsupported operations (like dynamically scaling a writer instance size with Aurora Auto Scaling) prevents single points of failure and operational failures.

Anahtar Kavram

Disaster Recovery strategies for multi-region workloads require choosing appropriate database replication methods and automated DNS failover mechanisms that align with targeted RTO and RPO limits.
Bu soruyu puanla