Why automation matters in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a resource group automatically in Azure.

Azure

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

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

Aeastus

BMyResourceGroup

Cvm1

Dstorageaccount

Attempts:

3 left

💡 Hint

Common Mistakes

Using location value instead of the resource group name.

Confusing resource group name with resource names.

The --name parameter specifies the resource group name, which is required to create it.

2fill in blank

medium

Complete the code to deploy a virtual machine automatically using Azure CLI.

Azure

az vm create --resource-group MyResourceGroup --name [1] --image UbuntuLTS

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

AMyVM

Beastus

CMyResourceGroup

DUbuntuLTS

Attempts:

3 left

💡 Hint

Common Mistakes

Using location or resource group name instead of VM name.

Confusing image name with VM name.

The --name parameter specifies the name of the virtual machine to create.

3fill in blank

hard

Fix the error in the command to automate storage account creation.

Azure

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

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

AMyResourceGroup

Beastus

Cmystorageaccount

DStandard_LRS

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase letters or spaces in the storage account name.

Confusing resource group or location with storage account name.

The --name parameter requires a unique storage account name in lowercase letters and numbers only.

4fill in blank

hard

Fill both blanks to automate creating a network security group and associating it with a subnet.

Azure

az network nsg create --resource-group MyResourceGroup --name [1]
az network vnet subnet update --resource-group MyResourceGroup --vnet-name MyVNet --name MySubnet --network-security-group [2]

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

AMyNSG

BMyVNet

DMySubnet

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for NSG creation and association.

Confusing subnet or virtual network names with NSG name.

The network security group name must be the same when creating and associating it with the subnet.

5fill in blank

hard

Fill all three blanks to automate tagging resources during creation.

Azure

az resource tag --tags [1]=[2] --resource-group MyResourceGroup --resource-type Microsoft.Compute/virtualMachines --name [3]

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

Aenvironment

Bproduction

CMyVM

Dlocation

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up tag keys and values.

Using incorrect resource names.

Tags help organize resources. Here, 'environment' is the tag key, 'production' is the value, and 'MyVM' is the resource name.

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