Custom domains and SSL in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a custom domain to an Azure App Service.

Azure

az webapp config hostname add --webapp-name myApp --resource-group myResourceGroup --hostname [1]

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

Awww.example.com

Bmyapp.azurewebsites.net

Cmyapp.com

Ddefaultdomain.net

Attempts:

3 left

💡 Hint

Common Mistakes

Using the default Azure domain instead of the custom domain.

Forgetting to specify the resource group.

The hostname parameter should be the custom domain you want to add, such as www.example.com.

2fill in blank

medium

Complete the command to bind a managed SSL certificate to your Azure App Service custom domain.

Azure

az webapp config ssl bind --certificate-thumbprint [1] --ssl-type SNI --name myApp --resource-group myResourceGroup --hostname www.example.com

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

AmyResourceGroup

B1234ABCD5678EFGH

CmyAppCertificate

Dwww.example.com

Attempts:

3 left

💡 Hint

Common Mistakes

Using the domain name instead of the certificate thumbprint.

Confusing resource group or app name with thumbprint.

The certificate-thumbprint is a unique identifier for the SSL certificate to bind.

3fill in blank

hard

Fix the error in the command to create a free managed SSL certificate for your custom domain.

Azure

az webapp config ssl create --resource-group myResourceGroup --name myApp --hostname [1]

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

AmyApp

Bmyapp.azurewebsites.net

CmyResourceGroup

Dwww.example.com

Attempts:

3 left

💡 Hint

Common Mistakes

Using the Azure default domain instead of the custom domain.

Confusing resource group or app name with hostname.

The hostname must be the custom domain you want the SSL certificate for, such as www.example.com.

4fill in blank

hard

Fill both blanks to configure a CNAME record for your custom domain pointing to your Azure app.

Azure

az network dns record-set cname create --resource-group myDNSGroup --zone-name example.com --name [1] --cname [2]

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

Awww

Bmyapp.azurewebsites.net

Cmyapp

Dexample.com

Attempts:

3 left

💡 Hint

Common Mistakes

Using the full domain name as the record name.

Setting the CNAME to the custom domain instead of the Azure app domain.

The name is the subdomain (like 'www'), and cname is the Azure app's default domain.

5fill in blank

hard

Fill all three blanks to create and bind a managed SSL certificate for your custom domain in Azure CLI.

Azure

thumbprint=$(az webapp config ssl create --resource-group [1] --name [2] --hostname [3] --query thumbprint -o tsv)
az webapp config ssl bind --certificate-thumbprint $thumbprint --ssl-type SNI --name [2] --resource-group [1] --hostname [3]

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

AmyResourceGroup

BmyApp

Cwww.example.com

Ddefaultdomain.net

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up resource group and app name.

Using the default Azure domain instead of the custom domain.

Use your resource group, app name, and custom domain to create and bind the SSL certificate properly.

Practice

1. What is the main purpose of adding a custom domain to an Azure web app?

easy

A. To increase the storage capacity of the web app

B. To use your own website name instead of Azure's default URL

C. To enable automatic backups of the web app

D. To improve the speed of the web app

Solution

1. Step 1: Understand what a custom domain is

   A custom domain lets you replace the default Azure URL with your own website name, making it easier for visitors to remember.

2. Step 2: Identify the purpose of using a custom domain

   Using your own domain improves branding and trust, not storage or speed.

3. Final Answer:

   To use your own website name instead of Azure's default URL -> Option B

4. Quick Check:

   Custom domain = Your own website name [OK]

Hint: Custom domain means your own website name, not Azure's URL [OK]

Common Mistakes:

• Confusing custom domain with storage or speed features
• Thinking custom domain automatically improves backups
• Assuming custom domain changes app performance

2. Which Azure CLI command is used to bind an SSL certificate to a web app's custom domain?

easy

A. az webapp domain bind

B. az webapp create ssl

C. az ssl certificate add

D. az webapp config ssl bind

Solution

1. Step 1: Recall Azure CLI commands for SSL binding

   The correct command to bind an SSL certificate to a web app is az webapp config ssl bind.

