Question

Your company hosts a product catalog on Azure Front Door Standard. The origin serves personalized responses that differ based on the 'region' query string parameter (for example, ?region=us and ?region=eu return different pricing). Users report that visitors in Europe sometimes see US pricing. Investigation shows Front Door is caching responses and serving the same cached object regardless of the query string. Which configuration change on the route should you make to fix this while still benefiting from caching?

Accepted Answer

Set the query string caching behavior to 'Use query string' (cache each unique URL including query string) on the route

Answer

Set the query string caching behavior to 'Ignore query strings' on the route

Answer

Disable caching entirely on the route so every request is forwarded to the origin

Answer

Enable 'Ignore specified query strings' and list the 'region' parameter to exclude it from the cache key