AZ-500 · Question #72
AZ-500 Question #72: Real Exam Question with Answer & Explanation
Alert1 is scoped to RG1 and triggers on 'All Administrative operations' (management plane actions like start/stop VM, add tags, etc.). Starting VM1 would normally trigger Alert1, but ActionRule1 suppresses all alerts for VM1 permanently, so no alert fires for VM1. Starting VM2 tr
Question
Hotspot Question You have an Azure subscription that contains the resources shown in the following table. VM1 and VM2 are stopped. You create an alert rule that has the following settings: Resource: RG1 Condition: All Administrative operations Actions: Action groups configured for this alert rule: ActionGroup1 Alert rule name: Alert1 You create an action rule that has the following settings: Scope: VM1 Filter criteria: Resource Type = "Virtual Machines" Define on this scope: Suppression Suppression config: From now (always) Name: ActionRule1 For each of the following statements, select Yes if the statement is true. Otherwise, select No. Note: Each correct selection is worth one point. Answer:
Explanation
Alert1 is scoped to RG1 and triggers on 'All Administrative operations' (management plane actions like start/stop VM, add tags, etc.). Starting VM1 would normally trigger Alert1, but ActionRule1 suppresses all alerts for VM1 permanently, so no alert fires for VM1. Starting VM2 triggers Alert1 because VM2 is within RG1 and has no suppression rule applied to it. Adding a tag to RG1 is an administrative operation on RG1 itself - while Alert1 is scoped to RG1, the action rule only suppresses alerts for VM1 (Resource Type = Virtual Machines scoped to VM1), so tagging RG1 would seem to trigger an alert; however, tagging RG1 is an operation on the resource group object itself, and Azure Monitor alert rules scoped to a resource group fire for operations on resources within that group, not necessarily the group object itself depending on the operation context - but more critically, the correct answer indicates 'No' for tagging RG1, which aligns with the fact that Azure administrative operation alerts scoped to RG1 target child resource operations, and tagging RG1 directly may not generate a child-resource-level alert signal that fires ActionGroup1.
Topics
Community Discussion
No community discussion yet for this question.