SAA-C03 Question 329
Single answerA company is hosting a web application that serves both static and dynamic content to its users. The application is deployed across multiple Availability Zones for high availability. The company wants to ensure that incoming traffic is distributed based on the URL path of the request. For example, requests to '/images/' should be routed to servers hosting static content, while requests to '/api/' should be routed to a separate set of backend instances that handle dynamic content. Which load balancer configuration should you recommend?
- A
Use an Application Load Balancer (ALB) with path-based routing rules.
- B
Use a Network Load Balancer (NLB) with target groups for different backend instances.
- C
Use a Classic Load Balancer with sticky sessions enabled.
- D
Use Route 53 with weighted routing to distribute traffic.
Show answer and explanation
Correct answer: A
Explanation
An Application Load Balancer (ALB) is the best choice for this scenario because it operates at the application layer (Layer 7) and supports advanced routing capabilities, including path-based routing. This allows you to direct different URL paths to specific backend target groups, fulfilling the requirements of the scenario. Other options, like the Network Load Balancer or Classic Load Balancer, lack the necessary features, and Route 53 is not designed for this functionality.
- A. Correct.
Correct. An Application Load Balancer (ALB) supports advanced routing features like path-based routing, which allows requests to be routed to different target groups based on the URL path.
- B. Incorrect.
Incorrect. A Network Load Balancer (NLB) operates at the transport layer (Layer 4) and does not provide application-layer (Layer 7) features like path-based routing.
- C. Incorrect.
Incorrect. A Classic Load Balancer is more limited in features and does not support path-based routing. Enabling sticky sessions does not address the requirement to route traffic based on the URL path.
- D. Incorrect.
Incorrect. While Route 53 can implement routing policies such as weighted or latency-based routing, it does not provide path-based routing functionality.