Resource naming conventions in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Azure resource name length limits

Azure resources have specific length limits for their names. Which of the following resource names is valid for an Azure Storage Account?

A storageaccount12345678901234567890

B storageaccounttoolong1234567890123456789012345

C storage_account_with_underscores

D stgacc

💡 Hint

Azure Storage Account names must be between 3 and 24 characters, and only lowercase letters and numbers are allowed.

Option D is valid because it is between 3 and 24 characters and contains only lowercase letters. Option D is too long (more than 24 characters). Option D contains underscores which are not allowed. Option D is too long.

❓ Architecture

intermediate

Choosing resource names for environment separation

You want to name Azure resources to clearly separate development and production environments. Which naming pattern best supports this goal?

A app-prod-webserver, app-dev-webserver

B appwebserver1, appwebserver2

C webserver-prod, webserver-prod2

D prodappwebserver, devappwebserver

💡 Hint

Think about clarity and consistency in naming to identify environment quickly.

Option A clearly includes environment tags 'prod' and 'dev' in the same position, making it easy to identify and group resources by environment. Other options are less clear or inconsistent.

❓ security

advanced

Avoiding sensitive information in resource names

Which of the following Azure resource names best avoids exposing sensitive information?

A dbserver-prod-001

B finance-prod-db-server-nyc

C finance-prod-db-password123

D nyc-finance-prod-db

💡 Hint

Resource names should not contain passwords or sensitive data.

Option A uses generic identifiers without sensitive info. Option A includes a password in the name, which is a security risk. Options A and B include business or location info that might be sensitive.

✅ Best Practice

advanced

Consistent resource naming for automation

Which naming convention is best for automating resource management scripts in Azure?

A resGrp1, resGrp2, resGrp3

B rg-prod-eastus-001, rg-prod-eastus-002, rg-prod-eastus-003

C prod-eastus-rg-1, prod-eastus-rg-2, prod-eastus-rg-3

D eastus-prod-rg-01, eastus-prod-rg-02, eastus-prod-rg-03

💡 Hint

Automation benefits from predictable, structured names including environment, region, and sequence.

Option B includes environment, region, and a sequence number in a consistent order, making it easy for scripts to parse and manage resources. Other options are less consistent or less clear.

❓ service_behavior

expert

Impact of resource name on Azure DNS resolution

Consider an Azure App Service with the name 'myappservice123'. What is the fully qualified domain name (FQDN) automatically assigned to this app service?

A myappservice123.azure.com

B myappservice123.windows.net

C myappservice123.azurewebsites.net

D myappservice123.cloudapp.net

💡 Hint

Azure App Services use a specific domain suffix for their default URLs.

The default domain for Azure App Services is 'azurewebsites.net'. So the FQDN is 'myappservice123.azurewebsites.net'. Other domains belong to different Azure services.

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