A global gaming company is preparing to launch a new game on AWS. The game runs in multiple AWS Regions on a fleet of Amazon EC2 instances. The instances are in an Auto Scaling group behind an…

Question

Options

• ACreate Amazon CloudWatch alarms that monitor the health of the ALB in each Region. Configure
• BCreate Amazon CloudWatch alarms that monitor the health of the EC2 instances in each Region.
• CConfigure Route 53 DNS failover by using a health check that monitors the private IP address of
• DConfigure Route 53 geoproximity routing. Specify the Regions that are used for the infrastructure.
• EConfigure Route 53 simple routing. Specify the continent, country, and state or province that are

• A
  83% (24)
• B
  3% (1)
• C
  3% (1)
• E
  10% (3)

Explanation

The combination of geoproximity routing and DNS failover health checks provides global low- latency routing with high availability. Geoproximity routing in Route 53 routes users to the AWS Region closest to their geographic location, optimizing latency. For automatic failover, Route 53 health checks can monitor CloudWatch alarms tied to the health of the ALB in each Region. When a Region becomes unhealthy, Route 53 reroutes traffic to the next available Region automatically. "Use geoproximity routing to direct users to resources based on geographic location, and configure health checks to provide DNS failover for high availability." Option B incorrectly monitors EC2 instances directly, which is not efficient at scale. Option C uses private IPs, which cannot be globally health-checked. Option E (simple routing) does not support geographic or failover routing. Hence, A and D together meet both the proximity and failover

No community discussion yet for this question.