Azure CDN profiles and endpoints - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Azure CDN profile using Azure CLI.

Azure

az cdn profile create --name [1] --resource-group MyResourceGroup --location eastus --sku Standard_Verizon

Drag options to blanks, or click blank then click option'

AMyCdnProfile

BMyResourceGroup

Ceastus

DStandard_Verizon

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource group name instead of the profile name for --name.

Confusing location with profile name.

The --name parameter specifies the name of the CDN profile to create.

2fill in blank

medium

Complete the code to create a CDN endpoint under an existing profile.

Azure

az cdn endpoint create --name [1] --profile-name MyCdnProfile --resource-group MyResourceGroup --origin www.example.com

Drag options to blanks, or click blank then click option'

AMyCdnProfile

BMyResourceGroup

Cwww.example.com

DMyCdnEndpoint

Attempts:

3 left

💡 Hint

Common Mistakes

Using the origin URL as the endpoint name.

Confusing profile name with endpoint name.

The --name parameter specifies the name of the CDN endpoint to create.

3fill in blank

hard

Fix the error in the command to update the origin hostname of a CDN endpoint.

Azure

az cdn endpoint update --name MyCdnEndpoint --profile-name MyCdnProfile --resource-group MyResourceGroup --set properties.origins[0].hostName=[1]

Drag options to blanks, or click blank then click option'

Aneworigin.example.com

BMyCdnEndpoint

CMyResourceGroup

DMyCdnProfile

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource group or profile name instead of origin hostname.

Leaving the originHostHeader empty.

The hostName should be set to the new origin hostname, such as 'neworigin.example.com'.

4fill in blank

hard

Fill both blanks to list all CDN endpoints in a resource group and filter by profile name.

Azure

az cdn endpoint list --resource-group [1] --profile-name [2]

Drag options to blanks, or click blank then click option'

AMyResourceGroup

BMyCdnProfile

CMyCdnEndpoint

Deastus

Attempts:

3 left

💡 Hint

Common Mistakes

Using endpoint name instead of profile name.

Using location instead of resource group.

The --resource-group specifies the resource group, and --profile-name specifies the CDN profile to filter endpoints.

5fill in blank

hard

Fill all three blanks to delete a CDN endpoint safely.

Azure

az cdn endpoint delete --name [1] --profile-name [2] --resource-group [3] --yes

Drag options to blanks, or click blank then click option'

AMyCdnEndpoint

BMyCdnProfile

CMyResourceGroup

DStandard_Verizon

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up profile and resource group names.

Omitting the --yes flag to confirm deletion.

The --name is the endpoint name, --profile-name is the CDN profile, and --resource-group is the resource group containing them.

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