Q51 — AWS SAA-C03 Ch.5
Question 51 of 65 | ← Chapter 5
Q351. 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?
- 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
Correct Answer: B. Create an Amazon CloudFront distribution with an origin for each Region. Use CloudFront health checks to route traffic
Explanation
B. Create an Amazon CloudFront distribution with an origin for each Region. Use CloudFront health checks to route traffic:By creating a separate origin for each region on Amazon CloudFront and using CloudFront's health checks feature, the company can ensure that users are automatically directed to healthy endpoints in different regions if a primary endpoint becomes unavailable. This approach enables regional failover capabilities by routing traffic to healthy origins based on proximity and latency. Option A involves using Amazon Route 53 health checks for each region which may not be as efficient as CloudFront, since Route 53 is primarily designed for DNS routing. Option C involves using a transit gateway to connect API Gateway endpoints in each region which may introduce additional complexity and operational overhead.Option D involves using an Application Load Balancer (ALB) to route traffic to API Gateway endpoints in each region, which may not be practical or efficient since ALB is designed for load balancing at the instance level rather than routing traffic to serverless functions like Lambda.