A logistics enterprise is migrating its inventory management system to AWS. The architecture must protect against localized facility-level disruptions while also ensuring business continuity in the event of a widespread geographic disaster. Which of the following design decisions regarding AWS Global Infrastructure should the enterprise make? (Select TWO)
- Distribute application instances across multiple Availability Zones in a single AWS Region to survive localized infrastructure outages.Answer
- Replicate transactional data backups to a separate AWS Region to serve as a secondary disaster recovery site.Answer
- CHost the application database across multiple AWS Edge Locations to achieve low-latency synchronous replication.
- DConfigure a single application cluster to span across Availability Zones in different countries to comply with local data sovereignty laws.
- EPlace both the primary and standby databases in the same physical data center building to reduce inter-AZ communication latency.
Answer
The logistics enterprise should distribute application instances across multiple Availability Zones in a single AWS Region to survive localized infrastructure outages, and replicate transactional data backups to a separate AWS Region to serve as a secondary disaster recovery site.
Distributing application instances across multiple Availability Zones in a single AWS Region provides high availability and fault tolerance because each Availability Zone has independent power, cooling, and network connections. Replicating backups to a separate AWS Region ensures disaster recovery and business continuity because AWS Regions are geographically isolated and independent of each other.
Step-by-Step Solution
Key Concept
AWS Regions and Availability Zones provide isolated infrastructure boundaries that support localized high availability (using Availability Zones) and broad disaster recovery (using separate Regions).