Bitzu

AZ-305 ยท Governance and compliance design

Subscriptions and resource groups

Subscription as a billing, scale, quota and isolation boundary, per-environment or per-workload subscriptions, resource group by lifecycle, resource locks.

Key points

  • Subscription: billing unit, scale and quota boundary, policy/RBAC isolation; split per workload and environment.
  • Resource group: lifecycle container; each resource in exactly one group; deleting the group deletes its contents.
  • Resource locks: CanNotDelete (read and modify, no delete), ReadOnly (read only).
  • Locks: inherited by child scopes, override user permissions, control plane operations only.

Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources

Practice questions

Single choice

Which resource lock level lets authorized users read and modify a resource but not delete it?

  1. CanNotDelete
  2. ReadOnly
  3. DoNotModify
  4. DenyAssignment
Show answer

Answer: A. CanNotDelete

CanNotDelete (shown as Delete in the portal) still allows reads and updates but blocks deletion. ReadOnly also blocks updates. DoNotModify and DenyAssignment are not lock levels.

Select all that apply

Which are valid reasons to place a workload in its own subscription?

  1. A business unit needs its own billing and cost ownership
  2. The workload is nearing subscription-level quota limits
  3. Production needs a separate policy and RBAC boundary from dev
  4. A resource needs to belong to two resource groups
  5. Resources should inherit the subscription's tags automatically
Show answer

Answer: A. A business unit needs its own billing and cost ownership, B. The workload is nearing subscription-level quota limits, C. Production needs a separate policy and RBAC boundary from dev

Subscriptions are billing, quota and access/policy boundaries, so separate cost ownership, quota headroom and a distinct prod vs non-prod governance boundary are all good reasons. A resource cannot belong to two resource groups in any design, and tags are never inherited automatically from a subscription.

True or false

A ReadOnly lock on a storage account also prevents users from deleting blobs through the Blob service endpoint.

Show answer

Answer: False

False. Locks apply only to control plane operations sent to Azure Resource Manager. Data plane operations, such as deleting a blob through the account's blob endpoint, are not blocked by the lock.

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.

Download on the App StoreGet it on Google Play

More AZ-305 topics in this module