AZ-305 ยท Logging and monitoring design
Log Analytics workspace design
Single vs multiple workspaces, data residency and region, workspace vs resource-context access control, table plans and retention/archive as design and cost levers.
Key points
- One workspace first; add more only for separate Entra tenants, regional data, separate owners, split billing or per-table retention.
- 'Use resource or workspace permissions' (default): resource-context access for resource owners.
- 'Require workspace permissions': explicit grants.
- Table-level RBAC limits specific tables.
- Cost: Analytics, Basic, Auxiliary plans; retention 30 days default, analytics 2 years, total 12; commitment tiers.
Source: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/workspace-design
Practice questions
Up to how long can the total retention of a Log Analytics table be set, including long-term retention?
- 2 years
- 5 years
- 12 years
- 25 years
Show answer
Answer: C. 12 years
Total retention, which includes low-cost long-term retention, can reach 12 years. Two years is the ceiling for analytics (interactive) retention of Analytics tables, which is the usual distractor.
Which are valid reasons to add another Log Analytics workspace instead of keeping a single one?
- Resources live in two separate Microsoft Entra tenants
- Billing must be split in a way cost reports cannot provide
- Query speed drops once a workspace holds a lot of data
- App teams should see only logs of the resources they own
- Resources writing to one table need different retention
Show answer
Answer: A. Resources live in two separate Microsoft Entra tenants, B. Billing must be split in a way cost reports cannot provide, E. Resources writing to one table need different retention
Separate Entra tenants, chargeback that Cost Management or log queries cannot provide, and different retention for different resources in the same table all justify another workspace. Data volume does not impose performance limits on a workspace, and app teams can already see their own resources' logs through resource-context access.
With the default access control mode, a user who can read a virtual machine can query that VM's logs in the workspace without being granted any role on the workspace itself.
Show answer
Answer: True
True. The default mode, 'Use resource or workspace permissions', enables resource-context access: read access to a resource carries over to that resource's data in the workspace. Switch to 'Require workspace permissions' if every user must be granted access explicitly.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
