SAP-C02 · Question #730
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…
The correct answer is A. Create an Amazon CloudFront distribution. Create an origin group with one origin for each ALB. To serve game assets from the closest AWS Region with automatic failover to another Region if the primary becomes unavailable, an Amazon CloudFront distribution with an origin group is the ideal solution. CloudFront provides latency-based routing to its edge locations, and the…
Question
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?
Options
- ACreate an Amazon CloudFront distribution. Create an origin group with one origin for each ALB.
- BCreate an Amazon Route 53 health check for each ALCreate a Route 53 failover routing record
- CCreate two Amazon CloudFront distributions, each with one ALB as the origin. Create an Amazon
- DCreate an Amazon Route 53 health check for each ALB. Create a Route 53 latency alias record
How the community answered
(23 responses)- A65% (15)
- B22% (5)
- C4% (1)
- D9% (2)
Why each option
To serve game assets from the closest AWS Region with automatic failover to another Region if the primary becomes unavailable, an Amazon CloudFront distribution with an origin group is the ideal solution. CloudFront provides latency-based routing to its edge locations, and the origin group enables automatic failover between the ALBs in different Regions based on their health.
An Amazon CloudFront distribution inherently provides global latency-based routing to serve content from the closest edge location, and an origin group with multiple ALBs configured allows CloudFront to automatically failover to a healthy secondary origin if the primary becomes unavailable.
Route 53 failover routing records provide primary/secondary failover but do not intrinsically offer latency-based routing to the *closest* healthy resource.
Creating two separate CloudFront distributions and then using Route 53 for failover is an overly complex and less integrated approach compared to using a single CloudFront distribution with an origin group for both latency and failover.
Route 53 latency alias records direct traffic to the lowest latency resource but do not automatically failover to another healthy region if the lowest latency endpoint becomes unhealthy.
Concept tested: CloudFront with origin groups for global latency routing and failover
Source: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/high_availability_origin_failover.html
Community Discussion
No community discussion yet for this question.