2. Step 2: Eliminate incorrect commands

   az webapp create ssl and az ssl certificate add are not valid commands. az webapp domain bind binds domains but not SSL certificates.

3. Final Answer:

   az webapp config ssl bind -> Option D

4. Quick Check:

   SSL bind command = az webapp config ssl bind [OK]

Hint: SSL bind uses 'az webapp config ssl bind' command [OK]

Common Mistakes:

• Using 'az webapp domain bind' for SSL binding
• Confusing create and bind commands
• Trying non-existent commands like 'az ssl certificate add'

3. Given this Azure CLI command:
az webapp config ssl bind --certificate-thumbprint abc123 --name myapp --resource-group mygroup --ssl-type SNI
What will this command do?

medium

A. Bind the SSL certificate with thumbprint abc123 to the web app myapp using SNI SSL

B. Create a new SSL certificate with thumbprint abc123 for the web app myapp

C. Remove the SSL certificate from the web app myapp

D. List all SSL certificates for the web app myapp

Solution

1. Step 1: Analyze the command parameters

   The command uses az webapp config ssl bind with a certificate thumbprint, web app name, resource group, and SSL type SNI.

2. Step 2: Understand the command effect

   This command binds the existing SSL certificate identified by thumbprint abc123 to the web app myapp using Server Name Indication (SNI) SSL.

3. Final Answer:

   Bind the SSL certificate with thumbprint abc123 to the web app myapp using SNI SSL -> Option A

4. Quick Check:

   SSL bind command with thumbprint = Bind SSL cert [OK]

Hint: Binding SSL uses thumbprint and 'az webapp config ssl bind' [OK]

Common Mistakes:

• Thinking the command creates or removes certificates
• Confusing listing certificates with binding
• Misunderstanding SNI SSL as removal

4. You tried to bind an SSL certificate to your Azure web app but got an error saying the certificate thumbprint was not found. What is the most likely cause?

medium

A. The SSL type SNI is not supported

B. The web app name is incorrect

C. The SSL certificate was not uploaded to the Azure resource group

D. The custom domain is not verified

Solution

1. Step 1: Understand the error about missing certificate thumbprint

   The error means Azure cannot find the SSL certificate with the given thumbprint in the resource group.

2. Step 2: Identify the cause

   This usually happens if the certificate was not uploaded or imported into the Azure resource group before binding.

3. Final Answer:

   The SSL certificate was not uploaded to the Azure resource group -> Option C

4. Quick Check:

   Missing thumbprint error = Certificate not uploaded [OK]

Hint: Upload SSL cert before binding to avoid thumbprint errors [OK]

Common Mistakes:

• Assuming web app name causes thumbprint errors
• Thinking SNI SSL is unsupported
• Ignoring domain verification as cause

5. You want to secure your Azure web app with a custom domain and SSL. Which sequence of steps is correct?

hard

A. Add custom domain to web app, upload SSL certificate, then bind SSL certificate to domain

B. Bind SSL certificate to web app, then add custom domain, then upload SSL certificate

C. Upload SSL certificate, add custom domain, then bind SSL certificate to domain

D. Add custom domain, bind SSL certificate, then upload SSL certificate

Solution

1. Step 1: Add the custom domain to the Azure web app

   You must first add your custom domain to the web app so Azure knows which domain to secure.

2. Step 2: Upload the SSL certificate to Azure

   Next, upload the SSL certificate to the Azure resource group to make it available for binding.

3. Step 3: Bind the SSL certificate to the custom domain

   Finally, bind the uploaded SSL certificate to the custom domain on the web app to enable HTTPS.

4. Final Answer:

   Add custom domain to web app, upload SSL certificate, then bind SSL certificate to domain -> Option A

5. Quick Check:

   Domain add -> cert upload -> cert bind [OK]

Hint: Add domain first, upload cert second, bind cert last [OK]

Common Mistakes:

• Trying to bind SSL before uploading certificate
• Binding SSL before adding custom domain
• Uploading certificate after binding