Answer-first summary for fast verification
Answer: Configure an accelerator in AWS Global Accelerator. Add a listener for the port that the application listens on, and attach it to a Regional endpoint in each Region. Add the ALB as the endpoint.
## Explanation **Correct Answer: A** **Why Option A is correct:** 1. **AWS Global Accelerator** is specifically designed for global applications that require low latency and high availability. It uses the AWS global network infrastructure to route traffic to the nearest healthy endpoint. 2. **Health monitoring and failover:** Global Accelerator continuously monitors the health of endpoints (ALBs in this case) and automatically redirects traffic to healthy endpoints when issues are detected. This provides automatic failover capabilities. 3. **Anycast IP addresses:** Global Accelerator provides static IP addresses that act as a fixed entry point to your application. Traffic is automatically routed to the nearest healthy endpoint based on network conditions. 4. **Regional endpoints:** By configuring regional endpoints in each AWS Region and attaching the ALBs as endpoints, Global Accelerator can monitor health and route traffic appropriately across all regions. **Why other options are incorrect:** **Option B (CloudFront with ALB origin):** - CloudFront is a Content Delivery Network (CDN) primarily for caching static and dynamic content - While it can route to ALB origins, it's not designed for real-time gaming applications with strict latency requirements - CloudFront doesn't provide the same level of health monitoring and automatic failover between regions as Global Accelerator **Option C (CloudFront with S3 origin):** - This is completely unsuitable for a gaming application running on EC2 instances - S3 is for object storage, not for hosting dynamic gaming applications - This solution would break the application functionality **Option D (DynamoDB with DAX):** - This addresses database performance but doesn't solve the traffic routing and health monitoring requirements - DynamoDB is a database service, not a traffic routing solution - DAX is an in-memory cache for DynamoDB, which might improve database performance but doesn't address application endpoint health monitoring **Key Requirements Met by Option A:** - ✅ **Latency sensitivity:** Global Accelerator uses AWS's global network for optimal routing - ✅ **Health monitoring:** Continuously monitors endpoint health - ✅ **Traffic redirection:** Automatically redirects to healthy endpoints - ✅ **Multi-region deployment:** Supports endpoints in every AWS Region - ✅ **Integration with ALBs:** Can use existing ALBs as endpoints
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company has a popular gaming platform running on AWS. The application is sensitive to latency because latency can impact the user experience and introduce unfair advantages to some players. The application is deployed in every AWS Region. It runs on Amazon EC2 instances that are part of Auto Scaling groups configured behind Application Load Balancers (ALBs). A solutions architect needs to implement a mechanism to monitor the health of the application and redirect traffic to healthy endpoints.
Which solution meets these requirements?
A
Configure an accelerator in AWS Global Accelerator. Add a listener for the port that the application listens on, and attach it to a Regional endpoint in each Region. Add the ALB as the endpoint.
B
Create an Amazon CloudFront distribution and specify the ALB as the origin server. Configure the cache behavior to use origin cache headers. Use AWS Lambda functions to optimize the traffic.
C
Create an Amazon CloudFront distribution and specify Amazon S3 as the origin server. Configure the cache behavior to use origin cache headers. Use AWS Lambda functions to optimize the traffic.
D
Configure an Amazon DynamoDB database to serve as the data store for the application. Create a DynamoDB Accelerator (DAX) cluster to act as the in-memory cache for DynamoDB hosting the application data.