AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company has a stateless web application that runs on AWS Lambda functions that are invoked by Amazon API Gateway. The company wants to deploy the application across multiple AWS Regions to provide Regional failover capabilities.
What should a solutions architect do to route traffic to multiple Regions?
Other
Community
UAnonymous
A
Create Amazon Route 53 health checks for each Region. Use an active-active failover configuration.
B
Create an Amazon CloudFront distribution with an origin for each Region. Use CloudFront health checks to route traffic.
C
Create a transit gateway. Attach the transit gateway to the API Gateway endpoint in each Region. Configure the transit gateway to route requests.
D
Create an Application Load Balancer in the primary Region. Set the target group to point to the API Gateway endpoint hostnames in each Region.
Explanation:
Explanation
Correct Answer: A
Amazon Route 53 is the appropriate AWS service for implementing multi-region failover and routing traffic across multiple AWS Regions. Here's why:
Why Route 53 is the Best Solution:
- DNS-based Routing: Route 53 is AWS's DNS service that can route traffic to resources in different AWS Regions based on health checks and routing policies.
- Health Checks: Route 53 can monitor the health of endpoints in each Region and automatically route traffic away from unhealthy Regions.
- Active-Active Configuration: This allows traffic to be distributed across multiple healthy Regions simultaneously, improving availability and performance.
- Failover Capabilities: Route 53 supports active-passive failover (where traffic goes to a primary Region and fails over to a secondary if the primary is unhealthy) and active-active configurations.
Why Other Options Are Incorrect:
Option B (CloudFront):
- CloudFront is a Content Delivery Network (CDN) primarily for caching and delivering content globally.
- While CloudFront can have multiple origins, it's not designed for regional failover routing between API endpoints in different Regions.
- CloudFront health checks are limited and not as robust as Route 53's for failover scenarios.
Option C (Transit Gateway):
- Transit Gateway is for connecting VPCs and on-premises networks, not for routing internet traffic to API Gateway endpoints.
- Transit Gateway operates within a single Region (though there is Transit Gateway Inter-Region Peering, but this is for connecting networks, not for internet traffic routing).
- This approach would be complex and not appropriate for routing public internet traffic.
Option D (Application Load Balancer):
- ALB operates within a single Region and cannot route traffic to endpoints in other Regions.
- ALB target groups can only contain targets within the same Region.
- This solution would not provide true multi-region failover.
Implementation Details:
To implement this solution, the solutions architect would:
- Deploy the Lambda/API Gateway application in multiple Regions.
- Create Route 53 health checks for each Region's API Gateway endpoint.
- Configure a Route 53 routing policy (such as failover routing or latency-based routing) with health checks.
- Set up an active-active configuration to distribute traffic across healthy Regions.
This approach provides the most reliable and AWS-native solution for multi-region failover with stateless applications.
Comments
Loading comments...