A municipal agency is designing a cloud-native smart-grid telemetry ingestion system to monitor real-time energy distribution. The core application runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The application database is hosted on Amazon Aurora PostgreSQL. The architecture must be highly resilient across two AWS Regions to handle regional outages. The business requirements specify an active-passive disaster recovery strategy with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 1 minute. Outbound internet traffic for the private EC2 instances must remain highly available during a local Availability Zone outage. Which two architectural configurations should the solutions architect implement to satisfy these requirements?
- Configure Amazon Route 53 with a failover routing policy, designating the primary region's Application Load Balancer as active and the secondary region's Application Load Balancer as passive, and associate active Route 53 health checks with both endpoints.Cevap
- Create an Amazon Aurora Global Database with the primary database cluster in the active region and a secondary cluster in the passive region, and deploy a NAT Gateway in each Availability Zone utilized by the private EC2 instances in both regions.Cevap
- CProvision a single NAT Gateway in one public subnet for each region's VPC, configure the route tables in all private subnets to point outbound traffic to this single gateway, and configure Route 53 failover routing.
- DEnable Aurora replica auto scaling for read replicas deployed in the standby region to automatically promote a standby instance to a primary writer cluster during a regional failover event.
- EConfigure AWS Backup to take hourly database snapshots and replicate them to the standby region, and set up Amazon Route 53 latency-based routing without active health checks.
- FConfigure Route 53 Private Hosted Zones for public DNS resolution and associate the hosted zone only with the primary region's VPC, while deploying NAT Instances in each Availability Zone.