Availability sets for redundancy in Azure - Time & Space Complexity

Time Complexity: Availability sets for redundancy

O(n)

Understanding Time Complexity

We want to understand how the time to deploy and manage virtual machines changes when using availability sets for redundancy in Azure.

How does adding more virtual machines affect the operations needed to keep them highly available?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Create an availability set
az vm availability-set create --name MyAvailabilitySet --resource-group MyResourceGroup --platform-fault-domain-count 2 --platform-update-domain-count 5

// Create multiple VMs in the availability set
for i in range(1, n+1):
  az vm create --resource-group MyResourceGroup --name VM$i --availability-set MyAvailabilitySet --image UbuntuLTS --admin-username azureuser --generate-ssh-keys

This sequence creates one availability set and then creates n virtual machines inside it to ensure redundancy.

Identify Repeating Operations

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

• Primary operation: Creating each virtual machine inside the availability set.
• How many times: This operation repeats n times, once per VM.

How Execution Grows With Input

Each additional virtual machine requires a separate creation call, so the total operations grow directly with the number of VMs.

Input Size (n)	Approx. Api Calls/Operations
10	1 availability set + 10 VM creations = 11
100	1 availability set + 100 VM creations = 101
1000	1 availability set + 1000 VM creations = 1001

Pattern observation: The number of operations increases linearly as more VMs are added.

Final Time Complexity

Time Complexity: O(n)

This means the time to deploy scales directly with the number of virtual machines you add to the availability set.

Common Mistake

[X] Wrong: "Creating an availability set once means adding more VMs won't increase deployment time much."

[OK] Correct: Each VM still needs its own creation process, so deployment time grows with each VM added, even though the availability set is created once.

Interview Connect

Understanding how deployment time grows with the number of resources helps you design scalable and reliable cloud solutions confidently.

Self-Check

"What if we created multiple availability sets and distributed VMs evenly among them? How would the time complexity change?"

Practice

1. What is the main purpose of an Availability Set in Azure?

easy

A. To automatically back up virtual machines every hour

B. To keep virtual machines running during hardware failures by spreading them across fault domains

C. To increase the storage capacity of a single virtual machine

D. To reduce the cost of virtual machines by sharing resources

Solution

1. Step 1: Understand the role of Availability Sets

   Availability sets distribute VMs across different physical hardware to avoid single points of failure.

2. Step 2: Identify the correct purpose

   This distribution helps keep apps running during hardware failures by using fault domains.

3. Final Answer:

   To keep virtual machines running during hardware failures by spreading them across fault domains -> Option B

4. Quick Check:

   Availability sets = fault domain distribution [OK]

Hint: Availability sets protect VMs from hardware failure by spreading them [OK]

Common Mistakes:

• Confusing availability sets with backup solutions
• Thinking availability sets increase storage
• Assuming availability sets reduce VM costs

2. Which of the following is the correct way to create an availability set using Azure CLI?

easy

A. az vm availability-set create --name MySet --resource-group MyGroup --platform-fault-domain-count 2 --platform-update-domain-count 5

B. az availability-set create --name MySet --group MyGroup --faults 2 --updates 5

C. az vm create availability-set --name MySet --resource-group MyGroup --fault-domain 2 --update-domain 5

D. az create availability-set --name MySet --resource MyGroup --fault-domain-count 2 --update-domain-count 5

Solution

1. Step 1: Recall Azure CLI syntax for availability sets

   The correct command uses az vm availability-set create with parameters for fault and update domain counts.

2. Step 2: Match the correct command

   az vm availability-set create --name MySet --resource-group MyGroup --platform-fault-domain-count 2 --platform-update-domain-count 5 matches the correct syntax and parameter names exactly.

3. Final Answer:

   az vm availability-set create --name MySet --resource-group MyGroup --platform-fault-domain-count 2 --platform-update-domain-count 5 -> Option A

4. Quick Check:

   Correct CLI syntax = az vm availability-set create --name MySet --resource-group MyGroup --platform-fault-domain-count 2 --platform-update-domain-count 5 [OK]

Hint: Use 'az vm availability-set create' with fault and update domain counts [OK]

Common Mistakes:

• Using wrong command group like 'az availability-set create'
• Incorrect parameter names like 'faults' or 'updates'
• Mixing VM creation command with availability set creation

3. Given an availability set with 3 fault domains and 5 update domains, what happens if a planned maintenance affects update domain 3?

medium

A. All VMs are shut down until maintenance completes

B. All VMs in the availability set reboot simultaneously

C. VMs in fault domain 3 are rebooted, others are unaffected

D. Only VMs in update domain 3 are rebooted; others keep running

Solution

1. Step 1: Understand update domains in availability sets

   Update domains define groups of VMs rebooted one group at a time during planned maintenance.

2. Step 2: Apply update domain behavior

   Only VMs in the affected update domain reboot; others continue running.

3. Final Answer:

   Only VMs in update domain 3 are rebooted; others keep running -> Option D

4. Quick Check:

   Update domain reboot = only affected domain [OK]

Hint: Update domains reboot one group at a time during maintenance [OK]

Common Mistakes:

• Confusing fault domains with update domains
• Assuming all VMs reboot together
• Thinking fault domain 3 is rebooted on update domain maintenance

4. You created two VMs but forgot to assign them to the same availability set. What is the likely impact?

medium

A. The VMs may be placed on the same hardware, increasing downtime risk

B. The VMs will automatically be grouped into a default availability set

C. The VMs will not start until assigned to an availability set

D. The VMs will be backed up automatically to prevent downtime

Solution

1. Step 1: Understand VM placement without availability sets

   Without an availability set, Azure may place VMs on the same physical hardware.

2. Step 2: Identify impact on redundancy

   This increases risk that a hardware failure affects both VMs, causing downtime.

3. Final Answer:

   The VMs may be placed on the same hardware, increasing downtime risk -> Option A

4. Quick Check:

   No availability set = no guaranteed hardware separation [OK]

Hint: Without availability sets, VMs risk being on same hardware [OK]

Common Mistakes:

• Assuming Azure auto-creates availability sets
• Thinking VMs won't start without availability sets
• Confusing availability sets with backup features

5. You need to deploy 6 VMs with high availability. You create an availability set with 2 fault domains and 3 update domains. What is the best way to distribute the VMs to maximize redundancy?

hard

A. Place 2 VMs in fault domain 1 and 4 VMs in fault domain 2, all in update domain 1

B. Place all 6 VMs in fault domain 1 to simplify management

C. Place 3 VMs in fault domain 1 and 3 VMs in fault domain 2, spread evenly across update domains

D. Place all VMs in the same update domain to reduce reboot frequency

Solution

1. Step 1: Understand fault domain distribution

   Fault domains separate VMs across different hardware racks to avoid single points of failure.

2. Step 2: Understand update domain distribution

   Update domains ensure VMs reboot in groups during maintenance, so spreading VMs across them reduces downtime.

3. Step 3: Apply best practice for VM distribution

   Distributing VMs evenly across fault domains and update domains maximizes redundancy and availability.

4. Final Answer:

   Place 3 VMs in fault domain 1 and 3 VMs in fault domain 2, spread evenly across update domains -> Option C

5. Quick Check:

   Even VM spread across fault and update domains = max redundancy [OK]

Hint: Distribute VMs evenly across fault and update domains for best uptime [OK]

Common Mistakes:

• Putting all VMs in one fault domain
• Ignoring update domain distribution
• Assuming same update domain reduces reboots