Azure Monitor overview - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Monitor Log Analytics workspace.

Azure

az monitor log-analytics workspace create --resource-group myResourceGroup --workspace-name [1]

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

AmyStorageAccount

BmyVM

CmyWorkspace

DmyResourceGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource group name instead of the workspace name.

Using unrelated resource names like VM or storage account.

The workspace name is required to create a Log Analytics workspace. Here, myWorkspace is the correct name.

2fill in blank

medium

Complete the code to enable Azure Monitor metrics for a virtual machine.

Azure

az monitor metrics alert create --name HighCPUAlert --resource-group myResourceGroup --scopes [1] --condition "avg Percentage CPU > 80" --window-size 5m --evaluation-frequency 1m

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

A/subscriptions/xxxx/resourceGroups/myResourceGroup/providers/Microsoft.Storage/storageAccounts/myStorage

B/subscriptions/xxxx/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM

CmyVM

DmyResourceGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the VM name instead of the full resource ID.

Using the resource group name as the scope.

The --scopes parameter requires the full resource ID of the virtual machine to monitor its metrics.

3fill in blank

hard

Fix the error in the command to create an alert rule for CPU usage.

Azure

az monitor metrics alert create --name CPUAlert --resource-group myResourceGroup --scopes [1] --condition "avg Percentage CPU > 90" --window-size 5m --evaluation-frequency 1m

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

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

BmyVM

CmyResourceGroup

D/subscriptions/xxxx/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the VM name as scope.

Using a network interface resource ID instead of the VM.

The scope must be the full resource ID of the virtual machine, not just the VM name or resource group.

4fill in blank

hard

Fill both blanks to create a query that returns CPU usage over the last hour.

Azure

Perf | where TimeGenerated > ago([1]) | where CounterName == [2]

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

A1h

B"\Processor(_Total)\% Processor Time"

C1d

D"\Memory\Available MBytes"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 1 day instead of 1 hour for the time filter.

Using memory counters instead of CPU counters.

The query filters performance data from the last 1 hour and selects the CPU usage counter.

5fill in blank

hard

Fill all three blanks to create an alert rule that triggers when disk space is low.

Azure

az monitor metrics alert create --name DiskSpaceAlert --resource-group myResourceGroup --scopes [1] --condition "avg [2] [3] 10" --window-size 10m --evaluation-frequency 5m

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

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

B"LogicalDisk % Free Space"

C<

D"LogicalDisk Free Space"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect metric names.

Using > instead of < for the condition.

Using resource group name instead of full resource ID.

The alert monitors the average free disk space percentage and triggers if it falls below 10%.

Practice

1. What is the main purpose of Azure Monitor?

easy

A. To watch cloud resources and keep them healthy

B. To create virtual machines

C. To store large amounts of data

D. To manage user permissions

Solution

1. Step 1: Understand Azure Monitor's role

   Azure Monitor watches cloud resources to ensure they work well and stay healthy.

2. Step 2: Compare options with this role

   Creating virtual machines, storing data, and managing permissions are not the main tasks of Azure Monitor.

3. Final Answer:

   To watch cloud resources and keep them healthy -> Option A

4. Quick Check:

   Azure Monitor = watches resources [OK]

Hint: Azure Monitor = watches and keeps resources healthy [OK]

Common Mistakes:

• Confusing Azure Monitor with storage services
• Thinking it creates virtual machines
• Mixing it up with user management

2. Which of the following is the correct way to enable Azure Monitor for a resource in the Azure portal?

easy

A. Disable all alerts to start Azure Monitor

B. Create a new virtual machine and Azure Monitor is enabled by default

C. Go to the resource, select 'Monitoring', then 'Insights', and enable monitoring

D. Run a PowerShell script to delete monitoring settings

Solution

1. Step 1: Check how to enable monitoring in Azure portal

   Azure Monitor is enabled by going to the resource, selecting 'Monitoring', then 'Insights', and turning it on.

2. Step 2: Eliminate incorrect options

   Creating a VM does not automatically enable Azure Monitor; deleting monitoring or disabling alerts does not enable it.

3. Final Answer:

   Go to the resource, select 'Monitoring', then 'Insights', and enable monitoring -> Option C

4. Quick Check:

   Enable monitoring via Insights in portal [OK]

Hint: Enable monitoring under resource's Insights tab [OK]

Common Mistakes:

• Assuming Azure Monitor is on by default for all resources
• Confusing enabling with disabling alerts
• Thinking deleting settings enables monitoring

3. Consider this Azure Monitor alert rule setup:
Alert when CPU usage > 80% for 5 minutes
What happens if CPU usage spikes to 85% for 3 minutes and then drops to 75%?

medium

A. An alert is triggered immediately when CPU hits 85%

B. No alert is triggered because the high CPU lasted less than 5 minutes

C. An alert triggers after CPU usage drops below 80%

D. The alert triggers only if CPU stays above 90%

Solution

1. Step 1: Understand alert condition timing

   The alert triggers only if CPU usage stays above 80% continuously for 5 minutes.

2. Step 2: Analyze the CPU usage pattern

   The CPU was above 80% for only 3 minutes, then dropped below, so the alert condition is not met.

3. Final Answer:

   No alert is triggered because the high CPU lasted less than 5 minutes -> Option B

4. Quick Check:

   Alert needs 5 minutes above threshold [OK]

Hint: Alert triggers only after condition lasts full time [OK]

Common Mistakes:

• Thinking alert triggers immediately on spike
• Ignoring the 5-minute duration condition
• Confusing threshold values

4. You set up an Azure Monitor alert but it never triggers even when the condition is met. What is a likely cause?

medium

A. Alert rule is disabled or not properly configured

B. Azure Monitor does not support alerts

C. The resource is offline and cannot be monitored

D. Alerts only work during business hours

Solution

1. Step 1: Check alert rule status

   If the alert rule is disabled or misconfigured, it will not trigger even if conditions are met.

2. Step 2: Review other options for correctness

   Azure Monitor supports alerts anytime; resources offline may not send data but usually cause other errors; alerts are not time-limited.

3. Final Answer:

   Alert rule is disabled or not properly configured -> Option A

4. Quick Check:

   Disabled alert rules never trigger [OK]

Hint: Check if alert rule is enabled and correct [OK]

Common Mistakes:

• Assuming Azure Monitor can't alert
• Thinking alerts depend on time of day
• Ignoring alert rule configuration

5. You want to reduce costs but keep monitoring important metrics with Azure Monitor. Which approach is best?

hard

A. Collect all possible data and create alerts for every metric

B. Disable Azure Monitor completely to save money

C. Use Azure Monitor only during peak hours

D. Configure sampling to collect fewer data points and set alerts only on critical metrics

Solution

1. Step 1: Understand cost-saving options in Azure Monitor

   Sampling reduces data volume by collecting fewer points, lowering cost. Alerting only on critical metrics avoids unnecessary alerts.

2. Step 2: Evaluate other options

   Disabling monitoring risks missing issues; collecting all data increases cost; limiting monitoring by time is not supported and risky.

3. Final Answer:

   Configure sampling to collect fewer data points and set alerts only on critical metrics -> Option D

4. Quick Check:

   Sampling + critical alerts = cost saving [OK]

Hint: Use sampling and alert only on key metrics [OK]

Common Mistakes:

• Turning off monitoring completely
• Collecting too much data without filtering
• Assuming monitoring can be time-limited