What should a solutions architect do to meet these requirements?
Create an Amazon CloudFront distribution. Create an origin group with one origin for each ALB. Set one of the origins as primary.
Create an Amazon Route 53 health check for each ALB. Create a Route 53 failover routing record pointing to the two ALBs. Set the Evaluate Target Health value to Yes.
Create two Amazon CloudFront distributions, each with one ALB as the origin. Create an Amazon Route 53 failover routing record pointing to the two CloudFront distributions. Set the Evaluate Target Health value to Yes.
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.
Explanations:
While creating an Amazon CloudFront distribution with an origin group allows for failover between origins, it does not address fetching assets from the closest Region directly. This option does not account for geographic latency or ensure that the nearest region is always selected first.
This option suggests using Route 53 failover routing records with health checks, which would allow for failover to the secondary ALB if the primary one fails. However, it does not inherently prioritize requests to the closest region based on latency, as failover routing is primarily for disaster recovery rather than performance.
Creating two separate CloudFront distributions does not effectively utilize the benefits of a single distribution for geographical latency. Additionally, using Route 53 failover routing for CloudFront distributions is unnecessary and does not optimize for closest region retrieval effectively.
This option uses Route 53 latency routing, which directs traffic to the ALB in the region with the lowest latency, ensuring that game assets are fetched from the closest Region. The health checks provide failover capability, redirecting traffic to the secondary ALB if the primary one becomes unavailable.
I map out that the answer is:
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.