Detection and notification routing require separate configuration. In this case, a metric alert fires briefly from a single spike and causes noise. “The alert rule's associated action groups and receiver configuration” would not satisfy that requirement; the supported action is “Adjust aggregation granularity and alert threshold based on desired signal”. Short evaluation windows can treat transient spikes as incidents.

Processing rules avoid repeated editing of individual alert definitions. In this case, a metric alert fires briefly from a single spike and causes noise. “Use a scoped alert processing rule for the maintenance window” would not satisfy that requirement; the supported action is “Adjust aggregation granularity and alert threshold based on desired signal”. Short evaluation windows can treat transient spikes as incidents.

Alert processing rules can control downstream notifications during maintenance. In this case, a metric alert fires briefly from a single spike and causes noise. “Alert processing rule with a time-bound suppression schedule” would not satisfy that requirement; the supported action is “Adjust aggregation granularity and alert threshold based on desired signal”. Short evaluation windows can treat transient spikes as incidents.

Azure Monitor metric alert sensitivity depends on aggregation and evaluation timing. In this case, a team wants to silence existing notifications for a planned maintenance window without deleting each alert rule. “Configure metric threshold, evaluation frequency and aggregation window” would not satisfy that requirement; the supported action is “Alert processing rule with a time-bound suppression schedule”. Alert processing rules can control downstream notifications during maintenance.

Short evaluation windows can treat transient spikes as incidents. In this case, a team wants to silence existing notifications for a planned maintenance window without deleting each alert rule. “Adjust aggregation granularity and alert threshold based on desired signal” would not satisfy that requirement; the supported action is “Alert processing rule with a time-bound suppression schedule”. Alert processing rules can control downstream notifications during maintenance.

Detection and notification routing require separate configuration. In this case, a team wants to silence existing notifications for a planned maintenance window without deleting each alert rule. “The alert rule's associated action groups and receiver configuration” would not satisfy that requirement; the supported action is “Alert processing rule with a time-bound suppression schedule”. Alert processing rules can control downstream notifications during maintenance.

Azure Monitor metric alert sensitivity depends on aggregation and evaluation timing. In this case, an admin disables 30 alert definitions one by one before a patch. “Configure metric threshold, evaluation frequency and aggregation window” would not satisfy that requirement; the supported action is “Use a scoped alert processing rule for the maintenance window”. Processing rules avoid repeated editing of individual alert definitions.

Short evaluation windows can treat transient spikes as incidents. In this case, an admin disables 30 alert definitions one by one before a patch. “Adjust aggregation granularity and alert threshold based on desired signal” would not satisfy that requirement; the supported action is “Use a scoped alert processing rule for the maintenance window”. Processing rules avoid repeated editing of individual alert definitions.

Infrastructure aggregates do not attribute individual application failures. In this case, an admin disables 30 alert definitions one by one before a patch. “Correlated application request and exception diagnostics” would not satisfy that requirement; the supported action is “Use a scoped alert processing rule for the maintenance window”. Processing rules avoid repeated editing of individual alert definitions.

VM insights provides richer VM performance visibility using configured data sources. In this case, an operator sees a sustained VM disk latency metric but cannot identify a particular application request. “VM insights in Azure Monitor with the required agent/configuration” would not satisfy that requirement; the supported action is “Application Insights request traces and dependency telemetry where instrumented”. Application traces connect user requests to underlying dependencies beyond platform metrics.

VM insights depends on proper telemetry enrollment rather than just dashboard creation. In this case, an operator sees a sustained VM disk latency metric but cannot identify a particular application request. “Enable the supported Azure Monitor agent and data collection configuration” would not satisfy that requirement; the supported action is “Application Insights request traces and dependency telemetry where instrumented”. Application traces connect user requests to underlying dependencies beyond platform metrics.

