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.

Practice

1. Why is monitoring essential in Azure DevOps environments?

easy

A. It replaces the need for backups and data recovery.

B. It automatically updates all software without user input.

C. It helps detect and fix problems quickly to keep systems running smoothly.

D. It increases the cost of running cloud services.

Solution

1. Step 1: Understand the purpose of monitoring

   Monitoring tracks system performance and health in real time.

2. Step 2: Identify the benefit of quick problem detection

   Quick detection allows fast fixes, preventing downtime and issues.

3. Final Answer:

   It helps detect and fix problems quickly to keep systems running smoothly. -> Option C

4. Quick Check:

   Monitoring = Fast problem detection [OK]

Hint: Monitoring = catch issues early and fix fast [OK]

Common Mistakes:

• Thinking monitoring updates software automatically
• Confusing monitoring with backup solutions
• Assuming monitoring increases costs directly

2. Which Azure CLI command is used to view metrics for a resource?

easy

A. az storage account delete --name

B. az monitor metrics list --resource

C. az vm create --name

D. az network vnet list

Solution

1. Step 1: Identify the command for monitoring metrics

   The command az monitor metrics list lists metrics for a resource.

2. Step 2: Confirm the command matches the monitoring purpose

   Options A, B, and D perform unrelated tasks like storage deletion, VM creation, or listing VNets.

3. Final Answer:

   az monitor metrics list --resource <resource-id> -> Option B

4. Quick Check:

   Metrics command = az monitor metrics list [OK]

Hint: Use 'az monitor metrics list' to check resource metrics [OK]

Common Mistakes:

• Confusing VM or storage commands with monitoring commands
• Omitting the --resource parameter
• Using commands that list unrelated resources

3. What is the output of this Azure CLI command?

az monitor metrics list --resource /subscriptions/123/resourceGroups/myRG/providers/Microsoft.Compute/virtualMachines/myVM --metric CPUPercentage --interval PT1M --output table

medium

A. A JSON object with storage account details.

B. An error saying the resource ID is invalid.

C. A list of all virtual machines in the resource group.

D. A table showing CPU usage percentage of the VM every minute.

Solution

1. Step 1: Analyze the command parameters

   The command requests CPUPercentage metric for a VM resource with 1-minute intervals and table output.

2. Step 2: Determine expected output type

   The output will be a table showing CPU usage data points for the VM over time.

3. Final Answer:

   A table showing CPU usage percentage of the VM every minute. -> Option D

4. Quick Check:

   Metrics output = table of CPU usage [OK]

Hint: Look for metric and output parameters to guess output format [OK]

Common Mistakes:

• Assuming command lists VMs instead of metrics
• Confusing resource ID with resource group
• Expecting JSON when output is table

4. You run this command but get an error:

az monitor metrics list --resource myVM --metric CPUPercentage

What is the likely cause?

medium

A. The resource ID is incomplete; it needs the full Azure resource ID path.

B. The metric name CPUPercentage is invalid.

C. The command requires a storage account name instead of a VM name.

D. The Azure CLI is not installed.

Solution

1. Step 1: Check the resource parameter format

   The command uses 'myVM' which is not a full resource ID; Azure expects full resource ID path.

2. Step 2: Understand error cause

   Without full resource ID, Azure CLI cannot find the resource to get metrics.

3. Final Answer:

   The resource ID is incomplete; it needs the full Azure resource ID path. -> Option A

4. Quick Check:

   Full resource ID required = error [OK]

Hint: Always use full resource ID for monitoring commands [OK]

Common Mistakes:

• Using just resource name instead of full ID
• Assuming metric name is wrong
• Thinking CLI is not installed without checking

5. You want to set up monitoring alerts in Azure to notify you when CPU usage exceeds 80% for 5 minutes. Which approach best uses monitoring to prevent downtime?

hard

A. Configure Azure Monitor alerts with action groups to send notifications on CPU threshold breaches.

B. Manually check CPU metrics daily using Azure CLI commands.

C. Increase VM size without monitoring CPU usage.

D. Disable monitoring to reduce costs and rely on user reports.

Solution

1. Step 1: Identify proactive monitoring method

   Azure Monitor alerts can automatically notify when CPU exceeds thresholds, enabling fast response.

2. Step 2: Compare options for preventing downtime

   Manual checks or ignoring monitoring delay response; increasing VM size blindly wastes resources.

3. Final Answer:

   Configure Azure Monitor alerts with action groups to send notifications on CPU threshold breaches. -> Option A

4. Quick Check:

   Alerts + notifications = proactive downtime prevention [OK]

Hint: Use alerts with notifications for fast issue response [OK]

Common Mistakes:

• Relying on manual checks only
• Ignoring monitoring to save costs
• Scaling without monitoring data