Q75 — AWS SAA-C03 Ch.10

Question 75 of 100 | ← Chapter 10

Q675. An online gaming company hosts its platform on Amazon EC2 instances behind Network Load Balancers (NLBs) across multiple AWS Regions.The NLBs can route requests to targets over the internet.The company wants to improve the customer playing experience by reducing end-to-end load time for its global customer base.Which solution will meet these requirements?

Correct Answer: D. Create a standard accelerator in AWS Global Accelerator. Configure the existing NLBs as target endpoints

Explanation

To improve the customer playing experience by reducing end-to-end load time for a global customer base hosted on Amazon EC2 instances behind Network Load Balancers (NLBs) across multiple AWS Regions, the solution that would best meet these requirements is:D. Create a standard accelerator in AWS Global Accelerator. Configure the existing NLBs as target endpoints.Here's the rationale behind this solution:Option D: Create a standard accelerator in AWS Global Accelerator. Configure the existing NLBs as target endpoints.AWS Global Accelerator is a service that helps improve the availability and performance of applications with a global customer base. By creating a standard accelerator, you can take advantage of AWS's global network infrastructure to route traffic from your customers to the closest AWS Region. This can significantly reduce the end-to-end load time by minimizing the network latency.To implement this solution, you would create a standard accelerator in AWS Global Accelerator and configure the existing NLBs as target endpoints. By doing so, the traffic will be directed through the Global Accelerator to the closest AWS Region where the NLBs are hosted, improving the response time for your global customers.Option A: Create Application Load Balancers (ALBs) in each Region to replace the existing NLBs. Register the existing EC2 instances as targets for the ALBs in each Region. While ALBs can provide additional features and flexibility, such as content-based routing and advanced request handling, they may not necessarily improve the end-to-end load time for a global customer base compared to NLBs. Setting up ALBs in each Region would require additional configuration and management overhead, and it may not directly address the goal of reducing end-to-end load time across multiple AWS Regions.Option B: Configure Amazon Route 53 to route equally weighted traffic to the NLBs in each Region. While Amazon Route 53 can be used for DNS-based traffic routing, simply routing equally weighted traffic to NLBs in each Region may not provide the desired improvement in end-to-end load time. It doesn't leverage AWS Global Accelerator's network optimization capabilities and may not effectively route traffic to the closest AWS Region for each customer.Option C: Create additional NLBs and EC2 instances in other Regions where the company has large customer bases.Creating additional NLBs and EC2 instances in more Regions can help distribute the load and improve availability, but it may not directly address the goal of reducing end-to-end load time for the global customer base. It can also introduce additional management complexity and cost without leveraging AWS Global Accelerator's optimizations.Therefore, the most suitable solution that meets the requirements is to create a standard accelerator in AWS Global Accelerator and configure the existing NLBs as target endpoints (Option D). This solution leverages AWS Global Accelerator's global network infrastructure to route traffic efficiently, reducing end- to-end load time for the global customer base.