You use Azure CDN Standard from Microsoft in front of a web app. Requirements: 1) Force HTTPS by redirecting all HTTP requests with a 301, and 2) Internally rewrite requests from /blog/... to /content/blog/... while preserving the remaining path and query string. How should you configure the Rules Engine?

The correct option addresses both requirements using the Azure CDN Rules Engine. The first rule, matching HTTP requests and redirecting to HTTPS with a 301 (Permanent Redirect), ensures all traffic uses HTTPS as required. This rule should execute first to ensure secure communication before any other processing. The second rule, matching paths beginning with /blog/ and rewriting them to /content/blog/ while preserving the rest of the path and query string, fulfills the internal rewrite requirement. The {path} variable in the rewrite action is crucial for preserving the remaining path. The incorrect options fail for several reasons: A single rule cannot combine a redirect and a rewrite in this manner. Configuring rewrite logic on the origin or using DNS provider page rules bypasses the CDN's capabilities and adds unnecessary complexity, as the CDN Rules Engine is designed for these exact scenarios.