Reliability pillar principles in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Availability Set for high availability.

Azure

az vm availability-set create --name myAvailabilitySet --resource-group myResourceGroup --[1]

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

Alocation eastus

Bos-type Linux

Cplatform-fault-domain-count 2

Dvm-sku Standard_DS1_v2

Attempts:

3 left

💡 Hint

Common Mistakes

Using location instead of fault domain count

Specifying VM SKU in availability set creation

The platform-fault-domain-count option sets the number of fault domains to improve reliability.

2fill in blank

medium

Complete the code to configure Azure Load Balancer health probe.

Azure

az network lb probe create --resource-group myResourceGroup --lb-name myLoadBalancer --name myHealthProbe --protocol tcp --port 80 --[1] 5

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

Apriority

Bthreshold

Ctimeout

Dinterval

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing interval with timeout

Using threshold instead of interval

The interval option sets how often the health probe runs, improving reliability by detecting failures quickly.

3fill in blank

hard

Fix the error in the Azure VM scale set creation command to ensure automatic instance repair is enabled.

Azure

az vmss create --resource-group myResourceGroup --name myScaleSet --image UbuntuLTS --upgrade-policy-mode automatic --[1] true

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

Aenable-instance-repair

Bautomatic-repairs-enabled

Cenable-auto-repair

Dautomatic-instance-repair

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names that don't exist

Confusing instance repair with upgrade policy

The correct parameter to enable automatic instance repair is automatic-repairs-enabled.

4fill in blank

hard

Fill both blanks to create an Azure Storage Account with geo-redundant replication and enable soft delete.

Azure

az storage account create --name mystorageaccount --resource-group myResourceGroup --sku [1] --kind StorageV2
az storage account update --name mystorageaccount --resource-group myResourceGroup --[2] true

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

AStandard_GRS

BStandard_LRS

Cenable-soft-delete

Denable-delete-retention

Attempts:

3 left

💡 Hint

Common Mistakes

Using locally redundant storage instead of geo-redundant

Confusing soft delete with retention policies

Standard_GRS enables geo-redundant storage for reliability. enable-delete-retention turns on soft delete to protect data from accidental deletion.

5fill in blank

hard

Fill all three blanks to define an Azure Monitor alert rule that triggers when CPU usage exceeds 80% for 5 minutes.

Azure

az monitor metrics alert create --name HighCPUAlert --resource-group myResourceGroup --scopes [1] --condition "avg '[2]' > [3]" --description "Alert when CPU > 80%"

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

A/subscriptions/12345/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM

BPercentage CPU

C80

DCPU Usage

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect resource ID format

Using wrong metric name or threshold value

The scopes parameter needs the resource ID of the VM. The metric name is Percentage CPU, and the threshold is 80 percent.