A healthcare provider is designing a multi-region disaster recovery (DR) architecture for a critical patient telemetry application. The application's web and ingestion layers run on AWS Fargate behind Application Load Balancers (ALBs) in both the primary region (`us-east-1`) and the recovery region (`us-west-2`). The ingestion tasks in both regions must query a shared metadata store and resolve the internal microservice address `api.telemetry.local` using a Route 53 Private Hosted Zone (PHZ) created in the primary VPC. The application must also send outbound alert notifications to external clinical endpoints via the internet. The architecture must support a Recovery Time Objective (RTO) of minutes and a Recovery Point Objective (RPO) of minute. The recovery region must run as a cost-efficient warm standby, keeping running resources to a minimum until a failover is declared. The solution must also remain highly available within each region, ensuring no single Availability Zone (AZ) failure can disrupt telemetry ingestion or outbound alerting. Which configuration meets these requirements while minimizing cost?
- ADeploy Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, running a single db.r6g.large reader instance in the secondary cluster. Configure Route 53 Active-Passive Failover routing policy with health checks to route public traffic to the primary ALB, failing over to the secondary ALB if health checks fail. Set up a VPC Peering connection between the primary and secondary VPCs to route DNS queries to the Route 53 Private Hosted Zone (PHZ) associated with the primary VPC. In each VPC, deploy a NAT Gateway in each of the two utilized Availability Zones.
- BDeploy Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, running a single db.r6g.large reader instance in the secondary cluster. Associate the api.telemetry.local Private Hosted Zone with both the primary and secondary VPCs. In each VPC, deploy a single NAT Gateway in one Availability Zone to handle outbound internet traffic for Fargate tasks across all private subnets. Configure Route 53 Active-Passive Failover routing policy with health checks to route public traffic to the primary ALB, failing over to the secondary ALB if health checks fail.
- Deploy Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, running a single db.r6g.large reader instance in the secondary cluster. Associate the api.telemetry.local Private Hosted Zone with both the primary and secondary VPCs. In each VPC, deploy a NAT Gateway in each of the two utilized Availability Zones. Configure Route 53 Active-Passive Failover routing policy with health checks to route public traffic to the primary ALB, failing over to the secondary ALB if health checks fail.Cevap
- DDeploy a single-region Amazon RDS for MySQL database in us-east-1. Configure AWS Backup to copy automated database snapshots to us-west-2 every hour. Associate the api.telemetry.local Private Hosted Zone with both the primary and secondary VPCs. Deploy a NAT Gateway in each of the two utilized Availability Zones in both VPCs. Configure Route 53 Active-Passive Failover routing policy with health checks to route public traffic to the primary ALB, and use an AWS Lambda function to restore the database from the latest copied snapshot during a regional failover.