VM Scale Sets for auto scaling in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an Azure VM Scale Set?

An Azure VM Scale Set is a group of identical virtual machines that can automatically increase or decrease in number to handle changes in demand.

beginner

How does auto scaling work in VM Scale Sets?

Auto scaling adjusts the number of VMs in the scale set based on rules like CPU usage or schedule, so your app can handle more users or save costs when demand is low.

intermediate

What is a scale-in policy in VM Scale Sets?

A scale-in policy controls how VMs are removed when scaling down, for example, removing the oldest VM first or the one with the least load.

beginner

Why use VM Scale Sets instead of single VMs?

VM Scale Sets provide automatic scaling and high availability, so your app stays responsive and reliable without manual intervention.

intermediate

What metrics can trigger auto scaling in VM Scale Sets?

Common metrics include CPU usage, memory usage, disk I/O, and custom metrics you define to decide when to add or remove VMs.

What does a VM Scale Set automatically adjust?

A The network bandwidth

B The size of each virtual machine

C The operating system of VMs

D The number of virtual machines

VM Scale Sets automatically adjust the number of virtual machines to meet demand.

Which metric is commonly used to trigger scaling in VM Scale Sets?

A CPU usage

B Number of users logged in

C Disk size

D VM color

CPU usage is a common metric to trigger scaling actions.

What happens when demand decreases in a VM Scale Set with auto scaling?

A VMs change their operating system

B The number of VMs increases

C The number of VMs decreases

D Nothing changes

When demand decreases, auto scaling reduces the number of VMs to save costs.

Which of these is NOT a benefit of VM Scale Sets?

A Manual VM configuration for each instance

B High availability

C Load balancing

D Automatic scaling

VM Scale Sets use identical VMs and do not require manual configuration for each instance.

What is a scale-in policy used for?

A To add more VMs when demand increases

B To decide which VMs to remove when scaling down

C To upgrade VM operating systems

D To monitor network traffic

Scale-in policies control which VMs are removed during scale down.

Explain how VM Scale Sets help manage application demand automatically.

Think about how a store adds or removes cashiers depending on customer lines.

Describe what a scale-in policy is and why it matters in VM Scale Sets.

Imagine deciding which workers leave first when a store gets less busy.

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