A logistics company is designing a new fleet tracking application on AWS that must be deployed across two AWS Regions: eu-west-1 as primary and us-east-1 as secondary. The architecture must achieve a database Recovery Point Objective (RPO) of less than 1 minute and a Recovery Time Objective (RTO) of less than 10 minutes. The workloads in both VPCs require outbound internet access to track GPS coordinates from external devices. Outbound connectivity must be resilient to Availability Zone outages within each region. Additionally, internal microservices in both VPCs must be able to resolve private DNS records hosted in a centralized Amazon Route 53 Private Hosted Zone (PHZ).
Which two configuration options should the solutions architect select to meet these requirements?
- Configure an Amazon Aurora Global Database with the primary database cluster in eu-west-1 and a secondary database cluster in us-east-1 to handle replication and failover.Cevap
- Associate the Route 53 Private Hosted Zone with the VPCs in both regions, and deploy a NAT Gateway in each Availability Zone within both VPCs to handle outbound traffic.Cevap
- CConfigure Amazon RDS Multi-AZ for PostgreSQL in eu-west-1, deploy a cross-region read replica in us-east-1, and direct local read traffic to the RDS standby instance in eu-west-1.
- DDeploy a single NAT Gateway in the primary Availability Zone of each region to route outbound traffic, and configure VPC peering to enable DNS resolution in the secondary VPC without host zone association.
- EImplement a pilot light strategy by configuring hourly snapshots of the database in eu-west-1, copying them to us-east-1, and restoring them to a new database cluster during failover.