Question

Difficulty: MediumConfigure and Manage Azure CDN Endpoints and Caching Rules

You are developing a web application that serves static assets from an Azure CDN Standard from Microsoft endpoint. You need to configure the CDN endpoint to automatically redirect all incoming HTTP requests to HTTPS using the CDN's Rules engine. Which five actions should you perform in sequence? To answer, arrange the appropriate actions in the correct order.

  1. 1Navigate to the CDN endpoint page in the Azure Portal and select Rules engine under Settings.
  2. 2Select Add rule and enter a name for the rule.
  3. 3Add a Request protocol condition, set the operator to Equals, and set the value to HTTP.
  4. 4Add a URL redirect action, set the protocol to HTTPS, and select Found (302) as the redirect type.
  5. 5Select Save and wait for the rule configuration to deploy.

Answer

To configure an HTTP to HTTPS redirect for an Azure CDN Standard from Microsoft endpoint, you must navigate to the CDN endpoint in the Azure Portal, access the Rules engine under Settings, add a new rule, define a match condition where Request protocol equals HTTP, add a URL redirect action to HTTPS, and finally save the rule.
The correct sequence begins with accessing the endpoint settings and selecting the Rules engine. A new rule must be created and named. To target insecure traffic, a condition matching the HTTP protocol is added. The associated action must be a URL redirect pointing to HTTPS. Finally, saving the rule deploys the configuration to the edge nodes.

Step-by-Step Solution

1
Navigate to the Rules engine section of the CDN endpoint.
The Rules engine interface loads, allowing you to define global or custom rules.
This is the administrative interface where CDN rules are managed.
2
Add a new rule container.
A blank rule structure is created.
Each rule requires a name before conditions or actions can be appended.
3
Define the match condition for HTTP traffic.
The rule is configured to trigger only when an incoming request uses the HTTP protocol.
This ensures secure HTTPS requests are not evaluated or redirected again.
4
Configure the redirect action.
The rule is set to issue an HTTP redirect to the HTTPS counterpart.
The URL redirect action handles the redirection response directly at the CDN edge.
5
Save the rule configuration.
The rule is saved and begins deployment.
The configuration must propagate to all global edge servers to take effect.

Key Concept

Configuring transport layer security redirects using the Azure CDN Standard Rules Engine.
Estimated Time:1m 30s
Rate this question