A water utility wants an email when an Azure service it depends on degrades or has an incident. Which Service Health capability theme supports that need?
Select an answer to reveal the explanation.
Short Explanation
Service Health can tap you on the shoulder—health alerts—when a service you rely on goes sideways. That beats refreshing the status page all afternoon.
Full Explanation
Configuring health alerts for Azure service health events is the Service Health capability theme that emails a water utility when a depended-on Azure service degrades or has an incident. Alerts turn the health portal from a page staff must refresh into an event-driven notification channel for municipal on-call workflows. That matches AZ-900's describe-level picture of Service Health plus alerting.
Exporting ARM templates for every resource group nightly fails because template export is a deployment/documentation practice, not Service Health incident notification. Generating Advisor scores that replace all other monitoring fails because Advisor scores measure recommendation posture and do not substitute for platform health alerts. Automatically rewriting application source code during outages fails because neither Service Health nor AZ-900 fundamentals describe automatic source rewriting as a health capability.
Exam caveat: health alerts notify; they do not remediate. The utility still needs runbooks for failover, status pages for citizens, and application monitoring for non-platform faults.
Operational check: create a Service Health alert rule scoped to the utility's critical services and action group email, then use a test or historical event review to confirm the notification path reaches the operations distribution list.