Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An enterprise organization operates multiple Azure subscriptions across different business units. The IT security team needs to establish a centralized governance strategy that automatically enforces compliance standards and Role-Based Access Control (RBAC) permissions across all subscriptions and their underlying resources.
Which level of the Azure management hierarchy should the security team use to apply these policies and access controls?
Resource tags are metadata elements composed of key-value pairs that are attached directly to Azure resources, resource groups, or subscriptions to organize them logically for billing, reporting, and operational tracking.
Tags are purely informational metadata and do not serve as structural containers within the Azure management hierarchy. While Azure Policy can be used to audit or require tags, the tags themselves cannot enforce access permissions, implement Azure RBAC, or automatically propagate security rules across subscriptions.
This option would be correct if the organization needed a way to categorize billing data across departments without altering the underlying infrastructure hierarchy.
Azure service quotas and limits are predefined operational boundaries that restrict the quantity of specific resources—such as virtual CPU cores, networking gateways, or storage capacity—that can be provisioned within a subscription or region.
Service quotas are designed to prevent accidental over-provisioning and manage cloud capacity. They do not define access boundaries, assign user roles, or enforce organizational compliance policies across multiple subscriptions.
This option would be correct if the organization needed to prevent individual engineering teams from exceeding regional compute resource limits.
Resource groups are logical containers designed to hold and manage related Azure resources, such as virtual machines, virtual networks, and storage accounts, that share a common lifecycle.
A resource group exists entirely within the scope of a single subscription. It cannot contain other subscriptions or apply governance rules to resources residing outside of its own boundary. Implementing policies or RBAC at the resource group level would require manual configuration across hundreds of individual resource groups across separate subscriptions.
This option would be correct if the organization needed to group and secure resources belonging to a single application workload within one specific subscription.
Management groups are containers in Azure that sit above subscriptions in the resource hierarchy. They provide a unified governance scope that allows organizations to manage access policies, compliance rules, and security controls across multiple Azure subscriptions efficiently.
By assigning Azure Policy definitions and Azure Role-Based Access Control (RBAC) roles at the management group level, all configurations and permissions are automatically inherited by:
This inheritance ensures that centralized corporate standards and access boundaries are applied universally without requiring repetitive configuration on each subscription.
Applying governance at the management group scope eliminates administrative overhead and prevents configuration drift across multiple subscriptions, ensuring all resources remain consistently secure and compliant from the top down.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated