A global aviation logistics company is designing a high-availability crew bidding and scheduling platform across two AWS Regions: us-east-1 (Primary) and us-west-2 (Secondary). The platform has a Recovery Time Objective (RTO) of minutes and a Recovery Point Objective (RPO) of minutes. Under normal operations, global flight crews must be routed to the Region with the lowest network latency. In the event of a regional outage, traffic must automatically failover to the healthy Region. The application tier requires outbound internet connectivity to sync with external aviation authorities and must be resilient to Availability Zone (AZ) failures. Which architecture meets these requirements while minimizing operational complexity and cost?
- Configure Amazon Route 53 with Latency-based routing policies associated with health checks pointing to Application Load Balancers in both Regions. Deploy the application across multiple Availability Zones in each Region, routing outbound traffic through a NAT Gateway in each Availability Zone. Use Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, executing a managed failover during a regional disaster.Cevap
- BConfigure Amazon Route 53 with Latency-based routing policies associated with health checks pointing to Application Load Balancers in both Regions. Deploy the application across multiple Availability Zones in each Region, routing outbound traffic through a single NAT Gateway deployed in the primary Availability Zone of each Region to minimize costs. Use Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, executing a managed failover during a regional disaster.
- CConfigure Amazon Route 53 with Failover routing policies pointing to Application Load Balancers in both Regions. Deploy the application across multiple Availability Zones in each Region, routing outbound traffic through a NAT Gateway in each Availability Zone. Deploy Amazon RDS for PostgreSQL in us-east-1 with daily snapshot sharing to us-west-2, restoring the database in the secondary Region from the latest shared snapshot during a failover.
- DConfigure Amazon Route 53 with Latency-based routing policies associated with health checks pointing to Application Load Balancers in both Regions. Deploy the application across multiple Availability Zones in each Region, routing outbound traffic through a NAT Gateway in each Availability Zone. Deploy Amazon RDS for PostgreSQL in a Multi-AZ configuration in us-east-1, configuring the application tier in us-west-2 to route read-heavy database traffic directly to the RDS standby instance in the secondary Availability Zone to reduce cross-region latency.
Cevap
The correct architecture uses Route 53 Latency-based routing with health checks, a NAT Gateway in each Availability Zone in both Regions, and Amazon Aurora Global Database with managed failover.
The correct architecture meets all constraints: Route 53 Latency-based routing routes users to the lowest-latency Region and automatically redirects traffic to the secondary Region during a disaster when health checks fail. Deploying a NAT Gateway in each Availability Zone avoids single points of failure for outbound traffic. Using Amazon Aurora Global Database satisfies the of minutes (since replication lag is typically sub-second) and the of minutes (since a managed failover can be completed within a minute).
Adım Adım Çözüm
Anahtar Kavram
Designing multi-Region architectures using Route 53 routing policies, NAT Gateway redundancy, and Amazon Aurora Global Database to achieve low RTO/RPO and high availability.