Path-Based Routing Load Balancer

Answer - B.

Some of the key points of the Application Load balancer over the classic load balancer is.

1

Support for path-based routing.

You can configure rules for your listener that forward requests based on the URL in the request.

This enables you to structure your application as smaller services, and route requests to the correct service based on the content of the URL.

2

Support for host-based routing.

You can configure rules for your listener that forward requests based on the host field in the HTTP header.

This enables you to route requests to multiple domains using a single load balancer.

For more information on load balancing solutions please visit the below URL:

http://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html

The correct load balancer to use in this scenario would be the Application Load Balancer (ALB).

Explanation:

• Classic Load Balancer: This load balancer operates at Layer 4 of the OSI model and is not capable of path-based routing. Additionally, while it can terminate HTTPS connections, it cannot communicate with backend instances over HTTPS.
• Network Load Balancer: This load balancer operates at Layer 4 and can route traffic based on IP protocol data, but not path-based routing. Like the Classic Load Balancer, it can terminate HTTPS connections, but it cannot communicate with backend instances over HTTPS.
• Secondary Load Balancer: There is no such thing as a Secondary Load Balancer in AWS. It is not a valid option.

Application Load Balancer: This load balancer operates at Layer 7 of the OSI model and can perform path-based routing. It is also capable of terminating HTTPS connections and communicating with backend instances over HTTPS, making it the correct choice for this scenario.

Therefore, the correct answer is B. Application Load balancer.