Operational Excellence — Azure Solutions Architect (AZ-305)
Application Insights, Monitor, and Activity Log Compared
A scenario requires distributed tracing across microservices, automated remediation on metric thresholds, and a change history for compliance review. Routing all three to Azure Monitor is directionally right and precisely wrong. Application Insights provides request tracing and dependency failure diagnosis at the application layer. Azure Monitor aggregates infrastructure metrics and logs, and drives Action Groups for automated response workflows. Activity Log records control-plane changes for change management and audit. Each service answers a specific operational question, and the scenario names which question is in scope. Treating Monitor as a catch-all for all three is the mistake this question type is built to catch.
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
Decision Rules
Whether to route platform diagnostic logs through Azure Monitor Diagnostic Settings into the Log Analytics workspace in addition to configuring workspace-based Application Insights, versus relying on Application Insights alone as the complete observability solution.
Whether to satisfy the 180-day compliance retention requirement by routing Azure resource diagnostic logs through Azure Monitor diagnostic settings into a Log Analytics workspace (correct platform-layer path) versus relying on Application Insights, which captures only application-instrumented telemetry and creates a platform-layer observability blind spot that fails the stated compliance constraint.
Whether to route platform-level resource diagnostic logs through Azure Monitor Diagnostic Settings to a Log Analytics workspace configured with tiered (interactive + archive) retention, or to conflate platform-log compliance with application telemetry by targeting Application Insights — which cannot natively ingest platform diagnostic events and forces a custom export pipeline that adds operational failure-path complexity.
Whether to satisfy the 180-day platform-log retention requirement by configuring Azure Monitor diagnostic settings to route to a Log Analytics workspace with a native retention policy, versus constructing a custom archival pipeline (e.g., Event Hubs to Blob Storage) or relying solely on Application Insights—which covers only the application telemetry layer and leaves the platform layer unobserved.
Route Azure Monitor Activity Log to a Log Analytics workspace via diagnostic settings for ARM control-plane audit retention, rather than extending Application Insights, which is architecturally blind to control-plane events regardless of configuration.
Domain Coverage
Difficulty Breakdown