Resource naming conventions in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of resource naming conventions in Azure?

Resource naming conventions help organize, identify, and manage Azure resources easily and consistently across teams and projects.

beginner

Name two common elements included in Azure resource names.

Common elements include the resource type (like vm for virtual machine) and environment (like dev for development).

beginner

Why should resource names avoid using spaces and special characters?

Spaces and special characters can cause errors or be unsupported by Azure services, so using only letters, numbers, and hyphens ensures compatibility.

intermediate

What is a typical format for an Azure resource name?

A typical format is: <project>-<environment>-<resourceType>-<instanceNumber>, for example, 'webapp-prod-app01'.

intermediate

How do naming conventions help with automation and scripting in Azure?

Consistent names make it easier to write scripts that find, update, or delete resources without errors or confusion.

Which character is recommended to separate parts of an Azure resource name?

A - (hyphen)

B _ (underscore)

C Space

D # (hash)

Hyphens are widely supported and recommended to separate parts of resource names in Azure.

Why should resource names be consistent across a project?

A To confuse team members

B To avoid using tags

C To increase resource costs

D To make resources easier to find and manage

Consistency helps teams quickly identify and manage resources.

Which of these is NOT a good practice for Azure resource names?

A Using lowercase letters

B Including environment info like 'dev' or 'prod'

C Using spaces between words

D Including resource type abbreviation

Spaces are not allowed and can cause errors in Azure resource names.

What is the maximum length for most Azure resource names?

A 10 characters

B 63 characters

C 256 characters

D No limit

Most Azure resources have a maximum name length of 63 characters.

Which of these is a good example of an Azure resource name?

A webapp-prod-app01

B My VM #1

C Storage Account!

D dev app server

'webapp-prod-app01' follows naming conventions with hyphens and no spaces or special characters.

Explain why using a consistent resource naming convention is important in Azure.

Think about how teams find and manage resources.

Describe a simple naming format you could use for Azure resources in a project.

Try to include parts that help identify the resource purpose and environment.

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