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 organization is preparing to deploy several new workloads to Microsoft Azure using a consumption-based pricing model. The finance and engineering teams want to understand which configuration decisions and operational activities will directly determine their recurring cloud bill.
Which combination of factors directly drives the ongoing variable costs of cloud resources in Azure?
Management groups, Azure Policy definitions, and custom domain verifications are structural and compliance mechanisms designed to organize multiple subscriptions hierarchically, enforce corporate compliance standards across resources, and link vanity domains to hosted cloud services.
This option would be correct if the scenario focused on enterprise governance structure, organizational hierarchies, or policy compliance frameworks rather than consumption-based pricing elements.
In Microsoft Azure's consumption-based model, organizations pay only for the cloud resources and services they consume. Unlike traditional on-premises infrastructure where capital expenditures (CapEx) dictate upfront costs, Azure resource costs are operational expenditures (OpEx) governed by specific usage metrics and architectural configuration choices.
Resource type, service tier, geographic location, data transfer direction, and support plan tier are the foundational elements that dictate meter generation and consumption charges on an Azure invoice.
Administrative identifiers such as resource group names, subscription display names, and custom Azure portal themes are organizational and user interface properties. They exist to help administrators logically identify, browse, and personalize their cloud environment.
This option would be relevant if the question asked about governance naming standards or cloud administrative best practices, but it has no influence on consumption billing.
Resource tags, resource locks, and Azure Role-Based Access Control (RBAC) are governance and security capabilities provided natively by Azure Resource Manager (ARM) to manage metadata, prevent accidental modification or deletion, and enforce least-privilege security access.
ReadOnly or CanNotDelete locks to subscriptions, resource groups, or individual resources is a built-in platform safeguard that is entirely free of charge.This option would be correct if the goal were implementing resource governance, cost tracking taxonomy, and access security, rather than identifying direct drivers of variable consumption costs.
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