An Azure alert rule is configured to monitor CPU usage above 80%. What is the immediate result when the CPU usage exceeds 80%?
Think about how Azure alert rules and action groups work together to notify users.
When an Azure alert rule triggers, it immediately sends notifications to all linked action groups. This allows automated or manual responses to the alert.
Choose the JSON snippet that correctly configures an Azure action group with an email receiver named 'OpsTeam'.
Look for the correct property names used in Azure action group JSON schema.
Azure action groups use 'name' and 'emailReceivers' with 'name' and 'emailAddress' properties for email receivers.
You have VMs deployed in two Azure regions. You want alerts for high CPU usage to notify the on-call engineer with minimal delay and avoid duplicate alerts. Which design is best?
Think about centralizing monitoring to reduce duplicate alerts and delays.
Centralizing metrics in one Log Analytics workspace and creating a single alert rule reduces duplicate alerts and speeds notification.
You configure one action group shared by multiple teams for alerts. What is a potential security risk of this setup?
Consider how alert relevance affects team response and security.
Sharing action groups across teams can cause irrelevant alerts to be sent to teams, leading to alert fatigue and missed critical alerts.
You want to automatically restart a VM when a CPU alert triggers. Which action group configuration enables this automation?
Think about how to trigger automated actions from alerts.
Using a webhook receiver to call an Azure Function allows automated remediation like restarting a VM when an alert triggers.