A municipal smart-grid utility provider is launching a new smart-meter data ingestion system on AWS. The system's primary workload runs in the us-east-1 Region, and the company requires a disaster recovery (DR) solution in the us-west-2 Region. The application requires outbound internet access from its private subnets to register meters. The database tier uses Amazon Aurora PostgreSQL. The business requires a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. Which design meets these objectives with the lowest cost and operational complexity while maintaining high availability in the primary region?
- Configure Amazon Aurora Global Database to replicate data from us-east-1 to us-west-2. Deploy the application servers in both Regions using Auto Scaling groups, keeping the us-west-2 group scaled to a minimum capacity of one instance as a warm standby. Deploy a NAT Gateway in each Availability Zone within us-east-1 for outbound internet access. Configure Amazon Route 53 with a failover routing policy and health checks to route traffic to the secondary Region if the primary Region becomes unhealthy.Cevap
- BConfigure Amazon Aurora database cluster snapshots in us-east-1, and copy them to us-west-2 every 4 hours. Deploy the application servers using AWS CloudFormation templates in us-west-2 only when a disaster is declared. In us-east-1, deploy NAT Gateways in each Availability Zone. Use Amazon Route 53 with a failover routing policy to update DNS records to point to the new resources once the database is restored in the secondary Region.
- CConfigure Amazon Aurora Global Database to replicate data from us-east-1 to us-west-2. Deploy the application servers in both Regions using Auto Scaling groups, keeping the us-west-2 group scaled to a minimum capacity of one instance. In us-east-1, deploy a single NAT Gateway in one Availability Zone to route all outbound internet traffic from all private subnets. Configure Amazon Route 53 with a failover routing policy and health checks to handle regional failover.
- DDeploy Amazon RDS PostgreSQL in us-east-1 with a Multi-AZ deployment. Direct read-heavy application traffic in the primary region to the standby instance in the secondary Availability Zone to reduce load on the primary writer. Replicate data to us-west-2 using AWS Database Migration Service (DMS) for disaster recovery, and use Amazon Route 53 failover routing for DNS failover.
Cevap
Configure Amazon Aurora Global Database for database replication, run the secondary application tier in a warm standby state with a minimum capacity of one instance, deploy redundant NAT Gateways across Availability Zones in the primary region, and use Route 53 failover routing policy with health checks.
The correct option satisfies the 5-minute RPO using Amazon Aurora Global Database, which offers sub-second cross-region replication. It satisfies the 15-minute RTO by utilizing a warm standby strategy with at least one active instance in the secondary region's Auto Scaling group, allowing the application tier to scale up rapidly during failover. By placing NAT Gateways in each Availability Zone of the primary region, it avoids a single point of failure for outbound traffic. Using Route 53 failover routing policy allows the system to automatically redirect DNS requests to the secondary region if the primary region's ALB health checks fail.
Adım Adım Çözüm
Anahtar Kavram
High Availability and Disaster Recovery Design
Tahmini Süre:2m 0s