Processing rules avoid repeated editing of individual alert definitions. In this case, an operator sees a sustained VM disk latency metric but cannot identify a particular application request. “Use a scoped alert processing rule for the maintenance window” would not satisfy that requirement; the supported action is “Application Insights request traces and dependency telemetry where instrumented”. Application traces connect user requests to underlying dependencies beyond platform metrics.

VM insights provides richer VM performance visibility using configured data sources. In this case, a dashboard showing aggregate CPU cannot explain a single failed checkout. “VM insights in Azure Monitor with the required agent/configuration” would not satisfy that requirement; the supported action is “Correlated application request and exception diagnostics”. Infrastructure aggregates do not attribute individual application failures.

VM insights depends on proper telemetry enrollment rather than just dashboard creation. In this case, a dashboard showing aggregate CPU cannot explain a single failed checkout. “Enable the supported Azure Monitor agent and data collection configuration” would not satisfy that requirement; the supported action is “Correlated application request and exception diagnostics”. Infrastructure aggregates do not attribute individual application failures.

Processing rules avoid repeated editing of individual alert definitions. In this case, a dashboard showing aggregate CPU cannot explain a single failed checkout. “Use a scoped alert processing rule for the maintenance window” would not satisfy that requirement; the supported action is “Correlated application request and exception diagnostics”. Infrastructure aggregates do not attribute individual application failures.

Increasing compute memory may address capacity but does not configure telemetry ingestion. The competing choice “Raise the VM memory size and assume guest counters appear automatically” does not meet the specific requirement: VM insights displays basic Azure VM host utilization, but an operations team also needs guest operating-system performance counters collected in Log Analytics. Which prerequisite should be configured. The supported action is “Enable the supported Azure Monitor Agent and data collection rule for the guest telemetry required by the workload”.

A billing notification contains cost information and does not install or configure an OS performance counter collector. The competing choice “Add only a billing alert with no performance data collection” does not meet the specific requirement: VM insights displays basic Azure VM host utilization, but an operations team also needs guest operating-system performance counters collected in Log Analytics. Which prerequisite should be configured. The supported action is “Enable the supported Azure Monitor Agent and data collection rule for the guest telemetry required by the workload”.

Platform-only metrics cannot satisfy an explicit requirement for guest operating-system counters. The competing choice “Disable guest-level collection and rely exclusively on platform CPU metrics” does not meet the specific requirement: VM insights displays basic Azure VM host utilization, but an operations team also needs guest operating-system performance counters collected in Log Analytics. Which prerequisite should be configured. The supported action is “Enable the supported Azure Monitor Agent and data collection rule for the guest telemetry required by the workload”.

Disk capacity does not govern which performance streams the monitoring agent is configured to collect. The competing choice “Increase the new VM operating system disk size instead of checking monitoring rules” does not meet the specific requirement: VM insights shows guest performance for one Azure VM but not for another newly onboarded VM. The agent is installed on both. What data collection configuration should be compared next. The supported action is “Verify the expected Azure Monitor Data Collection Rule is associated with the new VM and contains the required guest performance streams”.

Removing the shared destination would destroy working telemetry rather than repair the new VM’s missing counters. The competing choice “Disable Log Analytics for both VMs to make the dashboards match” does not meet the specific requirement: VM insights shows guest performance for one Azure VM but not for another newly onboarded VM. The agent is installed on both. What data collection configuration should be compared next. The supported action is “Verify the expected Azure Monitor Data Collection Rule is associated with the new VM and contains the required guest performance streams”.

An assigned public IP is unrelated to Data Collection Rule association and expands network exposure unnecessarily. The competing choice “Create a public Internet IP for the VM and assume that causes guest counters to appear” does not meet the specific requirement: VM insights shows guest performance for one Azure VM but not for another newly onboarded VM. The agent is installed on both. What data collection configuration should be compared next. The supported action is “Verify the expected Azure Monitor Data Collection Rule is associated with the new VM and contains the required guest performance streams”.

