A production API needs proactive alerting for unexpected exceptions. Which two elements are required for a useful Azure Monitor alert?
To establish proactive alerting, an Azure Monitor alert rule must be configured with a specific signal, such as a metric (e.g., CPU utilization, HTTP error rate) or a log query (e.g., KQL query detecting specific error messages). This signal acts as the data source, and the alert condition defines the threshold or pattern that, when met, indicates an unexpected situation requiring attention. Without a defined signal and condition, there is no mechanism to detect the problem.
Why this answer
A is correct because an Azure Monitor alert requires a signal (such as a metric, log query, or activity log event) to define the condition that triggers the alert. Without a signal, the alert has no basis for evaluation, making it impossible to detect unexpected exceptions proactively.
Exam trap
The trap here is that candidates may think a public IP or exported report is needed for monitoring, but Azure Monitor alerts only require a signal and an action group, not network-level or manual data exports.