Bird
Raised Fist0
Azurecloud~5 mins

ARM template resources section in Azure - Time & Space Complexity

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Time Complexity: ARM template resources section
O(n)
Understanding Time Complexity

When deploying infrastructure with ARM templates, it's important to understand how the deployment time grows as you add more resources.

We want to know: How does adding more resources affect the number of deployment operations?

Scenario Under Consideration

Analyze the time complexity of deploying multiple resources defined in the ARM template's resources section.


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

This template deploys two storage accounts as separate resources.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

  • Primary operation: Deploying each resource defined in the resources array.
  • How many times: Once per resource listed in the resources section.
How Execution Grows With Input

Each resource requires a separate deployment operation, so as you add more resources, the number of operations grows directly with the number of resources.

Input Size (n)Approx. Api Calls/Operations
1010 resource deployments
100100 resource deployments
10001000 resource deployments

Pattern observation: The number of deployment operations increases linearly as you add more resources.

Final Time Complexity

Time Complexity: O(n)

This means deployment time grows in direct proportion to the number of resources you define.

Common Mistake

[X] Wrong: "Adding more resources won't affect deployment time much because Azure deploys everything instantly."

[OK] Correct: Each resource requires its own deployment call and provisioning time, so more resources mean more work and longer deployment.

Interview Connect

Understanding how deployment time scales with resource count helps you design efficient templates and estimate deployment durations in real projects.

Self-Check

What if we used nested templates to deploy resources instead? How would that change the time complexity?

Practice

(1/5)
1. What is the main purpose of the resources section in an ARM template?
easy
A. To list all cloud parts to create or update
B. To write scripts for manual deployment
C. To store user credentials securely
D. To monitor cloud resource usage

Solution

  1. Step 1: Understand the role of the resources section

    The resources section defines what cloud parts (like servers, databases) to create or update automatically.

  2. Step 2: Compare options with this role

    Only To list all cloud parts to create or update correctly describes this purpose. Other options describe unrelated tasks.

  3. Final Answer:

    To list all cloud parts to create or update -> Option A

  4. Quick Check:

    Resources section = list cloud parts [OK]
Hint: Resources section always defines cloud parts to deploy [OK]
Common Mistakes:
  • Thinking resources section stores credentials
  • Confusing resources with monitoring tools
  • Assuming resources section is for scripts
2. Which of the following is a required property inside each resource in the resources section of an ARM template?
easy
A. version
B. dependsOn
C. location
D. tags

Solution

  1. Step 1: Identify required properties for each resource

    Every Azure resource requires type, apiVersion, and name. The location property is required for regional resources to specify where the resource is created.

  2. Step 2: Check options for required property

    location (location) is required. version is incorrect; the correct property is apiVersion. tags and dependsOn are optional.

  3. Final Answer:

    location -> Option C

  4. Quick Check:

    Location is required for resource placement [OK]
Hint: Location is required for regional resources [OK]
Common Mistakes:
  • Confusing apiVersion with version
  • Assuming tags are mandatory
  • Thinking dependsOn is always required
3. Given this resource snippet in an ARM template's resources section:
{
  "type": "Microsoft.Storage/storageAccounts",
  "apiVersion": "2022-09-01",
  "name": "mystorageaccount",
  "location": "eastus",
  "sku": { "name": "Standard_LRS" },
  "kind": "StorageV2"
}

What will happen when this template is deployed?
medium
A. Deployment fails due to missing 'dependsOn' property
B. A new storage account named 'mystorageaccount' is created in East US
C. The storage account is created but with default SKU
D. The template will error because 'kind' is invalid

Solution

  1. Step 1: Analyze resource properties

    The resource defines a storage account with a valid type, apiVersion, name, location, sku, and kind. All required fields are present and valid.

  2. Step 2: Understand deployment behavior

    Since all required properties are correct, deployment will create the storage account named 'mystorageaccount' in 'eastus' with the specified SKU and kind. dependsOn is optional here.

  3. Final Answer:

    A new storage account named 'mystorageaccount' is created in East US -> Option B

  4. Quick Check:

    Valid resource properties = successful creation [OK]
Hint: Check required fields; missing dependsOn is okay if no dependencies [OK]
Common Mistakes:
  • Thinking dependsOn is always mandatory
  • Assuming default SKU applies if specified
  • Believing 'kind' property is invalid
4. You have this resource in your ARM template's resources section:
{
  "type": "Microsoft.Web/sites",
  "apiVersion": "2021-02-01",
  "name": "mywebapp",
  "location": "westus"
}

Deployment fails with an error about missing properties. What is the likely cause?
medium
A. Missing 'properties' section with site configuration
B. Missing required 'kind' property for web app
C. Missing 'dependsOn' property for resource order
D. Missing 'sku' property defining pricing tier

Solution

  1. Step 1: Review required properties for Microsoft.Web/sites

    Besides type, apiVersion, name, and location, a web app resource requires a properties section to define site settings.

  2. Step 2: Identify missing required section

    The snippet lacks the properties section, causing deployment failure. sku and dependsOn are optional, and kind defaults to 'app' if omitted.

  3. Final Answer:

    Missing 'properties' section with site configuration -> Option A

  4. Quick Check:

    Web app needs properties section [OK]
Hint: Web apps require properties section; check for it [OK]
Common Mistakes:
  • Assuming dependsOn is mandatory
  • Confusing kind as required
  • Ignoring properties section necessity
5. You want to deploy two resources in an ARM template: a storage account and a web app that uses that storage. How do you ensure the web app deploys only after the storage account is ready?
hard
A. Use the same 'apiVersion' for both resources
B. Place the web app resource before the storage account in the resources array
C. Set the web app's 'location' to the storage account's location
D. Add the storage account's name in the web app's 'dependsOn' property

Solution

  1. Step 1: Understand resource deployment order control

    ARM templates use the dependsOn property to specify that one resource must finish deploying before another starts.

  2. Step 2: Apply dependsOn for correct order

    Adding the storage account's resource name in the web app's dependsOn ensures the web app waits for the storage account to be ready.

  3. Final Answer:

    Add the storage account's name in the web app's 'dependsOn' property -> Option D

  4. Quick Check:

    dependsOn controls deployment order [OK]
Hint: Use dependsOn to order resource deployment [OK]
Common Mistakes:
  • Thinking resource order in array controls deployment
  • Believing apiVersion affects deployment order
  • Assuming location controls deployment sequence