Q10 — AWS SAA-C03 Ch.5

Question 10 of 65 | ← Chapter 5

Q310. A company has a stateless web application that runs on AWS IAMbda 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?

Correct Answer: B. Create an Amazon CloudFront distribution with an origin for each Region. Use CloudFront health checks to route traffic

Explanation

Option B: Creating an Amazon CloudFront distribution with an origin for each Region and using CloudFront health checks to route traffic is a good solution to provide regional failover capabilities. If one Region becomes unavailable, CloudFront will automatically route traffic to the next available Region. This approach also helps reduce latency by caching content closer to end-users and offloads traffic from the backend servers.Option A: Creating Amazon Route 53 health checks for each Region and using an active-active failover configuration can work but it does not provide the benefits of reduced latency through caching like CloudFront.Option A: Creating Amazon Route 53 health checks for each Region and using an active-active failover configuration is a valid solution to provide regional failover capabilities. However, it may add additional latency since the DNS resolution may take longer due to the time it takes for Route 53 to detect a failed region and update its DNS records. Additionally, this solution requires that clients make frequent DNS requests to ensure they have the latest IP address so traffic can be directed to an alternate region when a failure occurs.Option C: While creating a transit gateway and attaching it to the API Gateway endpoint in each Region and configuring the transit gateway to route requests is possible, it will add complexity and increase latency as the request needs to pass through the transit gateway before reaching the API Gateway endpoint. Option D: Creating an Application Load Balancer in the primary Region and setting the target group to point to the API Gateway endpoint hostnames in each Region is not a valid solution because Application Load Balancers cannot directly target API Gateway endpoints.