Study guide
2.1 Logging Solution Design
Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Orientation
1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide
2 Chapter 2: Logging, Monitoring & Diagnostics Design
2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design
3 Chapter 3: Authentication & Authorization Design
3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design
4 Chapter 4: Governance, Compliance & Identity Governance Design
4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design
5 Chapter 5: Relational Data Storage Design
5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design
6 Chapter 6: Semi-Structured & Unstructured Data Storage Design
6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design
7 Chapter 7: Data Integration & Analytics Design
7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design
8 Chapter 8: Backup & Disaster Recovery Design
8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design
9 Chapter 9: High Availability Design
9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design
10 Chapter 10: Compute Solution Design
10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)
11 Chapter 11: Application Architecture Design
11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)
12 Chapter 12: Migration Design
12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)
13 Chapter 13: Network Solution Design
13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design
14 Chapter 14: Final Review, Exam Strategy & Career Path
14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path
2.1 Logging Solution Design
Key Takeaways Explain This Topic AI
Azure Monitor splits data into two platforms: Metrics (automatic, numeric time-series) and Logs (requires a Log Analytics workspace and KQL)
Diagnostic settings are the only way to export resource logs into a workspace, are forward-only, and support up to 5 per resource with one destination of each type
Table plans (Analytics/Basic/Auxiliary) trade off ingestion cost, query power, and retention -- match the plan to how often the data is queried and alerted on
The Activity Log only records control-plane operations (create/delete/modify), never data-plane events like CPU spikes or app exceptions
Long-term retention can extend to 12 years (4,383 days), but archived data requires a search job to become interactively queryable again
Last updated: July 2026
Why This Topic Matters on AZ-305
Design solutions for logging and monitoring anchors Domain 1 (Design identity, governance, and monitoring solutions), the exam's second-largest domain at 25-30% of the AZ-305 score. Logging design is also the quietest cross-cutting skill on the exam: nearly every scenario in the Data Storage, Business Continuity, and Infrastructure domains eventually asks "how would you know if this failed?" If you cannot reason correctly about Azure Monitor 's two data platforms and how diagnostic settings move data between them, you will also miss points buried inside unrelated-looking questions about databases, VMs, and networking.
Core Concepts: Two Data Platforms, One Front Door
Azure Monitor collects data into two platforms, and AZ-305 scenario questions frequently hinge on knowing which platform a given piece of data lives in:
Metrics — lightweight, numeric time-series data (for example, CPU percentage, queue length). Platform metrics are collected automatically at roughly one-minute granularity with no configuration required and are retained for a fixed window measured in months, viewable immediately in Metrics Explorer.
Logs (Azure Monitor Logs) — structured event records queried with Kusto Query Language (KQL) inside a Log Analytics workspace (LAW) . Logs are not collected automatically; you must explicitly configure collection.
The bridge between raw platform data and a workspace is the diagnostic setting . A diagnostic setting is a per-resource configuration object that says "take this data, send it to these destinations." It can capture three source types:
Source Collected by default? What it contains
Platform metrics Yes (viewable in Metrics Explorer) Numeric time series; a diagnostic setting only exports a copy into logs-based destinations
Activity log Yes (subscription-level, 90-day retention) Control-plane operations — who created/deleted/modified a resource — never data-plane operations
Resource logs No Service-specific operational data (for example, Key Vault access events, NSG flow logs, SQL query performance data)
Exam trap : the Activity Log only records management-plane actions (an ARM PUT / DELETE / PATCH against a resource). It never shows you that a virtual machine's CPU spiked or that an application threw an exception — those are resource logs and metrics, which require a diagnostic setting to persist into a workspace for historical querying.
Log Analytics Workspace Design
A Log Analytics workspace is both the storage container and the KQL query engine for Azure Monitor Logs. Two workspace-design decisions repeatedly appear on AZ-305:
Centralized vs. per-team/per-subscription workspaces. One centralized workspace simplifies cross-resource KQL correlation and consolidated alerting, but it mixes data ownership and access boundaries across teams. Separate workspaces isolate access control and cost allocation per team but complicate any query that needs to span them. Azure Monitor's access control mode lets a workspace require workspace-context permissions (broad access to all tables) or resource-context permissions (a user only sees data from resources they can already read) — choose resource-context when regulatory or organizational boundaries require it inside a shared workspace.
Table plan selection. Every table in a workspace runs on a plan that trades off cost, query power, and retention:
Plan Ingestion cost Query capability Default interactive retention Best for
Analytics Standard (highest) Full KQL, supports alerting, workbooks, dashboards 30 days (extendable up to 730 days) Security, operational, and alerting data you query often
Basic Substantially lower Limited KQL, no alerting on the table directly Fixed 30 days High-volume verbose diagnostic/debug logs queried occasionally
Auxiliary Lowest Very limited query, no alerting Total retention period only (queryable via search jobs) Extreme-volume compliance/audit data rarely queried
A table can be extended with long-term (archive) retention up to 12 years (4,383 days) at low cost regardless of plan; archived data is not interactively queryable until you run a search job that rehydrates the needed slice into a temporary results table. Two tables always keep 90 days free by default , regardless of workspace setting: Usage and AzureActivity . Application Insights App* tables ( AppRequests , AppExceptions , AppDependencies , and others) also default to 90-day free retention.
Design Constraints You Must Know
Up to five diagnostic settings per resource , and a single setting can define at most one of each destination type — if a design calls for two Log Analytics workspaces (for example, one regional operational workspace and one central security workspace), you need two separate diagnostic settings on that resource.
Regional destinations (storage accounts, Event Hubs) must sit in the same region as the monitored resource when that resource is regional.
After a diagnostic setting is created, data typically starts flowing within about 90 minutes ; nothing is backfilled — diagnostic settings are forward-only.
Metrics exported through a diagnostic setting are flattened : multi-dimensional metrics lose their per-dimension breakdown and are aggregated when they land in a workspace.
Scenario Walkthrough
A retail company runs workloads across 40 subscriptions. The security team wants one place to run KQL threat-hunting queries across every subscription, while each application team wants to troubleshoot only their own resources without seeing other teams' data. The correct design uses one centralized Log Analytics workspace with the access control mode set to resource-context permissions , so RBAC on each individual resource — not workspace membership — determines what a given engineer can query, while the security team (granted workspace-level read access) still sees everything centrally.
Key Takeaways
Metrics and Logs are two distinct Azure Monitor data platforms; only Logs require a Log Analytics workspace and KQL.
Diagnostic settings are the only mechanism to export resource logs, and they are forward-only — never retroactive.
Centralize workspaces for cross-cutting KQL and alerting; use resource-context access control mode to preserve per-team data boundaries within that same workspace.
Match each table's plan (Analytics/Basic/Auxiliary) to how often it needs to be queried and alerted on, not just its volume.
Long-term retention (up to 12 years) is cheap but not interactively queryable without a search job.