A company is designing a new regional supply chain inventory forecasting application on AWS. The application tier runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The database tier uses Amazon Aurora PostgreSQL. The business requires a Disaster Recovery (DR) solution with a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. The architecture must minimize cost while ensuring high availability and redundancy for all outbound internet dependencies. Which design strategy meets these requirements?
- AConfigure daily Amazon Aurora database snapshots and copy them to the recovery region. Deploy the application tier on Amazon EC2 instances behind an Application Load Balancer (ALB) in the primary region only. Use AWS CloudFormation to deploy the application tier in the recovery region and restore the database from the latest snapshot during a disaster. Configure Amazon Route 53 Latency routing to manage client traffic.
- Configure Amazon Aurora Global Database with the primary cluster in the primary region and a secondary cluster in the recovery region, maintaining an active, minimum-size Amazon Aurora Serverless v2 reader instance in the secondary cluster. Deploy the application tier on Amazon EC2 instances in Auto Scaling groups behind Application Load Balancers (ALBs) in both regions, keeping the recovery region's Auto Scaling group at minimum capacity. Configure Amazon Route 53 Failover routing with health checks on the primary ALB. Deploy NAT Gateways in each Availability Zone utilized by the application in both regions.Cevap
- CConfigure Amazon Aurora Global Database with a secondary cluster in the recovery region. Deploy the application tier on Amazon EC2 instances in Auto Scaling groups behind Application Load Balancers (ALBs) in both regions, keeping the recovery region's Auto Scaling group at minimum capacity. Configure Amazon Route 53 Failover routing with health checks on the primary ALB. Deploy a single NAT Gateway in the primary Availability Zone of each region to route outbound internet traffic for all application instances.
- DDeploy an Amazon Aurora cluster in the primary region. Create a standard Aurora Replica in the recovery region and configure Amazon Aurora Auto Scaling to dynamically spin up additional reader instances in the recovery region during failover. Configure Amazon Route 53 Geolocation routing to distribute client traffic. Deploy NAT Gateways in each Availability Zone utilized by the application in both regions.
Cevap
Configure Amazon Aurora Global Database with the primary cluster in the primary region and a secondary cluster in the recovery region, maintaining an active, minimum-size Amazon Aurora Serverless v2 reader instance in the secondary cluster. Deploy the application tier on Amazon EC2 instances in Auto Scaling groups behind Application Load Balancers (ALBs) in both regions, keeping the recovery region's Auto Scaling group at minimum capacity. Configure Amazon Route 53 Failover routing with health checks on the primary ALB. Deploy NAT Gateways in each Availability Zone utilized by the application in both regions.
The correct strategy leverages Amazon Aurora Global Database to achieve sub-second cross-region replication, keeping data loss well under the 5-minute RPO. Maintaining a minimum-size Aurora Serverless v2 reader instance in the secondary region ensures a warm database target at minimal standby cost. Deploying the application tier to both regions with the secondary region's Auto Scaling group at minimum capacity ensures a warm standby that can scale out quickly, meeting the 15-minute RTO. Route 53 Failover routing with health checks automates traffic redirection when the primary endpoint is unhealthy. Finally, deploying NAT Gateways in each Availability Zone utilized in both regions ensures high availability for outbound traffic.
Adım Adım Çözüm
Anahtar Kavram
Disaster Recovery strategies (Warm Standby) combined with cross-region database replication and network path redundancy.