AZ-700 Question 222
Single answerYou are configuring Azure Front Door for a global web application that serves media-heavy static content. You want to reduce latency and offload traffic from the application origin by caching static files such as images, style sheets, and JavaScript. Which single approach best achieves this goal?
- A
Enable caching in Azure Front Door by creating a routing rule that overrides the origin� cache-control headers for static file paths.
- B
Install Azure Cache for Redis in the same Azure region and enable the Redis In-Memory cache for all incoming requests to the web application.
- C
Use Azure Traffic Manager with Weighted routing to direct a portion of traffic to a secondary backend in another region.
- D
Create a private endpoint for the web application and rely on Azure DNS to resolve the content to the nearest Azure region.
Show answer and explanation
Correct answer: A
Explanation
To optimize delivery of static files, you should leverage Azure Front Door� built-in caching features. By configuring cache overrides in Azure Front Door, you ensure that static resources are served from edge locations around the globe, improving performance and reducing load on your origin. Refer to Microsoft� documentation on Azure Front Door caching (https://docs.microsoft.com/azure/frontdoor/front-door-caching) for best practices and step-by-step configuration details.
- A. Correct.
Correct. Azure Front Door can provide edge caching at its global Points of Presence (POPs). By creating or modifying a routing rule that overrides the origin� cache-control headers, you ensure that static content is cached at the edge, reducing repeated requests to the origin and improving performance.
- B. Incorrect.
Incorrect. While Azure Cache for Redis can help reduce load on the application backend, it is not designed for globally distributed edge caching of static web content. Redis is typically used for accelerating backend data operations or session state caching, rather than directly serving static files to end users around the world.
- C. Incorrect.
Incorrect. Azure Traffic Manager Weighted routing can direct traffic to multiple backends, but it does not provide caching at the edge. It is primarily a DNS-based routing service for balancing traffic among endpoints, not for caching static content.
- D. Incorrect.
Incorrect. Private endpoints and Azure DNS do not provide edge caching. Private endpoints secure connections to Azure services within a virtual network, and Azure DNS simply resolves domain names. Neither service offers a caching mechanism for static content.