Question 11 — AZ-104 Practice Exam 8
For each management scope or boundary, drag it to its characteristic.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Generates separate billing reports and invoices per scope | [Gap 1] |
| Scope where access-management policies are applied at the subscription level | [Gap 2] |
| Can be nested; governance conditions (policy/RBAC) inherit to descendant subscriptions | [Gap 3] |
| Cannot be nested; deleting it deletes all included resources | [Gap 4] |
- Account
- Resource
- Resource group
- Management group
- Access control boundary
- Billing boundary
Correct answers
- Gap 1: Billing boundary
- Gap 2: Access control boundary
- Gap 3: Management group
- Gap 4: Resource group
Explanations
Correct Matches
Billing boundary – Subscriptions act as a billing boundary, producing separate invoices/reports so you can organize and track costs.
Access control boundary – Subscriptions are an access control boundary; you apply policies and access controls at this scope.
Management group – Can be nested and anything assigned (policy/RBAC) inherits to all child subscriptions/resource scopes.
Resource group – Cannot be nested; actions at the RG (for example, delete) apply to all resources in that group.
Unused Item(s)
Resource – The basic building block (VMs, VNets, DBs), not a boundary or hierarchy container.
Account – An identity in Microsoft Entra ID (or trusted directory) that owns subscriptions; not a policy/billing boundary itself.