ANS-C01 Question 280
Single answerYour company is running a multi-region application hosted on Amazon ECS with a private application load balancer (ALB) in each region. The application requires communication between regions, and you need to ensure low-latency connectivity while securely exposing the ALB endpoints for cross-region traffic. Which approach should you implement?
- A
Use AWS Global Accelerator to route traffic between the regions and configure endpoint groups for each ALB.
- B
Configure VPC peering between the regions and update security groups to allow cross-region traffic.
- C
Enable AWS PrivateLink for the ALBs and use interface endpoints for cross-region communication.
- D
Set up a Route 53 private hosted zone with weighted routing policies for each ALB.
Show answer and explanation
Correct answer: A
Explanation
AWS Global Accelerator is the best solution for cross-region communication in this scenario because it provides low-latency routing, traffic management, and secure connectivity. By configuring endpoint groups for each ALB, traffic can be intelligently routed to the appropriate region while benefiting from AWS's global network infrastructure. The other options either lack the necessary features or are not suitable for the requirements of this specific use case.
- A. Correct.
This option is correct. AWS Global Accelerator provides low-latency, highly available, and secure connectivity between endpoints in different regions. Using endpoint groups, it can direct traffic to the appropriate ALBs efficiently.
- B. Incorrect.
This option is incorrect. While VPC peering allows connectivity between regions, it does not offer the benefits of low-latency routing, global failover, or secure abstraction layers that AWS Global Accelerator provides.
- C. Incorrect.
This option is incorrect. AWS PrivateLink is used for service-to-service communication within or across VPCs but does not facilitate direct ALB-to-ALB communication across regions.
- D. Incorrect.
This option is incorrect. Route 53 private hosted zones are used for DNS resolution within a VPC, but weighted routing policies alone do not ensure secure or low-latency connectivity between regions.