AWS Certified Solutions Architect Associate SAA-C03 Practice Question
An international financial organization must ensure their highly transactional application's operations can withstand the outage of a data center without any service interruption. Furthermore, the application should incur minimal latency for users in Europe, North America, and Asia. Considering cost-effectiveness and operational complexity, what deployment approach adheres BEST to these requirements?
Implement a global database cluster with cross-region read replicas to ensure the application's relational data remains available and experiences low latency accesses.
Utilize one AWS Region to host the primary instance and establish cross-region read replicas in regions closest to Europe, North America, and Asia.
Deploy the application into a single AWS Region and distribute it across multiple Availability Zones, leveraging Amazon Route 53 health checks for failover.
Establish the application in multiple AWS Regions each located near Europe, North America, and Asia, with an Amazon Route 53 latency-based routing policy.
The correct approach is to establish the application in multiple AWS Regions near the primary user bases, using an Amazon Route 53 latency-based routing policy. This architecture directly addresses the two main requirements:
Global Low Latency: By deploying the application's resources (compute and database) in regions close to users in Europe, North America, and Asia, and using latency-based routing, user requests are sent to the region with the lowest network latency.
High Availability: A multi-region deployment ensures that the application can withstand a complete regional outage, which far exceeds the requirement of surviving a single data center (Availability Zone) failure.
The other options are incorrect for the following reasons:
Deploying in a single region across multiple Availability Zones provides high availability for failures within that region but fails to provide low latency for a global user base.
Implementing only a global database cluster or using cross-region read replicas are incomplete solutions. They only address the data layer. A complete solution requires deploying the application and compute resources in multiple regions as well. Furthermore, for a 'highly transactional' application, simply having read replicas in other regions does not solve for write latency, as writes must still travel to the primary database instance.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is Amazon Route 53 and how does it work?
Open an interactive chat with Bash
What are the benefits of deploying applications across multiple AWS Regions?
Open an interactive chat with Bash
What is the difference between Availability Zones and Regions in AWS?