A company that is developing a mobile game is making game assets available in two AWS Regions. Game assets are served from a set of Amazon EC2 instances behind an Application Load Balancer (ALB) in each Region. The company requires game assets to be fetched from the closest Region. If game assets become unavailable in the closest Region, they should be fetched from the other Region. What should a solutions architect do to meet these requirements?
Select an option, then click Submit answer.
Reference / correct answer:
Create an Amazon Route 53 health check for each ALB. Create a Route 53 latency alias record pointing to the two ALBs. Set the Evaluate Target Health value to Yes.
Most accepted answer: D. Create an Amazon Route 53 health check for each ALB. Create a Route 53 latency alias record pointing to the two ALBs. Set the Evaluate Target Health value to Yes.
Community votes: A=6, B=1, C=1, D=7
Selected Answer: D A - Need to set cache behaviour for another origin B - Failover routing record cannot point to 2 ALBs C - Works but does not meet the requirement. By default, when there is no unhealthy distribution, the traffic will always be sent to the primary but not the closest region. D - Sending the traffic to the closest region unless the closest region becomes unhealthy upvoted 14 times
Selected Answer: A It is either A or D but both are not perfect. In A Cloudfront will always fetch from the primary region not the closest region. In D latency based routing might not choose the closest region but the one with best latency. For the following reasons I go with A: A is correct: the user will always use the nearest edge location in the closest region to fetch the game assets. Cloudfront will either respond from the cache or load the game assets from the primary origin (or in case the primary origin is not available from the fail over origin). B is incorrect because the game assets would always be fetched from the primary region. C is wrong because this setup is essentially the same as A but much more complicated. D is wrong because latency based routing does not necessarily choose the nearest region but the region with the best latency (geolocation routing policy would be the correct to fulfill the requirement) upvoted 6 times
Selected Answer: D ey insight: Only latency-based routing routes users to the closest Region. Combined with health checks (Evaluate Target Health = Yes), it provides automatic failover to the other Region when the closest one is unhealthy. This satisfies both requirements in one clean solution. upvoted 1 times
Selected Answer: A D gives latency routing but weak/no reliable failover. A gives both closest delivery (via CloudFront edges) + fast automatic failover (via Origin Group). upvoted 1 times Amac1979 1 month, 1 week ago A (CloudFront with origin group) — A CloudFront origin group provides failover between origins, and it serves content from edge locations. However, the primary/secondary model in an origin group doesn't route to the "closest" origin — it always tries the primary first, then falls back to secondary. It doesn't provide latency-based origin selection between two Regions. upvoted 1 times ...
A (CloudFront with origin group) — A CloudFront origin group provides failover between origins, and it serves content from edge locations. However, the primary/secondary model in an origin group doesn't route to the "closest" origin — it always tries the primary first, then falls back to secondary. It doesn't provide latency-based origin selection between two Regions. upvoted 1 times