CDN with custom domains in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Custom Domain Validation in Azure CDN

When adding a custom domain to an Azure CDN endpoint, what is the primary method Azure uses to verify domain ownership?

A Azure sends an email to the domain registrant to confirm ownership.

B Azure checks for a specific CNAME record pointing from the custom domain to the CDN endpoint.

C Azure requires uploading a verification file to the root directory of the website.

D Azure uses WHOIS database lookup to verify the domain owner.

💡 Hint

Think about how DNS records can prove control over a domain.

Azure validates custom domains by requiring a CNAME DNS record that points the custom domain to the CDN endpoint hostname. This proves control over the domain.

❓ Architecture

intermediate

Designing a CDN Setup with Multiple Custom Domains

You need to serve content via Azure CDN for three different custom domains: example.com, images.example.com, and videos.example.com. What is the best practice for configuring these domains in Azure CDN?

A Create one CDN endpoint and add all three custom domains to it after validation.

B Create three separate CDN endpoints, each with one custom domain assigned.

C Use one CDN endpoint with a wildcard custom domain covering all subdomains.

D Create one CDN endpoint and use URL rewriting rules to handle different domains.

💡 Hint

Consider how Azure CDN endpoints support multiple custom domains.

Azure CDN endpoints can have multiple custom domains added after validation. This allows serving multiple domains from a single endpoint efficiently.

❓ scaling

advanced

Handling SSL/TLS for Multiple Custom Domains on Azure CDN

You have configured multiple custom domains on a single Azure CDN endpoint. What is the recommended approach to enable HTTPS for all these domains with minimal management overhead?

A Use a wildcard SSL certificate covering all domains and upload it to Azure CDN.

B Manually upload individual SSL certificates for each custom domain and renew them yourself.

C Use Azure CDN managed certificates which automatically provision and renew SSL certificates for all custom domains.

D Disable HTTPS and serve content only over HTTP to avoid certificate management.

💡 Hint

Think about automation and ease of maintenance for SSL certificates.

Azure CDN offers managed certificates that automatically handle provisioning and renewal of SSL certificates for custom domains, reducing operational overhead.

❓ tradeoff

advanced

Choosing Between Azure CDN Standard and Premium for Custom Domains

Which tradeoff is true when deciding between Azure CDN Standard and Premium tiers for supporting custom domains with HTTPS?

A Premium tier supports custom domain HTTPS with managed certificates and advanced rules engine, but costs more than Standard.

B Standard tier supports unlimited custom domains with free SSL, Premium requires manual SSL management.

C Premium tier does not support custom domains, only Standard does.

D Standard tier supports managed HTTPS for custom domains and advanced rules engine at a lower cost than Premium.

💡 Hint

Consider feature differences and pricing between tiers.

Azure CDN Premium offers advanced features like managed HTTPS for custom domains and a powerful rules engine but at a higher price compared to Standard.

❓ estimation

expert

Estimating DNS Propagation Time Impact on Custom Domain Activation

After adding a custom domain with a CNAME record to an Azure CDN endpoint, what is the typical maximum time you should wait before the custom domain becomes active and accessible via HTTPS?

A Up to 1 week because SSL certificates require manual approval.

B Less than 5 minutes because Azure instantly validates DNS records.

C Exactly 24 hours as Azure enforces a fixed waiting period.

D Up to 48 hours due to DNS propagation delays and certificate issuance time.

💡 Hint

Think about real-world DNS propagation and automated certificate issuance.

DNS changes can take time to propagate globally, and Azure's managed certificate issuance also requires some time, so up to 48 hours is typical.