Azure CDN profiles and endpoints - Mini Project: Build & Apply

Azure CDN profiles and endpoints

📖 Scenario: You are setting up a content delivery network (CDN) on Microsoft Azure to speed up your website's content delivery worldwide. You will create a CDN profile and then add an endpoint to it.

🎯 Goal: Create an Azure CDN profile named myCDNProfile in the resource group myResourceGroup located in eastus. Then create a CDN endpoint named myCDNEndpoint under this profile with the origin hostname www.example.com.

📋 What You'll Learn

Create an Azure CDN profile called myCDNProfile in resource group myResourceGroup with location eastus and SKU Standard_Microsoft.

Create an Azure CDN endpoint called myCDNEndpoint under the myCDNProfile profile.

Set the origin hostname of the endpoint to www.example.com.

Use valid Azure CLI commands or Azure Resource Manager (ARM) template JSON structure.

💡 Why This Matters

🌍 Real World

CDNs help deliver website content faster by caching it closer to users worldwide. Setting up CDN profiles and endpoints is a common task for cloud engineers to improve website performance.

💼 Career

Knowing how to create and manage Azure CDN profiles and endpoints is essential for cloud administrators and DevOps engineers working with Azure infrastructure.

1

Create the Azure CDN profile

Write the Azure CLI command to create a CDN profile named myCDNProfile in the resource group myResourceGroup with location eastus and SKU Standard_Microsoft.

Azure

# Your Azure CLI command to create the CDN profile

Hint

Use az cdn profile create with the correct parameters.

2

Set the origin hostname variable

Create a variable called origin_hostname and set it to the string www.example.com.

Azure

az cdn profile create --name myCDNProfile --resource-group myResourceGroup --location eastus --sku Standard_Microsoft

# Create a variable called origin_hostname with value 'www.example.com'

Hint

Use a simple variable assignment with double quotes.

3

Create the Azure CDN endpoint

Write the Azure CLI command to create a CDN endpoint named myCDNEndpoint under the profile myCDNProfile in resource group myResourceGroup with the origin hostname set to the variable origin_hostname.

Azure

az cdn profile create --name myCDNProfile --resource-group myResourceGroup --location eastus --sku Standard_Microsoft
origin_hostname="www.example.com"

# Your Azure CLI command to create the CDN endpoint

Hint

Use az cdn endpoint create with the correct parameters and reference the origin_hostname variable.

4

Verify the CDN endpoint creation

Write the Azure CLI command to show the details of the CDN endpoint named myCDNEndpoint in profile myCDNProfile and resource group myResourceGroup.

Azure

az cdn profile create --name myCDNProfile --resource-group myResourceGroup --location eastus --sku Standard_Microsoft
origin_hostname="www.example.com"
az cdn endpoint create --name myCDNEndpoint --profile-name myCDNProfile --resource-group myResourceGroup --origin $origin_hostname

# Your Azure CLI command to show the CDN endpoint details

Hint

Use az cdn endpoint show with the correct parameters to verify the endpoint.

Practice

1. What is the primary purpose of an Azure CDN profile?

easy

A. To manage user authentication

B. To store website content directly

C. To group CDN endpoints and define pricing tiers

D. To create virtual machines

Solution

1. Step 1: Understand the role of a CDN profile

   An Azure CDN profile acts as a container for one or more CDN endpoints and defines the pricing and features for those endpoints.

2. Step 2: Differentiate from other Azure services

   Profiles do not store content or manage authentication; those are handled by other Azure services.

3. Final Answer:

   To group CDN endpoints and define pricing tiers -> Option C

4. Quick Check:

   CDN profile = group endpoints + pricing [OK]

Hint: Profiles group endpoints and set pricing tiers [OK]

Common Mistakes:

• Confusing profiles with storage accounts
• Thinking profiles manage user access
• Assuming profiles store content

2. Which of the following is the correct way to create a new Azure CDN endpoint under an existing profile using Azure CLI?

easy

A. az cdn profile create --name myEndpoint --resource-group myResourceGroup --origin myOrigin

B. az cdn endpoint create --name myEndpoint --profile-name myProfile --resource-group myResourceGroup --origin myOrigin

C. az storage account create --name myEndpoint --profile myProfile

