A global e-commerce analytics enterprise is designing a transaction logging platform. The primary infrastructure must run in us-east-1 with a disaster recovery (DR) site in us-west-2. The business requirements specify a Recovery Time Objective (RTO) of 5 minutes, a Recovery Point Objective (RPO) of 1 minute, and a strict requirement that public client traffic be routed based on user geolocation under normal circumstances, with automated failover if a regional endpoint degrades. The solution must minimize cost where possible while ensuring high availability across Availability Zones for outbound regulatory compliance logging. Which two of the following architectural configurations must the Solutions Architect implement to satisfy these requirements?
- Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. In a disaster recovery event, use AWS Route 53 Application Recovery Controller (ARC) to initiate a failover and promote the secondary cluster to primary write status.Cevap
- Create Route 53 Geolocation routing records at the root domain level pointing to Route 53 Failover routing records for each region. Configure the failover records to direct traffic to regional Application Load Balancers, associated with Route 53 health checks of the local application stack.Cevap
- CDeploy a single NAT Gateway in one public subnet of each region's VPC, configuring the route tables of all private subnets across multiple Availability Zones to route egress traffic through this gateway to reduce costs.
- DConfigure a Route 53 Private Hosted Zone for the public domain and associate it with the VPCs in both regions, using latency-based routing policies to distribute incoming external client requests to the nearest regional load balancer.
- EEstablish a Multi-AZ Amazon RDS PostgreSQL instance in us-east-1 with cross-region read replicas in us-west-2. Enable Aurora replica auto-scaling on the standby database instances to handle write transactions immediately after failover.
- FUtilize a Pilot Light disaster recovery strategy by scheduling database snapshots every hour, replicating them to us-west-2, and maintaining a stopped set of Amazon EC2 application instances in us-west-2 that are started via AWS Lambda during failover.