Question

Your company runs Azure Application Gateway v2 with a single public frontend IP on port 443. You have configured three multi-site listeners that use overlapping host name patterns: one listener matches 'shop.contoso.com', another matches '*.contoso.com', and a third matches '*.com'. During testing, requests to 'shop.contoso.com' are intermittently routed to the wrong backend pool. You must ensure requests to 'shop.contoso.com' are always handled by its dedicated listener without removing the wildcard listeners. What should you do?

Accepted Answer

Assign explicit routing rule priority values so the 'shop.contoso.com' rule has a lower (higher-precedence) priority number than the wildcard rules.

Answer

Move the wildcard listeners to a separate Application Gateway to avoid host name conflicts.

Answer

Change the 'shop.contoso.com' listener to a basic listener so it is evaluated first.

Answer

Enable cookie-based session affinity on the 'shop.contoso.com' HTTP setting to pin requests to the correct backend.