Hotspot Question You have an Azure subscription that contains a user named Admin1 and a resource group named RG1. In Azure Monitor, you create the alert rules shown in the following table. Admin1…

Question

Exhibits

Answer Area

• Rule1No
• Rule2Yes
• Rule3No
• Rule4Yes

Explanation

This question tests understanding of Azure Monitor alert rules based on signal types (Activity Log signals) and how administrative actions like creating resources or adding locks trigger specific alert conditions.

Approach. Alert Rule1 is typically configured to monitor 'Create or Update Virtual Network' activity log signals scoped to RG1, so adding VNET1 triggers it. Alert Rule2 is configured to monitor 'Create or Update Resource Lock' (or all administrative operations) on RG1, so adding Lock1 (a delete lock) triggers it. The key concept is that Azure Monitor Activity Log alerts fire based on the specific operation names recorded in the Azure Activity Log - 'Microsoft.Network/virtualNetworks/write' for VNET1 creation and 'Microsoft.Authorization/locks/write' for Lock1 creation. Both actions are administrative write operations performed on RG1, and if the alert rules are scoped to RG1 with the matching signal/condition, both rules will trigger. Rule3, if scoped to a different resource type or condition not matching these actions, would NOT trigger.

Concept tested. Azure Monitor Activity Log Alert Rules - understanding which administrative actions (resource creation, lock creation) match specific alert rule signal conditions and trigger alerts based on Azure Resource Manager operation types.

Reference. https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/activity-log-alerts

No community discussion yet for this question.