Operational Excellence — Azure Administrator (AZ-104)
Monitoring depth and operational overhead pull in opposite directions
The exam surfaces this tension with constraints like "minimal configuration," "without deploying agents," or "existing Log Analytics workspace." Application Insights is deep but requires SDK instrumentation. Azure Monitor metrics are broader but shallower. Activity Log captures control-plane operations, not application behavior. Azure Policy enforces configuration drift, not runtime health. The wording in the scenario tells you which observability layer the question is testing — read the constraint before selecting the service.
What This Pattern Tests
Azure operational excellence questions test whether you automate operations with Azure-native tools. Azure Pipelines with YAML definitions provide version-controlled CI/CD. Azure Policy enforces resource configuration standards (require tags, restrict VM sizes, mandate encryption). Azure Automation runbooks handle routine tasks like VM patching, certificate rotation, and resource cleanup. For AZ-400, the focus is on combining Azure Boards for work tracking, Azure Repos for source control, and Azure Pipelines for build/release into a unified DevOps workflow. Azure Monitor action groups trigger Logic Apps or Azure Functions for automated incident response. The trap is building custom scripts on VMs when Azure Automation, Logic Apps, or Azure Functions provide managed alternatives.
Decision Axis
Manual scripts vs. managed automation services. Azure rewards declarative, policy-driven operations over imperative scripts.
Associated Traps
More Top Traps on This Exam
Decision Rules
When the scenario explicitly requires packet capture, hop-level path tracing, or connection-path diagnosis — not just metric dashboards — Azure Network Watcher satisfies signal-completeness; Azure Monitor Insights does not.
Whether a targeted Azure Monitor metric alert rule on the storage throttling metric satisfies signal-completeness at lower cost, or whether full Azure Monitor Insights for Storage (Log Analytics workspace plus all diagnostic categories) is required to meet the alerting SLA.
Whether to apply a performance-visualization tool (Azure Monitor Insights) or a network-diagnostic tool (Azure Network Watcher) when metric dashboards are clean but network-layer connectivity failures persist — the deciding constraint is diagnostic depth at the packet and flow level, not metric surface area.
Domain Coverage
Difficulty Breakdown