VM Scale Sets for auto scaling in Azure - Step-by-Step Execution

Process Flow - VM Scale Sets for auto scaling

Start VM Scale Set

↓

Monitor Metrics

↓

Check Scale Rules

↓

Scale Out

↓

Add VM Instances

↓

Update Load Balancer

↓

Continue Monitoring

The VM Scale Set starts and monitors performance metrics. If rules say to scale out, it adds VM instances and updates the load balancer, then continues monitoring.

Execution Sample

Azure

1. Create VM Scale Set with 2 VMs
2. Monitor CPU usage
3. If CPU > 70%, add 1 VM
4. If CPU < 30%, remove 1 VM
5. Repeat monitoring

This setup automatically adds or removes VM instances based on CPU usage thresholds.

Process Table

Step	CPU Usage (%)	Current VM Count	Condition	Action Taken	Resulting VM Count
1	50	2	50 > 70? No	No scaling	2
2	75	2	75 > 70? Yes	Scale out: add 1 VM	3
3	65	3	65 > 70? No	No scaling	3
4	25	3	25 < 30? Yes	Scale in: remove 1 VM	2
5	40	2	40 < 30? No	No scaling	2
6	80	2	80 > 70? Yes	Scale out: add 1 VM	3
7	85	3	85 > 70? Yes	Scale out: add 1 VM	4
8	60	4	60 > 70? No	No scaling	4
9	20	4	20 < 30? Yes	Scale in: remove 1 VM	3
10	30	3	30 < 30? No	No scaling	3

💡 Monitoring stops after step 10; scaling decisions made based on CPU thresholds.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	After 7	After 8	After 9	After 10
CPU Usage (%)	N/A	50	75	65	25	40	80	85	60	20	30
VM Count	2	2	3	3	2	2	3	4	4	3	3

Key Moments - 3 Insights

Why does the VM count not change when CPU usage is 50% at step 1?

Because 50% is not greater than the scale-out threshold of 70%, so no scaling action is taken as shown in execution_table row 1.

Why does the VM count decrease at step 4 when CPU usage is 25%?

Because 25% is below the scale-in threshold of 30%, triggering removal of one VM instance as shown in execution_table row 4.

Why are multiple scale-outs possible in consecutive steps like 6 and 7?

Because CPU usage remains above 70%, each check triggers adding one VM, increasing VM count step by step as shown in execution_table rows 6 and 7.

Visual Quiz - 3 Questions

Look at the execution table, what is the VM count after step 3?

A 2

B 3

C 4

D 1

💡 Hint

Check the 'Resulting VM Count' column at step 3 in the execution_table.

At which step does the CPU usage first trigger a scale-in action?

A Step 2

B Step 6

C Step 4

D Step 9

💡 Hint

Look for the first 'Scale in' action in the 'Action Taken' column in execution_table.

If the scale-out threshold changed from 70% to 80%, what would happen at step 2?

A No scaling would happen

B Scale in would happen

C Scale out would still happen

D VM count would decrease

💡 Hint

Compare CPU usage at step 2 with the new threshold and check the 'Condition' column.

Concept Snapshot

VM Scale Sets automatically add or remove VM instances based on performance metrics.
Set thresholds (e.g., CPU > 70% to scale out, CPU < 30% to scale in).
Monitor metrics continuously.
Scale out adds VMs; scale in removes VMs.
Load balancer updates to distribute traffic.
This ensures apps handle demand efficiently.

Full Transcript

VM Scale Sets start with a set number of VMs. They monitor CPU usage regularly. If CPU usage goes above 70%, the system adds one VM to handle more load. If CPU usage falls below 30%, it removes one VM to save resources. This process repeats, adjusting the number of VMs to match demand. The load balancer updates to include new VMs or exclude removed ones. This automatic scaling helps keep applications responsive and cost-effective.

Practice

1. What is the main purpose of Azure VM Scale Sets in cloud infrastructure?

easy

A. To store data permanently in the cloud

B. To create a single virtual machine with fixed resources

C. To automatically adjust the number of virtual machines based on demand

D. To manage user access and permissions

Solution

1. Step 1: Understand VM Scale Sets function

   VM Scale Sets allow running multiple VMs that can increase or decrease automatically.

2. Step 2: Identify the main benefit

   This automatic adjustment helps handle changes in workload efficiently.

3. Final Answer:

   To automatically adjust the number of virtual machines based on demand -> Option C

4. Quick Check:

   Auto scaling = Adjust VM count [OK]

Hint: Think 'auto' means adjusting VM count automatically [OK]

Common Mistakes:

• Confusing VM Scale Sets with storage services
• Thinking it manages user permissions
• Assuming it creates only one VM

