Giving a tool the wrong kind of data
The wrong answers assign a data type to the wrong Azure Monitor tool. Metrics Explorer charts numeric metrics but does not run KQL over log tables. Logs holds log and trace records queried with KQL, not a time-series numeric store. The activity log records control-plane operations, and Service Health reports platform incidents, so neither stores performance values. Metrics suit numeric values at regular intervals, Log Analytics in KQL mode suits read-only queries, and an activity log alert suits a discrete event such as a role assignment.
See it in a sample questionCrediting a diagnostic setting with abilities it lacks
Storage and a Log Analytics workspace are offered for streaming to a non-Microsoft SIEM, although only Event Hubs forwards a stream to external systems. One setting is credited with two workspaces, although a setting defines at most one of each destination type, so a second workspace needs a second setting. The wrong options also cap a resource at three settings when the limit is five, demand the same subscription when cross-subscription destinations are allowed, and demand premium storage, which is not supported.
See it in a sample questionSwapping Next hop and IP flow verify
The wrong answers hand routing questions to IP flow verify and NSG diagnostics, and filtering questions to Next hop. IP flow verify checks whether a packet is allowed or denied at the virtual machine and names the security rule responsible. Next hop reports routing: the hop type, IP address and route table ID for a destination. Connection monitor, Packet capture and Topology are also offered, yet none of them names the deciding rule or computes a route.
See it in a sample questionTreating alert rules, processing rules and action groups as one layer
An alert rule combines the monitored resources, the signal and the conditions; action groups and suppression sit downstream of it. Alert processing rules do not create alerts, they only modify alerts that are already firing, and their scope stays within the same subscription. When a suppression rule and an apply-action-groups rule match one alert, suppression takes precedence. The wrong options claim the two cancel out, or that applying action groups wins.
See it in a sample questionBlurring drills, failover and failback in Site Recovery
Disaster recovery drills validate a plan without affecting ongoing replication. Planned failover, unplanned failover and failback each move or return a workload, so offering one as a non-disruptive test fails. Planned failover is for expected outages with zero-data loss; unplanned failover answers a disaster with minimal loss that depends on replication frequency. The wrong options also claim failback is blocked after failover, or that a planned failover needs a fully lost region.
See it in a sample question