An energy utility company is designing a disaster recovery architecture for its smart grid control system. The application's primary deployment is in us-west-2 and consists of microservices running on Amazon EC2 instances inside private subnets, outbound traffic routed via NAT Gateways, and a backend Amazon Aurora MySQL database. The company needs to design a disaster recovery solution in us-east-1 that achieves a Recovery Time Objective (RTO) of 10 minutes and a Recovery Point Objective (RPO) of 1 minute, while minimizing cost and avoiding active-active write workloads. Which TWO configurations should a Solutions Architect implement to meet these requirements?
- Create an Amazon Aurora Global Database with the primary database cluster in us-west-2 and a secondary database cluster in us-east-1 to replicate data with sub-second replication latency.Cevap
- Deploy the application servers in us-east-1 using Auto Scaling groups configured with minimum running instances, and configure Route 53 active-passive failover routing to redirect traffic to the secondary region when the primary region is unhealthy.Cevap
- CImplement hourly database snapshots in us-west-2, copy them to us-east-1 via cross-region snapshot copy, and restore them to a new database cluster during a failover event.
- DDeploy a single NAT Gateway in a single Availability Zone in us-east-1 to route outbound telemetry verification requests from all recovery private subnets to the internet.
- EConfigure the application servers in the secondary region to write directly to the read-only standby instance of a standard Amazon RDS Multi-AZ deployment located in the primary region.
Cevap
Creating an Amazon Aurora Global Database to achieve sub-second data replication and deploying the application servers in us-east-1 in a warm standby state with Route 53 active-passive failover routing.
To meet the 1-minute RPO and 10-minute RTO constraints while avoiding active-active complexity, a Solutions Architect should implement an Amazon Aurora Global Database for sub-second database replication across regions, and deploy a warm standby application stack in us-east-1. The warm standby uses Auto Scaling groups with minimum capacity to control cost, and Route 53 active-passive failover routing automatically or manually redirects traffic during a failover event.
Adım Adım Çözüm
Anahtar Kavram
Designing multi-region disaster recovery using warm standby compute configurations and low-latency storage replication mechanisms like Aurora Global Database.