D. az vm create --name myEndpoint --profile myProfile

Solution

1. Step 1: Identify the correct Azure CLI command for endpoint creation

   The command to create a CDN endpoint is az cdn endpoint create with parameters for name, profile, resource group, and origin.

2. Step 2: Eliminate incorrect commands

   The other options use commands for profile creation, storage account creation, and virtual machine creation, which are unrelated to endpoint creation.

3. Final Answer:

   az cdn endpoint create --name myEndpoint --profile-name myProfile --resource-group myResourceGroup --origin myOrigin -> Option B

4. Quick Check:

   Endpoint creation uses az cdn endpoint create [OK]

Hint: Use 'az cdn endpoint create' with profile and origin [OK]

Common Mistakes:

• Using profile create command instead of endpoint create
• Confusing storage or VM commands with CDN commands
• Omitting required parameters like origin

3. Given an Azure CDN endpoint configured with origin mywebsite.azurewebsites.net, what happens when a user requests a file not yet cached by the CDN?

medium

A. The CDN fetches the file from the origin and caches it for future requests

B. The CDN returns a 404 error immediately

C. The CDN redirects the user to the origin URL

D. The CDN serves a default placeholder file

Solution

1. Step 1: Understand CDN cache miss behavior

   When a requested file is not in the CDN cache, the CDN fetches it from the origin server.

2. Step 2: Explain caching for future requests

   After fetching, the CDN caches the file to serve subsequent requests faster and reduce load on the origin.

3. Final Answer:

   The CDN fetches the file from the origin and caches it for future requests -> Option A

4. Quick Check:

   Cache miss = fetch + cache [OK]

Hint: Cache miss triggers origin fetch and caching [OK]

Common Mistakes:

• Assuming CDN returns error on cache miss
• Thinking CDN redirects to origin URL
• Believing CDN serves placeholder files

4. You created an Azure CDN endpoint but users report stale content is served after you updated your origin. What is the most likely cause and fix?

medium

A. The CDN profile is deleted; recreate the profile

B. The origin server is down; restart the origin server

C. The endpoint URL is incorrect; update DNS settings

D. The CDN cache is not refreshed; purge the CDN endpoint cache

Solution

1. Step 1: Identify cause of stale content

   CDNs cache content to improve speed, so updates at origin may not appear immediately due to cached copies.

2. Step 2: Apply the fix by purging cache

   Purging the CDN endpoint cache forces the CDN to fetch fresh content from the origin on next requests.

3. Final Answer:

   The CDN cache is not refreshed; purge the CDN endpoint cache -> Option D

4. Quick Check:

   Stale content = cache purge needed [OK]

Hint: Purge CDN cache to update stale content [OK]

Common Mistakes:

• Restarting origin when issue is cache
• Recreating profile unnecessarily
• Changing DNS when endpoint URL is correct

5. You want to design a scalable global content delivery system using Azure CDN. Which combination of Azure CDN features and configurations best supports low latency and high availability?

hard

A. Create multiple CDN endpoints in different regions under one profile; enable geo-filtering and custom domain HTTPS

B. Use a single CDN endpoint with default settings; rely on origin scaling

C. Create multiple CDN profiles with one endpoint each; disable caching to always fetch from origin

D. Use Azure Blob Storage directly without CDN; enable CDN only for static files

Solution

1. Step 1: Understand global scalability needs

   Multiple CDN endpoints in different regions reduce latency by serving users from nearest edge locations.

2. Step 2: Use features for availability and security

   Geo-filtering controls content delivery by region; custom domain HTTPS secures traffic and improves trust.

3. Step 3: Evaluate other options

   Single endpoint or disabling caching reduces performance; multiple profiles add complexity without benefit; skipping CDN loses caching advantages.

4. Final Answer:

   Create multiple CDN endpoints in different regions under one profile; enable geo-filtering and custom domain HTTPS -> Option A

5. Quick Check:

   Multiple endpoints + geo-filter + HTTPS = scalable, low latency [OK]

Hint: Multiple endpoints + geo-filtering + HTTPS for global scale [OK]

Common Mistakes:

• Using single endpoint for global users
• Disabling caching reduces performance
• Ignoring HTTPS security best practices