Azure CDN profiles and endpoints - Step-by-Step Execution

Process Flow - Azure CDN profiles and endpoints

Create CDN Profile

↓

Create CDN Endpoint

↓

Associate Endpoint with Profile

↓

Configure Endpoint Settings

↓

Deploy CDN Endpoint

↓

Serve Content via CDN

↓

Monitor and Update as Needed

This flow shows creating a CDN profile, adding endpoints, configuring them, deploying, and serving content.

Execution Sample

Azure

az cdn profile create --name myProfile --resource-group myGroup --location westus
az cdn endpoint create --name myEndpoint --profile-name myProfile --resource-group myGroup --origin www.example.com

Creates a CDN profile and an endpoint linked to an origin server.

Process Table

Step	Action	Resource Created/Modified	Result/State
1	Create CDN profile 'myProfile'	CDN Profile	Profile 'myProfile' created in resource group 'myGroup' at location 'westus'
2	Create CDN endpoint 'myEndpoint' linked to 'myProfile'	CDN Endpoint	Endpoint 'myEndpoint' created with origin 'www.example.com'
3	Associate endpoint with profile	CDN Profile and Endpoint	Endpoint 'myEndpoint' is part of profile 'myProfile'
4	Configure endpoint settings (e.g., caching rules)	CDN Endpoint	Settings applied to 'myEndpoint'
5	Deploy CDN endpoint	CDN Endpoint	Endpoint 'myEndpoint' deployed and ready to serve content
6	Serve content via CDN endpoint	CDN Endpoint	Content served from 'myEndpoint' caching origin content
7	Monitor and update endpoint as needed	CDN Endpoint	Endpoint status monitored and updated if required

💡 All steps completed; CDN profile and endpoint are active and serving content.

Status Tracker

Resource	Initial State	After Creation	After Configuration	After Deployment	Final State
CDN Profile 'myProfile'	Not exist	Created	N/A	Active	Active
CDN Endpoint 'myEndpoint'	Not exist	Created	Configured	Deployed	Serving content

Key Moments - 3 Insights

Why do we need both a CDN profile and an endpoint?

The profile is like a container for endpoints; endpoints define where and how content is delivered. Step 3 shows the association.

What happens if the endpoint is not deployed after creation?

Content won't be served via CDN. Step 5 shows deployment is necessary before serving content.

Can one profile have multiple endpoints?

Yes, a profile can have many endpoints to serve different origins or regions. This is implied in step 3 where endpoints associate with profiles.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the CDN endpoint configured?

A Step 2

B Step 4

C Step 5

D Step 3

💡 Hint

Check the 'Action' column for configuration details.

According to the variable tracker, what is the state of 'myProfile' after creation?

A Active

B Configured

C Created

D Not exist

💡 Hint

Look at the 'After Creation' column for 'myProfile'.

If the endpoint is not deployed, what will be the final state of 'myEndpoint'?

A Serving content

B Configured

C Created

D Deployed

💡 Hint

Refer to step 5 and the variable tracker final states.

Concept Snapshot

Azure CDN uses profiles as containers for endpoints.
Endpoints define origins and delivery settings.
Create profile first, then add endpoints.
Configure and deploy endpoints to serve content.
Profiles can have multiple endpoints.
Deployment activates the endpoint for use.

Full Transcript

This visual execution traces the creation and deployment of Azure CDN profiles and endpoints. First, a CDN profile is created as a container. Then, an endpoint is created and linked to the profile, specifying the origin server. The endpoint is configured with caching and delivery settings. Deployment activates the endpoint, allowing it to serve content cached from the origin. Monitoring and updates ensure continued performance. Variables track the state changes of profile and endpoint from non-existence to active serving status.

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