ANS-C01 Question 217
Single answerYou are designing a highly available web application hosted on AWS. The application has both static content (such as HTML files) and dynamic content (generated by backend servers). You need to implement a load balancing solution that optimizes performance, handles SSL termination, and supports routing based on URL paths (e.g., '/api/' routed to dynamic backend servers and '/static/' routed to an S3 bucket). Which type of load balancer and configuration should you choose?
- A
Use an Application Load Balancer (ALB) with URL-based routing rules
- B
Use a Network Load Balancer (NLB) with target groups for static and dynamic content
- C
Use a Classic Load Balancer (CLB) with SSL termination enabled
- D
Use a Gateway Load Balancer (GWLB) with custom routing rules
Show answer and explanation
Correct answer: A
Explanation
For a solution that optimizes performance and supports URL-based routing, an Application Load Balancer (ALB) is the most appropriate choice. ALB operates at Layer 7 of the OSI model and supports advanced features such as content-based routing, SSL termination, and integration with target groups for both static and dynamic content. In contrast, Network Load Balancers and Classic Load Balancers do not provide the necessary Layer 7 functionality, and Gateway Load Balancers are not suitable for this type of application.
- A. Correct.
Correct: An Application Load Balancer (ALB) operates at Layer 7 of the OSI model, which allows URL-based routing, making it ideal for this scenario. It also supports SSL termination and is well-suited to handle both static and dynamic content.
- B. Incorrect.
Incorrect: A Network Load Balancer (NLB) operates at Layer 4 of the OSI model and does not support URL-based routing. It is better suited for low-latency, TCP/UDP traffic but does not meet the requirements for this scenario.
- C. Incorrect.
Incorrect: While a Classic Load Balancer (CLB) supports SSL termination, it lacks advanced Layer 7 features like URL-based routing, making it unsuitable for this use case.
- D. Incorrect.
Incorrect: A Gateway Load Balancer (GWLB) is designed for deploying third-party virtual appliances (e.g., firewalls) and does not provide Layer 7 routing or SSL termination.