VM Scale Sets for auto scaling in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a VM Scale Set resource in Azure ARM template.

Azure

"type": "Microsoft.Compute/virtualMachineScaleSets",
"apiVersion": "2022-08-01",
"name": "myScaleSet",
"location": "eastus",
"sku": {
  "name": "Standard_DS1_v2",
  "tier": "Standard",
  "capacity": [1]
},
"properties": {}

Drag options to blanks, or click blank then click option'

A3

B10

C0

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Setting capacity to 0 will create no VMs.

Setting capacity too high may increase costs unnecessarily.

The capacity property sets the initial number of VM instances in the scale set. Setting it to 1 means the scale set starts with one VM.

2fill in blank

medium

Complete the code to specify the upgrade policy mode for the VM Scale Set.

Azure

"upgradePolicy": {
  "mode": "[1]"
}

Drag options to blanks, or click blank then click option'

AManual

BScheduled

CRolling

DAutomatic

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Rolling' or 'Scheduled' which are not valid modes in this context.

Confusing 'Automatic' with 'Manual' mode.

The upgradePolicy.mode property controls how VMs are updated. Manual means updates are applied only when triggered.

3fill in blank

hard

Fix the error in the autoscale profile metric trigger condition.

Azure

"metricTrigger": {
  "metricName": "Percentage CPU",
  "metricNamespace": "",
  "timeGrain": "PT1M",
  "statistic": "Average",
  "timeWindow": "PT5M",
  "timeAggregation": "Average",
  "operator": "[1]",
  "threshold": 75
}

Drag options to blanks, or click blank then click option'

AGreaterThan

BGreaterThanOrEqual

CLessThan

DEquals

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'GreaterThan' excludes the threshold value.

Using 'Equals' triggers only when exactly 75%, which is rare.

The operator GreaterThanOrEqual triggers scaling when the CPU usage is 75% or higher.

4fill in blank

hard

Fill both blanks to define a scale out rule that increases capacity by 1 when CPU is high.

Azure

"scaleOut": {
  "cooldown": "PT1M",
  "action": {
    "type": "ChangeCount",
    "value": "[1]",
    "direction": "[2]"
  }
}

Drag options to blanks, or click blank then click option'

A1

BIncrease

CDecrease

D2

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Decrease' direction for scale out.

Setting value to 2 instead of 1 for a single increment.

The scale out action increases the VM count by 1 when triggered.

5fill in blank

hard

Fill all three blanks to define a scale in rule that decreases capacity by 1 when CPU is low.

Azure

"scaleIn": {
  "cooldown": "PT5M",
  "action": {
    "type": "ChangeCount",
    "value": "[1]",
    "direction": "[2]",
    "instanceIds": [[3]]
  }
}

Drag options to blanks, or click blank then click option'

A1

BDecrease

C"1"

D"0"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Increase' direction for scale in.

Leaving instanceIds empty or incorrect.

The scale in action decreases the VM count by 1 and targets the instance with ID '0' for removal.