B is the correct one for seld manage DNS If need to use Route53, ALB (layar 7 ) needs to be used as end points for 2 reginal x 3 EC2s, if it the case answer would be the option 4

for me it is B

i choose a previous until i checked google that tells me "DNS is an Application-layer protocol"

A seems the right answer.

Not A: CloudFront is not for DNS Not C: Involves CloudFront which is not needed, otherwise would work but ignore the NLBs Not D: ALB can't handle DNS Leaves B

Keyword- AWS global accelerator = Super cop (who direct the traffic and give you the best way to reach your destination) Geolocation is use for showing web content as you want to show your web content to particular country or continent. Geolocation has nothing to do with traffic.

Option B. Create a standard accelerator in AWS Global Accelerator. Establish endpoint groups in us-west-2 and eu-west-1. Add two NLBs as endpoints of the endpoint group. AWS Global Accelerator is a network service that can provide a global traffic management solution. By creating a standard accelerator in AWS Global Accelerator, you can guide user traffic to the endpoint closest to them, thereby improving the performance and availability of the application. In this case, you can establish endpoint groups in the us-west-2 and eu-west-1 regions, and add two NLBs as endpoints. In this way, no matter where the user is located, their requests will be routed to the EC2 instance closest to them, thereby improving the performance and availability of DNS resolution. In addition, this design can also provide flexibility and scalability to handle a large amount of traffic. Therefore, this solution can meet your needs.

Global Accelerator: AWS Global Accelerator is designed to improve the availability and performance of applications by using static IP addresses (Anycast IPs) and routing traffic over the AWS global network infrastructure. Endpoint Groups: By creating endpoint groups in both the us-west-2 and eu-west-1 Regions, the company can effectively distribute traffic to the NLBs in both Regions. This improves availability and allows traffic to be directed to the closest Region based on latency.

Key: route traffic to all the EC2 instances

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. Here's why this option is the most suitable: Global Accelerator: AWS Global Accelerator is designed to improve the availability and performance of applications by using static IP addresses (Anycast IPs) and routing traffic over the AWS global network infrastructure. Endpoint Groups: By creating endpoint groups in both the us-west-2 and eu-west-1 Regions, the company can effectively distribute traffic to the NLBs in both Regions. This improves availability and allows traffic to be directed to the closest Region based on latency.

B is the best solution to route traffic to all the EC2 instances across regions. The key reasons are: AWS Global Accelerator allows routing traffic to endpoints in multiple AWS Regions. It uses the AWS global network to optimize availability and performance. Creating an accelerator with endpoint groups in us-west-2 and eu-west-1 allows traffic to be distributed across both regions. Adding the NLBs in each region as endpoints allows the traffic to be routed to the EC2 instances behind them. This provides improved performance and availability compared to just using Route 53 geolocation routing.

B route requests to one of the two NLBs --> hence AD out / Attach Elastic IP addresses --> who will pay for it?

Option B offers a global solution by utilizing Global Accelerator. By creating a standard accelerator and configuring endpoint groups in both Regions, the company can route traffic to all the EC2 across multiple regions. Adding the two NLBs as endpoints ensures that traffic is distributed effectively. Option A does not directly address the requirement of routing traffic to all EC2 instances. It focuses on routing based on geolocation and using CloudFront as a distribution, which may not achieve the desired outcome. Option C involves managing Elastic IP addresses and routing based on geolocation. However, it may not provide the same level of performance and availability as AWS Global Accelerator. Option D focuses on ALBs and latency-based routing. While it can be a valid solution, it does not utilize AWS Global Accelerator and may require more configuration and management compared to option B.

Correctly is B. if it is self-managed DNS, you cannot use Route 53. There can be only 1 DNS service for the domain.

For self-managed DNS solution: https://aws.amazon.com/blogs/security/how-to-protect-a-self-managed-dns-service-against-ddos-attacks-using-aws-global-accelerator-and-aws-shield-advanced/

Re-wording the correct explanations here: if it is self-managed DNS, you cannot use Route 53. There can be only 1 DNS service for the domain. If the question didn't mentioned self-managed DNS and asked for optimal solution, then D is correct.

Using self managed DNS - other three options talking about Route 53 so B can only B answer