AZ-700 Question 225
Single answerYou are designing a global e-commerce solution that uses Azure Front Door to distribute traffic for the domain contoso.com. You need to permanently redirect any incoming HTTP requests to HTTPS and also rewrite requests from /old-path to /new-path. Which approach should you implement to meet these requirements using Azure Front Door?
- A
Create a rewrite rule in Azure Application Gateway and forward traffic to HTTPS.
- B
Use Azure Traffic Manager with weighted routing to handle all redirection and rewriting.
- C
Define a routing rule in Azure Front Door that issues a permanent HTTPS redirect and use the Rules Engine to rewrite the path from /old-path to /new-path.
- D
Configure an Azure CDN endpoint to force HTTPS and handle the path rewrite at the endpoint level.
Show answer and explanation
Correct answer: C
Explanation
Azure Front Door offers native support for implementing redirects (HTTP to HTTPS) and path rewrites using its routing rules and the Rules Engine. By combining a permanent redirect with a URL path rewrite, you can ensure that all traffic is secured (HTTPS) and that legacy paths are seamlessly forwarded to new ones. For more details, refer to Microsoft documentation on Azure Front Door Rules Engine at https://docs.microsoft.com/azure/frontdoor/front-door-rules-engine-actions.
- A. Incorrect.
Option 1 is incorrect because Azure Application Gateway alone cannot serve as the global entry point for your domain. While it does support rewrite and redirect features, the more efficient approach for a global service is to use Azure Front Door directly for edge redirection and rewriting.
- B. Incorrect.
Option 2 is incorrect because Azure Traffic Manager operates at the DNS level for load balancing and does not handle path-based redirects or rewrites. It only directs traffic based on DNS queries and cannot rewrite URLs.
- C. Correct.
Option 3 is correct. Azure Front Door has built-in support for redirection and a Rules Engine that can rewrite incoming paths. You can configure an HTTP to HTTPS redirect (often a 301) in your routing rules and set up a rewrite rule (for example, rewriting /old-path to /new-path) in the Rules Engine for your Front Door.
- D. Incorrect.
Option 4 is incorrect because while Azure CDN provides some rule-based features, it is not typically used as the primary source for complex edge redirect and rewrite behavior in a scenario requiring a globally distributed entry point for a web application and permanent path rewrites.