A financial services firm is migrating its transaction processing application to AWS. The application requires synchronous database replication to ensure high availability with minimal latency. Additionally, compliance regulations dictate that a copy of the transactional data must be stored in a geographically isolated location at least 250 miles away for disaster recovery. Which architectural strategy utilizing AWS global infrastructure components best meets these requirements?
- Deploy the database instances across multiple Availability Zones within a single AWS Region, and replicate data to a separate AWS Region for disaster recovery.Answer
- BDeploy the database instances across multiple AWS Regions for synchronous replication, and store disaster recovery backups in a different Availability Zone within the primary AWS Region.
- CDeploy the database instances in a single Availability Zone, and use AWS Edge Locations to host synchronous database replicas for disaster recovery.
- DDeploy the database instances across multiple Edge Locations for low-latency replication, and store backups in a different Availability Zone in the same AWS Region.
Answer
Deploy the database instances across multiple Availability Zones within a single AWS Region, and replicate data to a separate AWS Region for disaster recovery.
Deploying database instances across multiple Availability Zones in the same Region ensures high availability through synchronous replication due to low-latency links. Replicating data to a different AWS Region achieves the required geographic distance (hundreds of miles) to safeguard against regional disasters.
Step-by-Step Solution
Key Concept
AWS Regions provide geographical separation for disaster recovery and compliance, while Availability Zones provide isolated locations within a Region designed for high availability and low-latency synchronous replication.