Why automation matters in Azure - See It in Action

Why Automation Matters in Azure Cloud

📖 Scenario: You are working as a cloud engineer for a small company. The company wants to manage its Azure resources more efficiently. Right now, they create virtual machines manually, which takes a lot of time and can cause mistakes.Your task is to create a simple automation setup that defines virtual machines in a structured way and then uses a configuration variable to control how many machines to create. This will help the company save time and avoid errors.

🎯 Goal: Build a basic Azure automation script that defines virtual machines, uses a configuration variable to control the number of machines, and applies a loop to prepare the deployment plan. Finally, complete the script with a tag that marks the deployment as automated.

📋 What You'll Learn

Create a dictionary called vm_templates with exact VM names and sizes

Add a configuration variable called vm_count with the value 3

Use a for loop with variables vm_name and vm_size to iterate over vm_templates.items()

Add a final line that sets deployment_tag = 'AutomatedDeployment'

💡 Why This Matters

🌍 Real World

Automating cloud resource creation saves time and reduces errors in real companies managing Azure infrastructure.

💼 Career

Cloud engineers and DevOps professionals use automation scripts like this to deploy and manage resources efficiently.

1

Create VM templates dictionary

Create a dictionary called vm_templates with these exact entries: 'webserver': 'Standard_B1s', 'database': 'Standard_B2s', 'cache': 'Standard_B1ms'

Azure

# Create a dictionary called vm_templates with VM names and sizes
# Your code here

Hint

Use curly braces {} to create a dictionary with keys and values.

2

Add VM count configuration

Add a configuration variable called vm_count and set it to 3

Azure

vm_templates = {
    'webserver': 'Standard_B1s',
    'database': 'Standard_B2s',
    'cache': 'Standard_B1ms'
}
# Add a variable vm_count and set it to 3
# Your code here

Hint

Just assign the number 3 to the variable vm_count.

3

Loop over VM templates

Use a for loop with variables vm_name and vm_size to iterate over vm_templates.items()

Azure

vm_templates = {
    'webserver': 'Standard_B1s',
    'database': 'Standard_B2s',
    'cache': 'Standard_B1ms'
}
vm_count = 3
# Use a for loop to iterate over vm_templates.items()
# Your code here

Hint

Use for vm_name, vm_size in vm_templates.items(): to loop through the dictionary.

4

Add deployment tag

Add a final line that sets deployment_tag = 'AutomatedDeployment'

Azure

vm_templates = {
    'webserver': 'Standard_B1s',
    'database': 'Standard_B2s',
    'cache': 'Standard_B1ms'
}
vm_count = 3
for vm_name, vm_size in vm_templates.items():
    pass
# Add deployment_tag variable with value 'AutomatedDeployment'
# Your code here

Hint

Assign the string 'AutomatedDeployment' to the variable deployment_tag.

Practice

1. Why is automation important in managing Azure cloud resources?

easy

A. It removes the need for any monitoring.

B. It makes the cloud slower to respond.

C. It increases manual work for administrators.

D. It saves time and reduces human errors.

Solution

1. Step 1: Understand the role of automation

   Automation helps perform tasks faster and with fewer mistakes compared to manual work.

2. Step 2: Identify the benefits in Azure context

   In Azure, automation saves time and reduces errors when managing resources.

3. Final Answer:

   It saves time and reduces human errors. -> Option D

4. Quick Check:

   Automation = saves time and reduces errors [OK]

Hint: Automation reduces errors and saves time [OK]

Common Mistakes:

• Thinking automation slows down processes
• Believing automation increases manual work
• Assuming automation removes all monitoring needs

2. Which of the following is a correct Azure CLI command to create a resource group named MyGroup in the eastus region?

easy

A. az group new --name eastus --location MyGroup

B. az create group --location MyGroup eastus

C. az group create --name MyGroup --location eastus

D. az resource create --group MyGroup --region eastus

