A metropolitan public transit agency is designing a contactless fare validation system on AWS. The application tier runs on Amazon EC2 instances in private subnets across multiple Availability Zones in both the us-east-1 and us-west-2 Regions. The application must connect securely to external fare settlement endpoints on the public internet. Internal microservices rely on private DNS resolution for service discovery across all VPCs. Validation requests from devices must be routed to the closest Region with active failover capabilities to ensure high availability and low latency. The architecture must achieve a Recovery Time Objective (RTO) of less than 5 minutes and a Recovery Point Objective (RPO) of less than 1 minute.
Which two of the following configuration options should the Solutions Architect implement to meet these requirements? (Select TWO.)
- Deploy NAT Gateways in each Availability Zone of the VPCs in both Regions, updating the private subnet route tables to route outbound internet traffic to the local NAT Gateway in the same Availability Zone.Answer
- Configure Route 53 Latency routing records with active health checks to route public validation traffic to the Application Load Balancers in both Regions, automatically routing traffic away from a degraded Region.Answer
- CDeploy a single NAT Gateway in the primary Availability Zone of each Region's VPC, routing all outbound internet traffic from all private subnets through it to minimize NAT Gateway costs.
- DCreate a Route 53 Private Hosted Zone in the us-east-1 VPC, and configure inter-region VPC peering to allow the us-west-2 VPC to automatically resolve internal DNS queries without local hosted zone association.
- EConfigure Route 53 Geolocation routing records without health checks, relying on client-side retry logic to handle failover during regional outages.
- FConfigure the database layer in us-east-1 and copy daily automated database snapshots to us-west-2 to restore the database cluster in the event of a regional disaster.