Question

Difficulty: EasyConfigure and Manage Azure CDN Endpoints and Caching Rules

You are managing a web application that distributes documents through an Azure CDN endpoint. You need to configure a custom caching rule in the Azure portal that overrides the default caching behavior specifically for files in the `/pdf/` directory.

In which order should you perform the steps in the Azure portal to configure and apply this custom caching rule?

  1. 1Navigate to the Azure CDN endpoint blade in the Azure portal.
  2. 2Select Caching rules under the Settings menu of the endpoint.
  3. 3In the Custom caching rules section, add a rule with the match condition set to Path, the match value to `/pdf/*`, and the caching behavior to Override.
  4. 4Click Save on the command bar to apply the configuration changes.

Answer

To configure a custom caching rule in the Azure portal, you must first navigate to the CDN endpoint, select the Caching rules settings, configure the path match and override behavior in the Custom caching rules section, and then save the changes.
The correct order begins with locating the target CDN endpoint in the portal. Next, navigation to the caching rules settings is required. Once inside, you define the custom rule settings (using the path match condition and override behavior) to target the `/pdf/` directory. Finally, saving the settings deploys the rule to the CDN POPs.

Step-by-Step Solution

1
Navigate to the CDN endpoint
The endpoint blade is displayed, exposing the management settings.
You must target the specific endpoint before you can modify its caching configurations.
2
Open Caching rules
The caching rules workspace opens, showing query string, global caching, and custom caching options.
All caching-related settings are consolidated in the Caching rules menu under Settings.
3
Configure the Custom caching rule
A new custom rule is defined targeting the `/pdf/*` path with an Override behavior.
Defining the rule specifies which requests (by path) will have their cache headers overridden and how the CDN should handle them.
4
Save the changes
The configuration is saved and propagation to the CDN edge servers begins.
Changes to caching rules do not take effect until they are saved and deployed.

Key Concept

Custom caching rules allow overriding or bypassing default caching behaviors based on specific match conditions like path or file extension.
Rate this question