Solution

1. Step 1: Recall Azure CLI syntax for resource group creation

   The correct command uses az group create with --name and --location flags.

2. Step 2: Match the command with the options

   az group create --name MyGroup --location eastus matches the correct syntax and parameters.

3. Final Answer:

   az group create --name MyGroup --location eastus -> Option C

4. Quick Check:

   Correct Azure CLI syntax = az group create --name MyGroup --location eastus [OK]

Hint: Use 'az group create --name <name> --location <region>' [OK]

Common Mistakes:

• Swapping parameter order
• Using wrong command verbs like 'new' or 'create group'
• Confusing resource group with resource commands

3. Given this Azure CLI script snippet:

az group create --name TestGroup --location westus
az vm create --resource-group TestGroup --name TestVM --image UbuntuLTS --generate-ssh-keys

What will be the result after running it?

medium

A. The script will fail because SSH keys are missing.

B. A resource group named TestGroup and a VM named TestVM are created in westus.

C. Only a VM named TestVM is created without a resource group.

D. A resource group is created but no VM is created.

Solution

1. Step 1: Analyze the first command

   The first command creates a resource group named TestGroup in the westus region.

2. Step 2: Analyze the second command

   The second command creates a VM named TestVM inside TestGroup with Ubuntu image and auto-generated SSH keys.

3. Final Answer:

   A resource group named TestGroup and a VM named TestVM are created in westus. -> Option B

4. Quick Check:

   Resource group + VM created = A resource group named TestGroup and a VM named TestVM are created in westus. [OK]

Hint: Check commands create both group and VM with keys [OK]

Common Mistakes:

• Assuming SSH keys must be manually provided
• Thinking VM can be created without resource group
• Believing only one resource is created

4. You wrote this ARM template snippet to automate resource creation:

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2019-06-01",
      "name": "mystorageaccount",
      "location": "eastus",
      "sku": { "name": "Standard_LRS" },
      "kind": "StorageV2"
    }
  ]
}

When deploying, you get an error about the storage account name. What is the likely cause?

medium

A. Storage account names must be globally unique and lowercase.

B. The location 'eastus' is invalid for storage accounts.

C. The API version is outdated and unsupported.

D. The SKU name 'Standard_LRS' is not allowed.

Solution

1. Step 1: Understand storage account naming rules

   Storage account names must be unique across Azure and use only lowercase letters and numbers.

2. Step 2: Check the template name

   The name "mystorageaccount" is lowercase but may not be unique; uniqueness is the common cause of deployment errors.

3. Final Answer:

   Storage account names must be globally unique and lowercase. -> Option A

4. Quick Check:

   Storage account name uniqueness = Storage account names must be globally unique and lowercase. [OK]

Hint: Storage account names must be unique and lowercase [OK]

Common Mistakes:

• Ignoring uniqueness requirement
• Assuming location or SKU causes name errors
• Not checking API version compatibility

5. You want to automate deployment of multiple identical virtual machines in Azure using an ARM template. Which approach best ensures consistency and easy management?

hard

A. Use a single ARM template with a copy loop to create multiple VMs.

B. Manually create each VM in the Azure portal one by one.

C. Write separate ARM templates for each VM with different names.

D. Deploy VMs using different scripts for each machine.

Solution

1. Step 1: Identify automation best practice for multiple resources

   Using a copy loop in an ARM template allows creating many identical resources efficiently and consistently.

2. Step 2: Compare other options

   Manual creation or separate templates/scripts increase errors and management complexity.

3. Final Answer:

   Use a single ARM template with a copy loop to create multiple VMs. -> Option A

4. Quick Check:

   Copy loop in ARM template = consistent automation [OK]

Hint: Use ARM template copy loops for multiple identical resources [OK]

Common Mistakes:

• Creating resources manually defeats automation purpose
• Writing separate templates increases errors
• Using different scripts complicates management