Auto scaling App Service in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the minimum number of instances for auto scaling.

Azure

az monitor autoscale create --resource-group MyResourceGroup --resource MyAppServicePlan --resource-type Microsoft.Web/serverfarms --min-count [1] --max-count 5 --count 1

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

A1

B2

C0

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Setting min-count to 0 stops the app service.

Setting min-count higher than max-count causes errors.

The --min-count parameter sets the minimum number of instances. Setting it to 1 ensures at least one instance is always running.

2fill in blank

medium

Complete the code to add a scale rule based on CPU percentage.

Azure

az monitor autoscale rule create --resource-group MyResourceGroup --autoscale-name MyScaleRule --metric-name [1] --operator GreaterThan --threshold 70 --scale out 1 --cooldown 5

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

ACpuPercentage

BDiskQueueLength

CMemoryPercentage

DNetworkIn

Attempts:

3 left

💡 Hint

Common Mistakes

Using MemoryPercentage instead of CpuPercentage for CPU-based scaling.

Using NetworkIn which measures network traffic, not CPU.

The CpuPercentage metric is commonly used to trigger scaling when CPU usage is high.

3fill in blank

hard

Fix the error in the scale rule command to correctly specify the scale direction.

Azure

az monitor autoscale rule create --resource-group MyResourceGroup --autoscale-name MyScaleRule --metric-name CpuPercentage --operator GreaterThan --threshold 80 --scale [1] 2 --cooldown 10

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

Ascaleout

Bup

Cincrease

Dout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'up' instead of 'out' causes command failure.

Using 'scaleout' as one word is invalid.

The correct scale direction keyword is out to increase instances.

4fill in blank

hard

Fill both blanks to create a scale rule that decreases instances when CPU is low.

Azure

az monitor autoscale rule create --resource-group MyResourceGroup --autoscale-name MyScaleRule --metric-name [1] --operator LessThan --threshold 30 --scale [2] 1 --cooldown 5

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

ACpuPercentage

Bin

Cout

DMemoryPercentage

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'out' instead of 'in' for scaling down.

Using MemoryPercentage metric when CPU is intended.

Use CpuPercentage for the metric and in to scale in (reduce instances) when CPU is low.

5fill in blank

hard

Fill all three blanks to create an autoscale profile with min, max, and default instance counts.

Azure

az monitor autoscale create --resource-group MyResourceGroup --resource MyAppServicePlan --resource-type Microsoft.Web/serverfarms --min-count [1] --max-count [2] --count [3]

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

A1

B3

C2

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Setting default count higher than max count.

Setting min count higher than default count.

Set minimum instances to 1, maximum to 5, and default count to 2 for balanced scaling.