Bird
Raised Fist0
Azurecloud~5 mins

Azure Resource Manager (ARM) concept - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Introduction
Managing cloud resources can be confusing when done one by one. Azure Resource Manager helps organize and control these resources together as a group, making deployment and management easier and consistent.
When you want to deploy multiple related cloud resources like virtual machines, storage, and networks together.
When you need to update or delete a group of resources safely without affecting others.
When you want to track and control access to your cloud resources in a clear way.
When you want to automate deployments using a reusable template.
When you want to see all resources related to a project in one place.
Config File - azuredeploy.json
azuredeploy.json
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "storageAccountName": {
      "type": "string",
      "defaultValue": "examplestorage123",
      "metadata": {
        "description": "Name of the storage account"
      }
    }
  },
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2022-09-01",
      "name": "[parameters('storageAccountName')]",
      "location": "eastus",
      "sku": {
        "name": "Standard_LRS"
      },
      "kind": "StorageV2",
      "properties": {}
    }
  ],
  "outputs": {
    "storageAccountId": {
      "type": "string",
      "value": "[resourceId('Microsoft.Storage/storageAccounts', parameters('storageAccountName'))]"
    }
  }
}

This JSON file is an ARM template that defines a storage account resource.

parameters: Allows setting the storage account name when deploying.

resources: Defines the storage account with location, SKU, and kind.

outputs: Returns the resource ID of the created storage account after deployment.

