Answer-first summary for fast verification
Answer: Create a CloudFront origin group including two origins, one for each backend service Region, and configure origin failover as a cache behavior for the CloudFront distribution.
The correct answer is D. Creating a CloudFront origin group with two origins, one for each backend service Region, and configuring origin failover as a cache behavior for the CloudFront distribution will provide the fastest failover. This is because CloudFront Origin Failover allows CloudFront to switch between the primary and secondary origins almost immediately when it detects a failure. This method is more efficient than reducing DNS TTL or using a latency routing policy because it does not depend on DNS propagation times, which can be variable. Origin Failover is designed specifically for quick failover scenarios, making it the most effective solution for minimizing failover time.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A company operates a high-traffic website with a backend service deployed in a primary AWS Region and a disaster recovery (DR) Region. They use a single Amazon CloudFront distribution for the website and have set up an Amazon Route 53 record set with health checks and a failover routing policy for the primary Region's backend service. This Route 53 record set is configured as an origin for the CloudFront distribution, with another record set pointing to the DR Region's backend service endpoint as a secondary failover. Both record sets have a TTL of 60 seconds. However, failover currently exceeds 1 minute. A solutions architect is tasked with designing a solution to minimize failover time. Which solution would achieve the fastest failover?
A
Deploy an additional CloudFront distribution and create a new Route 53 failover record set with health checks for both CloudFront distributions.
B
Reduce the TTL to 4 seconds for the existing Route 53 record sets used for the backend services in each Region.
C
Create new record sets for the backend services using a latency routing policy and use these record sets as origins in the CloudFront distribution.
D
Create a CloudFront origin group including two origins, one for each backend service Region, and configure origin failover as a cache behavior for the CloudFront distribution.
No comments yet.