Tailwind Airlines needs an Application Gateway to route requests to /images/* to a blob-serving backend pool and /api/* to API VMs. They plan to use a single multi-site listener on app.contoso.com. What Application Gateway configuration will accomplish this with the least complexity?

The correct approach is to use a path-based routing rule (path map). Application Gateway's path-based routing allows you to direct traffic to different backend pools based on the URL path. By defining rules for /images/ and /api/ on a single listener, you efficiently route requests to the appropriate backend pools (blob storage and API VMs, respectively) with minimal configuration complexity. A default backend ensures all other paths are handled. Incorrect options: Creating two separate listeners for /images and /api would require two distinct hostnames or frontend IPs, which contradicts the requirement of using a single multi-site listener on app.contoso.com. URL rewrite operates on the request before it reaches the backend pool and is not designed for routing to different backend pools based on paths in this manner. It's more for modifying the URL or headers. Probe-based routing is used for health checks and determining backend pool member availability, not for routing incoming requests based on URL paths. Multiple backend HTTP settings are common but don't inherently solve path-based routing without a routing rule.