2. Which of the following is the correct way to define an autoscale rule in Azure VM Scale Sets to add instances when CPU usage is above 70%?

easy

A. Set a rule to add instances when CPU > 70% using metric 'Percentage CPU' and operator 'GreaterThan' with threshold 70

B. Set a rule to decrease instances when CPU > 70%

C. Set a rule to add instances when CPU < 70% using metric 'Percentage CPU' and operator 'LessThan' with threshold 70

D. Set a rule to add instances when memory usage > 70% ignoring CPU metrics

Solution

1. Step 1: Identify correct metric and operator

   The autoscale rule should trigger when CPU usage is greater than 70%, so metric 'Percentage CPU' and operator 'GreaterThan' are correct.

2. Step 2: Confirm action to add instances

   The rule must add instances when the condition is met, not decrease or use wrong metrics.

3. Final Answer:

   Set a rule to add instances when CPU > 70% using metric 'Percentage CPU' and operator 'GreaterThan' with threshold 70 -> Option A

4. Quick Check:

   CPU > 70% triggers add instances [OK]

Hint: Match metric and operator to condition exactly [OK]

Common Mistakes:

• Using 'LessThan' instead of 'GreaterThan'
• Confusing CPU with memory metrics
• Setting decrease action instead of add

3. Given this autoscale rule for a VM Scale Set:

{
  "metricTrigger": {
    "metricName": "Percentage CPU",
    "operator": "GreaterThan",
    "threshold": 80
  },
  "scaleAction": {
    "direction": "Increase",
    "value": "2"
  }
}

What happens when CPU usage goes above 80%?

medium

A. The VM Scale Set decreases by 2 instances

B. The VM Scale Set increases by 2 instances

C. The VM Scale Set stays the same

D. The VM Scale Set increases by 1 instance

Solution

1. Step 1: Analyze metric trigger

   The rule triggers when CPU usage is greater than 80%.

2. Step 2: Analyze scale action

   The action is to increase the VM count by 2 instances.

3. Final Answer:

   The VM Scale Set increases by 2 instances -> Option B

4. Quick Check:

   CPU > 80% triggers increase by 2 [OK]

Hint: Look for 'Increase' and 'value' in scaleAction [OK]

Common Mistakes:

• Confusing increase with decrease
• Ignoring the value number
• Assuming default increase of 1

4. You configured an autoscale rule to add 1 instance when CPU usage is above 60%, but the VM Scale Set never scales out. What is the most likely error?

medium

A. The metric name is misspelled or incorrect

B. The scale action direction is set to 'Decrease'

C. The threshold is set to 10 instead of 60

D. The VM Scale Set has no instances initially

Solution

1. Step 1: Check metric name correctness

   If the metric name is wrong, the rule never triggers because it can't read CPU usage.

2. Step 2: Verify other options

   Direction 'Decrease' would scale down, threshold 10 is too low but would still trigger, and initial instances are usually at least one.

3. Final Answer:

   The metric name is misspelled or incorrect -> Option A

4. Quick Check:

   Wrong metric name blocks scaling [OK]

Hint: Always verify metric names exactly match Azure docs [OK]

Common Mistakes:

• Setting wrong scale direction
• Ignoring metric name spelling
• Assuming zero initial instances

5. You want to configure a VM Scale Set to maintain between 3 and 10 instances. It should add 2 instances when average CPU is above 75% and remove 1 instance when CPU is below 30%. Which setup correctly achieves this?

hard

A. Set minimum 5, maximum 15 instances; add 2 when CPU < 30%; remove 1 when CPU > 75%

B. Set minimum 1, maximum 5 instances; add 1 when CPU > 75%; remove 2 when CPU < 30%

C. Set minimum 3, maximum 10 instances; add 1 when CPU > 30%; remove 2 when CPU < 75%

D. Set minimum 3, maximum 10 instances; add 2 when CPU > 75%; remove 1 when CPU < 30%

Solution

1. Step 1: Confirm instance limits

   The requirement is minimum 3 and maximum 10 instances, so only Set minimum 3, maximum 10 instances; add 2 when CPU > 75%; remove 1 when CPU < 30% matches this.

2. Step 2: Check autoscale rules

   Set minimum 3, maximum 10 instances; add 2 when CPU > 75%; remove 1 when CPU < 30% adds 2 instances when CPU > 75% and removes 1 when CPU < 30%, exactly as required.

3. Final Answer:

   Set minimum 3, maximum 10 instances; add 2 when CPU > 75%; remove 1 when CPU < 30% -> Option D

4. Quick Check:

   Limits and rules match requirements [OK]

Hint: Match min/max and scale rules exactly to requirements [OK]

Common Mistakes:

• Mixing up CPU thresholds for add/remove
• Setting wrong min or max instance counts
• Reversing scale directions