Why monitoring is essential in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable basic monitoring on an Azure VM.

Azure

az vm extension set --resource-group myResourceGroup --vm-name myVM --name [1] --publisher Microsoft.Azure.Monitor --version 1.0

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

AAzureMonitorWindowsAgent

BCustomScriptExtension

CNetworkWatcherAgent

DDiagnosticsExtension

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing an extension unrelated to monitoring like CustomScriptExtension.

The AzureMonitorWindowsAgent extension enables monitoring on Azure VMs.

2fill in blank

medium

Complete the command to create an Azure Monitor alert rule for CPU usage.

Azure

az monitor metrics alert create --name HighCPUAlert --resource-group myResourceGroup --scopes [1] --condition "avg Percentage CPU > 80" --description "Alert on high CPU usage"

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

A/subscriptions/0000/resourceGroups/myResourceGroup/providers/Microsoft.Network/networkInterfaces/myNIC

B/subscriptions/0000/resourceGroups/myResourceGroup/providers/Microsoft.Storage/storageAccounts/myStorage

C/subscriptions/0000/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM

D/subscriptions/0000/resourceGroups/myResourceGroup/providers/Microsoft.Web/sites/myWebApp

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource IDs of storage or web apps instead of the VM.

The scope must be the resource ID of the VM to monitor CPU usage.

3fill in blank

hard

Fix the error in the Azure CLI command to enable diagnostic settings for a storage account.

Azure

az monitor diagnostic-settings create --resource [1] --name diagSettings --workspace myWorkspace --logs '[{"category": "StorageRead", "enabled": true}]'

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

AmyStorageAccount

BmyResourceGroup

CmyWorkspace

DmyStorageAccountResourceId

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the storage account name instead of its full resource ID.

The --resource parameter requires the full resource ID, not just the name.

4fill in blank

hard

Fill both blanks to create a log query that counts errors in Azure Monitor logs.

Azure

AzureDiagnostics | where [1] == 'Error' | summarize count() by [2]

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

ALevel

BResource

CCategory

DTimeGenerated

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Category' instead of 'Level' for filtering errors.

The Level field filters error logs, and Resource groups the count by resource.

5fill in blank

hard

Fill all three blanks to create an alert rule that triggers when average response time exceeds 1000 ms.

Azure

az monitor metrics alert create --name ResponseTimeAlert --resource-group myResourceGroup --scopes [1] --condition "avg [2] > [3]" --description "Alert on high response time"

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

A/subscriptions/0000/resourceGroups/myResourceGroup/providers/Microsoft.Web/sites/myWebApp

BResponseTime

C1000

DPercentage CPU

Attempts:

3 left

💡 Hint

Common Mistakes

Using CPU metric instead of ResponseTime for this alert.

The scope is the web app resource ID, the metric is ResponseTime, and the threshold is 1000 ms.