CDN with custom domains in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a CDN endpoint specifying its location.

Azure

az cdn endpoint create --name myEndpoint --profile-name myProfile --resource-group myResourceGroup --origin-host-name myOrigin [1]

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

A--tags environment=prod

B--custom-domain mycustomdomain.com

C--sku Standard_Verizon

D--location eastus

Attempts:

3 left

💡 Hint

Common Mistakes

Using custom-domain, which is added separately after endpoint creation.

Using SKU, which is specified on the profile not the endpoint.

The --location flag is used to specify the location for the CDN endpoint.

2fill in blank

medium

Complete the code to enable HTTPS on a custom domain in Azure CDN.

Azure

az cdn custom-domain enable-https --resource-group myResourceGroup --profile-name myProfile --endpoint-name myEndpoint --name myCustomDomain [1]

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

A--certificate-source CdnManagedCertificate

B--certificate-source CustomCertificate

C--certificate-source AzureKeyVault

D--certificate-source None

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting AzureKeyVault without setting up the vault.

Choosing None disables HTTPS.

Using CdnManagedCertificate enables Azure to manage the HTTPS certificate automatically.

3fill in blank

hard

Fix the error in the command to map a custom domain to a CDN endpoint.

Azure

az cdn custom-domain create --resource-group myResourceGroup --profile-name myProfile --endpoint-name myEndpoint --hostname [1]

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

AmyProfile

BmyEndpoint

Cmycustomdomain.com

DmyResourceGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using the endpoint or resource group name instead of the domain.

Confusing profile name with hostname.

The --hostname parameter requires the custom domain name, not resource group or profile names.

4fill in blank

hard

Fill both blanks to create a CDN profile with the correct SKU and location.

Azure

az cdn profile create --name myProfile --resource-group myResourceGroup --sku [1] --location [2]

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

AStandard_Microsoft

Beastus

Cwestus

DPremium_Verizon

Attempts:

3 left

💡 Hint

Common Mistakes

Using Premium SKU with Standard location or vice versa.

Choosing invalid or unsupported regions.

The SKU Standard_Microsoft is a common choice, and eastus is a valid Azure region.

5fill in blank

hard

Fill all three blanks to configure a custom domain with HTTPS enabled using a managed certificate.

Azure

az cdn custom-domain create --resource-group myResourceGroup --profile-name myProfile --endpoint-name myEndpoint --name [2] --hostname [1] && az cdn custom-domain enable-https --resource-group myResourceGroup --profile-name myProfile --endpoint-name myEndpoint --name [2] --certificate-source [3]

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

Amycustomdomain.com

Bmycustomdomain

CCdnManagedCertificate

DAzureKeyVault

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing hostname and name parameters.

Choosing AzureKeyVault without proper setup.

The hostname is the full domain name, the custom domain name is usually the domain without extension, and the certificate source is set to CdnManagedCertificate for automatic HTTPS.