AZ-900 ยท Identity, access and security
Azure role-based access control (Azure RBAC)
Azure RBAC roles (built-in like Owner, Contributor, Reader, and custom), role assignments at a scope, inheritance down the hierarchy and least privilege.
Key points
- Azure RBAC: who can do what to which resources.
- Role assignment: security principal (user, group, service principal, managed identity) + role definition + scope.
- Scopes, inherited downward: management group, subscription, resource group, resource.
- Owner: all, incl. roles. Contributor: manage, cannot grant access. Reader: view. User Access Administrator: access.
- Additive permissions; least privilege: smallest role, narrowest scope.
Source: https://learn.microsoft.com/en-us/azure/role-based-access-control/overview
Practice questions
Which built-in Azure role lets a user view all resources but not change anything?
- Contributor
- User Access Administrator
- Owner
- Reader
Show answer
Answer: D. Reader
Reader allows viewing all resources without making changes. Contributor and Owner can modify resources, and User Access Administrator manages who has access.
At which of these scopes can you assign an Azure role?
- Management group
- Azure region
- Resource group
- Resource tag
- Individual resource
Show answer
Answer: A. Management group, C. Resource group, E. Individual resource
Azure RBAC supports four scope levels: management group, subscription, resource group and resource. Regions and tags are not scopes for role assignments.
A role assigned at subscription scope does not apply to the resource groups inside that subscription until you assign it there too.
Show answer
Answer: False
False. Scopes form a parent-child hierarchy, and a role assigned at a parent scope is inherited by every child scope, so a subscription-level assignment already covers its resource groups and resources.
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.
