Resource naming conventions in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a resource group with a valid name.

Azure

az group create --name [1] --location eastus

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

A123ResourceGroup

Bmy_resource_group!

CResource Group

DMyResourceGroup1

Attempts:

3 left

💡 Hint

Common Mistakes

Using spaces or special characters in the resource group name.

Starting the name with a number.

Resource group names must be alphanumeric and can include numbers. No spaces or special characters allowed.

2fill in blank

medium

Complete the code to create a storage account with a valid name.

Azure

az storage account create --name [1] --resource-group MyResourceGroup1 --location eastus --sku Standard_LRS

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

Astorage_account

BStorageAccount

Cstorageaccount123

DStorage-Account

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase letters in the storage account name.

Including underscores or hyphens.

Storage account names must be between 3 and 24 characters, lowercase letters and numbers only, no underscores or hyphens.

3fill in blank

hard

Fix the error in the storage account name to meet Azure naming rules.

Azure

az storage account create --name [1] --resource-group MyResourceGroup1 --location eastus --sku Standard_LRS

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

Astorageaccount!

Bstorageaccount123

Cstorage_account

DStorageAccount

Attempts:

3 left

💡 Hint

Common Mistakes

Including special characters like exclamation marks.

Using uppercase letters.

The storage account name must be lowercase letters and numbers only, no special characters or underscores.

4fill in blank

hard

Fill both blanks to create a virtual network with a valid name and address prefix.

Azure

az network vnet create --name [1] --resource-group MyResourceGroup1 --address-prefix [2] --location eastus

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

AmyVnet

B10.0.0.0/16

Cmy_vnet

D192.168.0.0/33

Attempts:

3 left

💡 Hint

Common Mistakes

Using underscores in the virtual network name.

Using an invalid CIDR address prefix.

Virtual network names can include letters and numbers without underscores. Address prefix must be a valid CIDR block.

5fill in blank

hard

Fill all three blanks to create an Azure SQL server with a valid name, admin username, and location.

Azure

az sql server create --name [1] --resource-group MyResourceGroup1 --location [2] --admin-user [3] --admin-password MyP@ssw0rd!

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

Asqlserver01

Beastus

Csqladmin

Dsql_server

Attempts:

3 left

💡 Hint

Common Mistakes

Using underscores in the server name.

Using invalid region names.

Using complex or invalid admin usernames.

SQL server names must be lowercase letters and numbers only, no underscores. Admin username should be simple and valid. Location must be a valid Azure region.

Practice

1. Which of the following is a best practice for naming Azure resources?

easy

A. Include environment, resource type, and location in the name

B. Use spaces and special characters freely

C. Keep names very short without any identifiers

D. Use only uppercase letters for all resource names

Solution

1. Step 1: Understand Azure naming best practices

   Azure recommends including environment (like dev or prod), resource type, and location to organize resources clearly.

2. Step 2: Evaluate each option

   Including environment, resource type, and location in the name follows best practices. Using spaces and special characters freely, keeping names very short without any identifiers, and using only uppercase letters for all resource names do not follow best practices or reduce clarity.

3. Final Answer:

   Include environment, resource type, and location in the name -> Option A

4. Quick Check:

   Best practice = Include environment, type, location [OK]

Hint: Names should describe environment, type, and location [OK]

Common Mistakes:

• Using spaces or special characters
• Ignoring environment or location in names
• Using inconsistent casing

2. Which of these Azure resource names is valid according to Azure naming rules?

easy

A. my-resource-01

B. my resource 01

C. myResource_01

D. myResource@01

Solution

1. Step 1: Recall Azure naming rules

   Azure allows letters, numbers, and hyphens (-) but not spaces or special characters like underscores (_) or @.

2. Step 2: Check each option

   my-resource-01 uses only letters, numbers, and hyphens, so it's valid. myResource_01 contains an underscore, my resource 01 contains spaces, and myResource@01 contains @, all invalid characters.

3. Final Answer:

   my-resource-01 -> Option A

4. Quick Check:

   Valid characters = letters, numbers, hyphens [OK]

Hint: Use only letters, numbers, and hyphens in names [OK]

Common Mistakes:

• Using underscores or spaces
• Including special characters like @ or #
• Starting or ending names with hyphens

3. Given the resource name prod-webapp-eastus-001, what does this name most likely represent?

medium

A. A development database in West Europe region

B. A production web application in East US region with unique ID 001

C. A test storage account in Central US region

D. An invalid resource name with no meaning

Solution

1. Step 1: Break down the resource name parts

   "prod" means production environment, "webapp" is resource type, "eastus" is location, "001" is unique ID.

2. Step 2: Match parts to options

   A production web application in East US region with unique ID 001 matches all parts correctly. Other options mention wrong environment, type, or location.

3. Final Answer:

   A production web application in East US region with unique ID 001 -> Option B

4. Quick Check:

   prod + webapp + eastus + 001 = A production web application in East US region with unique ID 001 [OK]

Hint: Split name by hyphens to identify parts [OK]

Common Mistakes:

• Confusing environment or location codes
• Ignoring unique ID meaning
• Assuming invalid names

4. You try to create an Azure storage account named storage_account_01 but get an error. What is the most likely cause?

medium

A. Storage account names cannot include numbers

B. Storage account names must be uppercase

C. Storage account names cannot contain underscores

D. Storage account names must be longer than 30 characters

Solution

1. Step 1: Recall storage account naming rules

   Storage account names must be lowercase letters and numbers only, no underscores allowed.

2. Step 2: Analyze the error cause

   The name contains an underscore, which is invalid. Other options are incorrect rules.

3. Final Answer:

   Storage account names cannot contain underscores -> Option C

4. Quick Check:

   Underscores not allowed in storage account names [OK]

Hint: Storage names allow only lowercase letters and numbers [OK]

Common Mistakes:

• Using uppercase letters
• Including underscores or special characters
• Misunderstanding length limits

5. You need to create a naming convention for Azure resources that includes environment, resource type, location, and a unique ID. Which of the following names follows best practices and Azure rules?

hard

A. Dev_VM_WestUS_01

B. dev-vm-westus-01!

C. devvmwestus01

D. dev-vm-westus-01

Solution

1. Step 1: Check naming convention components

   The name should include environment (dev), resource type (vm), location (westus), and unique ID (01) separated by hyphens.

2. Step 2: Validate Azure naming rules

   dev-vm-westus-01 uses lowercase letters, hyphens, and no invalid characters. Dev_VM_WestUS_01 uses uppercase and underscores, devvmwestus01 lacks separators, dev-vm-westus-01! has an exclamation mark.

3. Final Answer:

   dev-vm-westus-01 -> Option D

4. Quick Check:

   Lowercase + hyphens + all parts = dev-vm-westus-01 [OK]

Hint: Use lowercase and hyphens to separate parts [OK]

Common Mistakes:

• Using uppercase letters or underscores
• Missing separators between parts
• Including special characters