Commands
This command creates a resource group named 'exampleResourceGroup' in the East US region. Resource groups hold related resources together.
Terminal
az group create --name exampleResourceGroup --location eastus
Expected OutputExpected
{ "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/exampleResourceGroup", "location": "eastus", "managedBy": null, "name": "exampleResourceGroup", "properties": { "provisioningState": "Succeeded" }, "tags": {}, "type": "Microsoft.Resources/resourceGroups" }
→
--name - Sets the name of the resource group
→
--location - Specifies the Azure region for the resource group
This command deploys the ARM template file 'azuredeploy.json' to the resource group 'exampleResourceGroup', creating the storage account defined in the template.
Terminal
az deployment group create --resource-group exampleResourceGroup --template-file azuredeploy.json
Expected OutputExpected
{ "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/exampleResourceGroup/providers/Microsoft.Resources/deployments/deployment202406", "name": "deployment202406", "properties": { "provisioningState": "Succeeded", "outputs": { "storageAccountId": { "type": "String", "value": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/exampleResourceGroup/providers/Microsoft.Storage/storageAccounts/examplestorage123" } } }, "resourceGroup": "exampleResourceGroup", "timestamp": "2024-06-01T12:00:00Z", "type": "Microsoft.Resources/deployments" }
→
--resource-group - Specifies the target resource group for deployment
→
--template-file - Points to the ARM template file to deploy
This command retrieves details about the storage account named 'examplestorage123' in the resource group to verify it was created successfully.
Terminal
az storage account show --name examplestorage123 --resource-group exampleResourceGroup
Expected OutputExpected
{ "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/exampleResourceGroup/providers/Microsoft.Storage/storageAccounts/examplestorage123", "location": "eastus", "name": "examplestorage123", "primaryEndpoints": { "blob": "https://examplestorage123.blob.core.windows.net/", "file": "https://examplestorage123.file.core.windows.net/", "queue": "https://examplestorage123.queue.core.windows.net/", "table": "https://examplestorage123.table.core.windows.net/" }, "sku": { "name": "Standard_LRS" }, "tags": {}, "type": "Microsoft.Storage/storageAccounts" }
→
--name - Specifies the storage account name to show
→
--resource-group - Specifies the resource group containing the storage account
Key Concept

If you remember nothing else from this pattern, remember: ARM templates let you define and manage related Azure resources together as one unit for easy deployment and control.

Common Mistakes
Trying to deploy an ARM template without creating the resource group first.
The deployment fails because the target resource group does not exist to hold the resources.
Always create the resource group with 'az group create' before deploying the ARM template.
Using an invalid or missing parameter value in the ARM template during deployment.
Deployment fails or creates resources with wrong names or settings.
Check and provide correct parameter values either in the template or via command line parameters.
Not verifying the deployment result and assuming resources were created.
You might think resources exist when deployment failed or was incomplete.
Use commands like 'az storage account show' or 'az deployment group show' to confirm successful deployment.
Summary
Create a resource group to hold your Azure resources.
Deploy an ARM template to create and configure resources in that group.
Verify the resources were created successfully using Azure CLI commands.

Practice

(1/5)
1. What is the main purpose of Azure Resource Manager (ARM)?
easy
A. To write code for mobile applications
B. To manage and organize cloud resources as a group
C. To monitor network traffic only
D. To create virtual machines manually

Solution

  1. Step 1: Understand ARM's role

    ARM is designed to help manage cloud resources together, not individually.

  2. Step 2: Compare options

    Options B, C, and D describe unrelated tasks, while A correctly describes ARM's purpose.

  3. Final Answer:

    To manage and organize cloud resources as a group -> Option B

  4. Quick Check:

    ARM manages resources as a group = A [OK]
Hint: ARM groups resources for easy management [OK]
Common Mistakes:
  • Thinking ARM is only for virtual machines
  • Confusing ARM with monitoring tools
  • Assuming ARM writes application code
2. Which of the following is the correct way to deploy resources using ARM templates?
easy
A. Using FTP to upload ARM templates
B. Writing scripts in Python only
C. Using Azure Portal or Azure CLI with the ARM template
D. Manually creating resources without templates

Solution

  1. Step 1: Identify deployment methods

    ARM templates are deployed via Azure Portal or Azure CLI commands.

  2. Step 2: Eliminate incorrect options

    Python scripts and FTP are not standard deployment methods for ARM templates; manual creation ignores automation benefits.

  3. Final Answer:

    Using Azure Portal or Azure CLI with the ARM template -> Option C

  4. Quick Check:

    Deploy ARM templates via Portal or CLI = D [OK]
Hint: Deploy ARM templates via Portal or CLI commands [OK]
Common Mistakes:
  • Thinking ARM templates deploy only with scripts
  • Assuming manual creation is deployment
  • Confusing FTP with deployment method
3. Given this ARM template snippet:
{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2021-04-01",
      "name": "mystorageaccount",
      "location": "eastus",
      "sku": { "name": "Standard_LRS" },
      "kind": "StorageV2"
    }
  ]
}

What resource will this template create when deployed?
medium
A. A storage account named mystorageaccount in East US region
B. A virtual machine named mystorageaccount
C. A database named mystorageaccount
D. A network interface named mystorageaccount

Solution

  1. Step 1: Analyze resource type in template

    The resource type is "Microsoft.Storage/storageAccounts", which means a storage account.

  2. Step 2: Check resource properties

    The name is "mystorageaccount" and location is "eastus", confirming the storage account details.

  3. Final Answer:

    A storage account named mystorageaccount in East US region -> Option A

  4. Quick Check:

    Resource type storageAccounts = storage account = A [OK]
Hint: Resource type defines what is created in ARM template [OK]
Common Mistakes:
  • Confusing storage account with virtual machine
  • Ignoring resource type and focusing on name
  • Assuming location affects resource type
4. You try to deploy an ARM template but get an error saying the resource name is invalid. What is the most likely cause?
medium
A. The template schema URL is missing
B. The location is not specified
C. The API version is too old
D. The resource name contains unsupported characters

Solution

  1. Step 1: Understand error message

    An invalid resource name error usually means the name has characters not allowed by Azure naming rules.

  2. Step 2: Review other options

    Missing schema URL or old API version cause different errors; location missing usually triggers a different message.

  3. Final Answer:

    The resource name contains unsupported characters -> Option D

  4. Quick Check:

    Invalid name error = unsupported characters in name = B [OK]
Hint: Check resource name for invalid characters first [OK]
Common Mistakes:
  • Assuming schema URL causes name errors
  • Ignoring naming rules for resources
  • Thinking location omission causes name errors
5. You want to deploy multiple resources together and ensure they are created in the right order using ARM templates. Which feature should you use?
hard
A. Define dependencies between resources using the "dependsOn" property
B. Deploy each resource separately in different templates
C. Use manual deployment steps outside ARM
D. Create resources without specifying order

Solution

  1. Step 1: Identify how ARM manages resource order

    ARM uses the "dependsOn" property to specify which resources must be created first.

  2. Step 2: Evaluate other options

    Deploying separately or manually loses automation benefits; no order risks deployment failures.

  3. Final Answer:

    Define dependencies between resources using the "dependsOn" property -> Option A

  4. Quick Check:

    Use dependsOn to control deployment order = C [OK]
Hint: Use dependsOn to set resource creation order [OK]
Common Mistakes:
  • Deploying resources separately instead of together
  • Ignoring dependsOn and causing deployment errors
  • Relying on manual steps outside ARM
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard