ANS-C01 Question 67
Single answerYou are designing a highly available and secure web application that serves both HTTP and HTTPS traffic. The application has a global user base and requires features such as SSL termination, WebSocket connections, and intelligent path-based routing. Which type of load balancer should you choose to meet these requirements?
- A
Application Load Balancer (ALB)
- B
Network Load Balancer (NLB)
- C
Gateway Load Balancer (GWLB)
- D
Classic Load Balancer (CLB)
Show answer and explanation
Correct answer: A
Explanation
The Application Load Balancer (ALB) is specifically built for Layer 7 (HTTP/HTTPS) traffic and offers features such as SSL termination, WebSocket support, and intelligent path-based routing. These capabilities align perfectly with the requirements of the web application described in the scenario. Other load balancers like NLB and GWLB operate at different layers of the OSI model and do not provide the necessary Layer 7 functionality, while the CLB is outdated and lacks the advanced features needed for modern applications.
- A. Correct.
The Application Load Balancer (ALB) supports features such as SSL termination, WebSocket connections, intelligent path-based routing, and is designed for Layer 7 (HTTP/HTTPS) traffic, making it the best fit for this use case.
- B. Incorrect.
The Network Load Balancer (NLB) is designed for Layer 4 (TCP/UDP) traffic and doesn't natively support path-based routing or advanced Layer 7 features required in this scenario.
- C. Incorrect.
The Gateway Load Balancer (GWLB) is used for deploying virtual appliances like firewalls and does not support features like SSL termination or path-based routing.
- D. Incorrect.
The Classic Load Balancer (CLB) is a legacy service with limited features and is not recommended for new designs. It lacks the advanced Layer 7 capabilities required for this scenario.