Answer-first summary for fast verification
Answer: Create a standard accelerator in AWS Global Accelerator. Create endpoint groups in us-west-2 and eu-west-1. Add the two NLBs as endpoints for the endpoint groups.
## Explanation **Correct Answer: B** AWS Global Accelerator is specifically designed for this use case. Here's why: ### Why Option B is Correct: 1. **Global Accelerator provides global traffic distribution**: It uses AWS's global network to route traffic to optimal endpoints based on performance, health, and routing policies. 2. **Endpoint groups**: You can create endpoint groups in different regions (us-west-2 and eu-west-1) and add NLBs as endpoints. 3. **Performance optimization**: Global Accelerator uses Anycast IP addresses that route traffic to the nearest AWS edge location, then over AWS's global network to the optimal endpoint. 4. **Health checks**: Global Accelerator continuously monitors endpoint health and automatically routes traffic away from unhealthy endpoints. 5. **No DNS caching issues**: Unlike DNS-based solutions, Global Accelerator uses static IP addresses that don't change, avoiding DNS caching delays. ### Why Other Options are Incorrect: **Option A (Route 53 geolocation + CloudFront):** - Geolocation routing is based on user location, not performance - Doesn't consider endpoint health or real-time performance - Requires DNS resolution which has caching delays - CloudFront adds unnecessary complexity for this use case **Option C (EIPs + Route 53 geolocation + CloudFront):** - Directly exposing EC2 instances with EIPs bypasses the NLBs, losing load balancing benefits - Doesn't provide automatic failover or health checking - More complex to manage individual EC2 instances - Geolocation routing doesn't optimize for performance **Option D (ALBs + Route 53 latency + CloudFront):** - Replacing NLBs with ALBs is unnecessary and changes the architecture - Latency routing in Route 53 is based on historical data, not real-time performance - Still suffers from DNS caching issues - CloudFront adds unnecessary overhead ### Key Benefits of Global Accelerator: - **Improved performance**: Uses AWS's global network backbone - **High availability**: Automatic failover between endpoints - **Static IP addresses**: No DNS caching delays - **Health monitoring**: Continuous endpoint health checks - **Simple management**: Single entry point for global traffic This solution directly addresses the requirements for improved performance and availability across multiple regions while maintaining the existing NLB architecture.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company has implemented a self-managed DNS solution on three Amazon EC2 instances behind a Network Load Balancer (NLB) in the us-west-2 Region. Most of the company's users are located in the United States and Europe. The company wants to improve the performance and availability of the solution. The company launches and configures three EC2 instances in the eu-west-1 Region and adds the EC2 instances as targets for a new NLB.
Which solution can the company use to route traffic to all the EC2 instances?
A
Create an Amazon Route 53 geolocation routing policy to route requests to one of the two NLBs. Create an Amazon CloudFront distribution. Use the Route 53 record as the distribution's origin.
B
Create a standard accelerator in AWS Global Accelerator. Create endpoint groups in us-west-2 and eu-west-1. Add the two NLBs as endpoints for the endpoint groups.
C
Attach Elastic IP addresses to the six EC2 instances. Create an Amazon Route 53 geolocation routing policy to route requests to one of the six EC2 instances. Create an Amazon CloudFront distribution. Use the Route 53 record as the distribution's origin.
D
Replace the two NLBs with two Application Load Balancers (ALBs). Create an Amazon Route 53 latency routing policy to route requests to one of the two ALBs. Create an Amazon CloudFront distribution. Use the Route 53 record as the distribution's origin.