ANS-C01 Question 69
Single answerYour company is deploying a web application that requires high availability, low latency, and secure communication over HTTPS. The application backend is hosted on Amazon EC2 instances across multiple Availability Zones. The solution must also support path-based routing to different microservices. Which AWS load balancer type should you choose for this use case?
- A
Application Load Balancer (ALB)
- B
Network Load Balancer (NLB)
- C
Classic Load Balancer (CLB)
- D
Gateway Load Balancer (GWLB)
Show answer and explanation
Correct answer: A
Explanation
The Application Load Balancer (ALB) is the best choice for this use case as it is designed for HTTP/HTTPS traffic and provides features such as path-based routing, host-based routing, and high availability across multiple Availability Zones. It also meets the security requirement with HTTPS support. The other options do not meet all the requirements of the scenario.
- A. Correct.
Application Load Balancer (ALB) is the ideal choice for this scenario since it supports path-based routing, secure HTTPS communication, and efficient routing to targets across multiple Availability Zones, making it suitable for a web application requiring high availability and low latency.
- B. Incorrect.
Network Load Balancer (NLB) is optimized for ultra-low latency and high-throughput TCP/UDP traffic but does not support path-based routing or advanced application-layer features required by this use case.
- C. Incorrect.
Classic Load Balancer (CLB) is an older load balancer type and lacks many modern features like path-based routing. It is not recommended for new applications requiring advanced functionality.
- D. Incorrect.
Gateway Load Balancer (GWLB) is designed for deploying and scaling third-party virtual appliances, such as firewalls and intrusion detection systems. It is not suitable for web application traffic distribution.