IP flow verify reports effective allow or deny behavior and matching rules. In this case, a network engineer needs periodic tests of connectivity from one VM to an internal API. “IP flow verify for the target VM and flow tuple” would not satisfy that requirement; the supported action is “Network Watcher Connection Monitor”. Connection Monitor can test reachability and performance along network paths.

Next-hop checks identify the Azure routing decision toward a destination. In this case, a network engineer needs periodic tests of connectivity from one VM to an internal API. “Network Watcher next hop or effective route inspection” would not satisfy that requirement; the supported action is “Network Watcher Connection Monitor”. Connection Monitor can test reachability and performance along network paths.

VM insights provides richer VM performance visibility using configured data sources. In this case, a network engineer needs periodic tests of connectivity from one VM to an internal API. “VM insights in Azure Monitor with the required agent/configuration” would not satisfy that requirement; the supported action is “Network Watcher Connection Monitor”. Connection Monitor can test reachability and performance along network paths.

IP flow verify reports effective allow or deny behavior and matching rules. In this case, a VM's ping works but TCP 443 intermittently fails. “IP flow verify for the target VM and flow tuple” would not satisfy that requirement; the supported action is “Connection Monitor testing the specific TCP endpoint and port”. Protocol-specific probing reveals failures that ICMP alone cannot show.

VM insights provides richer VM performance visibility using configured data sources. In this case, a VM's ping works but TCP 443 intermittently fails. “VM insights in Azure Monitor with the required agent/configuration” would not satisfy that requirement; the supported action is “Connection Monitor testing the specific TCP endpoint and port”. Protocol-specific probing reveals failures that ICMP alone cannot show.

VM insights depends on proper telemetry enrollment rather than just dashboard creation. In this case, a VM's ping works but TCP 443 intermittently fails. “Enable the supported Azure Monitor agent and data collection configuration” would not satisfy that requirement; the supported action is “Connection Monitor testing the specific TCP endpoint and port”. Protocol-specific probing reveals failures that ICMP alone cannot show.

Connection Monitor can test reachability and performance along network paths. In this case, an administrator wants to determine whether a source port is denied by an NSG. “Network Watcher Connection Monitor” would not satisfy that requirement; the supported action is “IP flow verify for the target VM and flow tuple”. IP flow verify reports effective allow or deny behavior and matching rules.

Next-hop checks identify the Azure routing decision toward a destination. In this case, an administrator wants to determine whether a source port is denied by an NSG. “Network Watcher next hop or effective route inspection” would not satisfy that requirement; the supported action is “IP flow verify for the target VM and flow tuple”. IP flow verify reports effective allow or deny behavior and matching rules.

Protocol-specific probing reveals failures that ICMP alone cannot show. In this case, an administrator wants to determine whether a source port is denied by an NSG. “Connection Monitor testing the specific TCP endpoint and port” would not satisfy that requirement; the supported action is “IP flow verify for the target VM and flow tuple”. IP flow verify reports effective allow or deny behavior and matching rules.

Next-hop checks identify the Azure routing decision toward a destination. In this case, two NSGs are attached and an operator cannot identify which blocks RDP. “Network Watcher next hop or effective route inspection” would not satisfy that requirement; the supported action is “Inspect effective security rules or IP flow verification”. Effective rules reveal combined subnet and NIC filtering decisions.

Effective routing can direct traffic via configured appliances. In this case, two NSGs are attached and an operator cannot identify which blocks RDP. “A user-defined route may supersede the expected peering route” would not satisfy that requirement; the supported action is “Inspect effective security rules or IP flow verification”. Effective rules reveal combined subnet and NIC filtering decisions.

Protocol-specific probing reveals failures that ICMP alone cannot show. In this case, two NSGs are attached and an operator cannot identify which blocks RDP. “Connection Monitor testing the specific TCP endpoint and port” would not satisfy that requirement; the supported action is “Inspect effective security rules or IP flow verification”. Effective rules reveal combined subnet and NIC filtering decisions.