What should you configure on an Azure Application Gateway to route traffic based on resource types?

Configuring URL path-based routing on an Azure Application Gateway allows you to direct traffic to different backend pools based on the specific path or resource type in a request’s URL. This capability enables the application gateway to effectively manage and route requests to various services or applications hosted on different servers depending on the path specified. For example, requests to /images can be routed to one backend pool optimized for serving images, while /api requests can be sent to another pool that handles API requests.

This feature is especially useful in environments where multiple applications share the same domain, allowing different types of resources to be accessed seamlessly. Path-based routing is more flexible than basic routing, which does not allow such granular control.

Multi-site listeners enable the configuration of traffic routing based on the incoming host headers, which is a different approach focused on the domain rather than the path. SSL termination is about managing SSL connections but does not include routing mechanisms based on the URL structure. Basic routing simply directs traffic to a single backend pool without the capability to differentiate based on URL paths.