AZ-900 Describe Azure management and governance Practice Question
What is Azure Cost Management's 'cost allocation' feature used for?
⚠ Common exam trap
A common mix-up: candidates confuse cost allocation (which redistributes existing costs for reporting) with cost optimization actions like shutting down resources or purchasing reservations, leading candidates to pick options that describe automated cost-saving features instead.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
To distribute shared infrastructure costs across teams or business units for reporting
Azure Cost Management's 'cost allocation' feature allows you to assign or redistribute shared infrastructure costs (e.g., common network, management, or security services) to specific teams, departments, or business units. This is done by defining allocation rules that split costs based on percentages or custom keys, enabling accurate chargeback and showback reporting without changing how resources are billed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To automatically reduce costs by shutting down unused resources
Why it's wrong here
Automatically shutting down unused resources is an optimization action achieved through Azure Automation (Start/Stop VMs v2), Azure Automanage, or scheduling policies that deallocate VMs outside business or peak hours. Cost allocation is a chart-of-accounts mapping exercise: it takes expenses that were tracked on a shared account and redistributes them later to beneficiaries for reporting. It neither inspects resource utilization, identifies idle assets, nor initiates shutdown calls—those are operational management features. Treating it as a cost-reduction mechanism ignores that its sole output is a re-classified cost report, not a savings event.
- ✓
To distribute shared infrastructure costs across teams or business units for reporting
Why this is correct
Cost allocation in Azure Cost Management lets you create distribution rules that take shared costs (such as a central ExpressRoute connection or shared support fees) and proportionally reattribute them to specific teams, projects, or business units based on tags, subscriptions, or resource groups. It reorganizes the Cost Management report so each team can see its 'fair share' of an otherwise centralized cost, which is the foundation for chargeback or showback reporting. Critically, it only changes how costs are displayed for reporting; it does not alter billing, enforce limits, or trigger any automated action.
- ✗
To set spending limits for individual resource groups
Why it's wrong here
A spending limit is an enforced cap, typically set in the Azure portal or via Azure Budgets, that stops or alerts on new spend once a threshold is reached. Cost allocation has no enforcement capability; it is purely a financial-reporting transformation that redistributes existing costs among cost owners. Budgets can be scoped to resource groups and can fire alerts or disable resources, but they never change the attribution of costs across teams. Therefore, this option mistakes a billing-control mechanism for an attribution/accounting feature.
- ✗
To automatically purchase Reserved Instances based on usage patterns
Why it's wrong here
Reserved Instance purchases are procurement actions that give guaranteed capacity and lower rates, and they are executed manually by an administrator or based on recommendations from Azure Advisor or the Savings plan evaluation tools. Cost allocation operates after such purchases, taking the amortized cost of the reservation and assigning portions to the relevant consuming workloads for reporting. It does not analyze usage patterns, make buying decisions, or interact with the purchasing workflow in any way. Conflating cost allocation with advisory purchase suggestions confuses cost accountability with cost optimization procurement.
Go deeper
Related to this question
Learn chapter
Azure Cost Management and Billing
Key term
Security
Security in IT is the practice of protecting systems, networks, and data from unauthorized access, damage, or theft.
Key term
Feature
A feature is a distinct unit of functionality that delivers value to the user, often managed and tracked throughout the software development lifecycle.
About these practice questions
Courseiva writes every AZ-900 question from scratch — 981 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-900 exam.