A financial services firm is migrating a critical transaction-processing workload to AWS. The application must achieve zero data loss (Recovery Point Objective of 0) during a physical site failure, satisfy strict data residency laws requiring all data to remain within a specific country, and minimize latency for users in that country. To meet these requirements, how should the firm design its infrastructure using AWS Regions and Availability Zones?
- ADeploy the application in a multi-region active-active configuration across two separate AWS Regions within the country, using synchronous database replication between the regions.
- BDeploy the primary database in a single Availability Zone, and configure AWS to automatically mirror the data to a neighboring country's Region using synchronous replication.
- Deploy the application across multiple Availability Zones within a single AWS Region located in the target country, utilizing synchronous replication between the zones.Answer
- DConfigure a single Availability Zone to span across two different AWS Regions within the country to ensure physical redundancy and power grid independence.
Answer
Deploy the application across multiple Availability Zones within a single AWS Region located in the target country, utilizing synchronous replication between the zones.
Deploying the application across multiple Availability Zones within a single AWS Region located in the target country meets all requirements. Availability Zones within the same Region are connected by high-speed, private fiber-optic networks that support the low-latency required for synchronous replication (achieving RPO of 0). Because all selected Availability Zones reside within the single Region in the target country, the data residency requirement is fully satisfied.
Step-by-Step Solution
Key Concept
AWS Regions vs Availability Zones Connectivity and Boundaries
Estimated Time:2m 0s