Question

Contoso hosts a single web application behind Azure Application Gateway v2. The application serves static images from URLs beginning with /images/* and API calls from URLs beginning with /api/*. The team wants requests to /images/* to be sent to a backend pool of storage-optimized VMs, requests to /api/* to be sent to a backend pool of compute-optimized VMs, and all other requests to a default backend pool. All requests arrive on the same listener (HTTPS, same hostname). What should you configure to route the traffic correctly?

Accepted Answer

Create a path-based routing rule with URL path maps that match /images/* and /api/* to their respective backend pools, and set the default backend pool for unmatched paths.

Answer

Create three separate multi-site listeners, each bound to a different host header, and associate each with its own basic routing rule.

Answer

Create a rewrite rule set that inspects the request URI and rewrites the backend target based on the path prefix.

Answer

Create a custom health probe for each backend pool so the gateway automatically directs traffic to the matching path.