AZ-500 Question 108
Single answerYou manage a global e-commerce platform that serves both static assets (images, CSS, JavaScript) and dynamic pages from multiple Azure App Services. You plan to deploy Azure Front Door to provide a single global endpoint, reduce latency, and enable caching for static content. Which of the following actions must you perform to correctly configure Azure Front Door for caching and load balancing?
- A
Set up a route in Azure Front Door that points to your backend App Services, enable caching in the route's configuration, and define caching policies for static paths.
- B
Create an Azure Traffic Manager profile for each region to handle traffic distribution, then integrate Azure CDN separately for content caching.
- C
Configure Azure Application Gateway to terminate SSL, then point it to multiple backend App Services and enable blob-level caching for static files.
- D
Use directly the default App Service URL as your public endpoint; caching will automatically be enabled for all file types without additional configuration.
Show answer and explanation
Correct answer: A
Explanation
To implement global caching and load balancing with Azure Front Door, you must create a routing rule targeting your backends (App Services or other origins) and enable caching for static content. By configuring caching rules for the designated paths, static files are stored in edge locations around the world, reducing round trips and latency. For more information, refer to the Microsoft documentation on Azure Front Door caching (https://learn.microsoft.com/azure/frontdoor/front-door-caching).
- A. Correct.
Correct: When configuring Azure Front Door, you set a route to your backend services and enable caching for your static content paths. Defining caching rules ensures that static files (e.g., images, CSS) are served from edge locations, improving global performance.
- B. Incorrect.
Incorrect: Azure Traffic Manager only handles DNS-level distribution and does not provide caching capabilities. You would still need a separate solution (like Azure Front Door or Azure CDN) for global edge caching, making this approach incomplete.
- C. Incorrect.
Incorrect: Azure Application Gateway provides Layer 7 load balancing and WAF capabilities but does not offer global edge caching. You would need Azure Front Door or a CDN to cache assets globally for latency improvements.
- D. Incorrect.
Incorrect: Simply exposing your App Service endpoint does not enable global edge caching. Azure Front Door or Azure CDN is required to cache static content at the edge. Without a proper caching configuration, you only benefit from the default App Service capabilities, which do not offer global distribution.