This chapter covers the consumption-based pricing model that underlies cloud computing — paying for what you use rather than owning fixed infrastructure. AZ-900 tests this under objective 1.4, alongside broader cost-management concepts.
Jump to a section
A simple way to picture Consumption-Based Pricing Model
If you owned your own water tank, you'd pay a large upfront cost to install it, sized to handle your highest possible usage, and then own it regardless of how much water you actually use month to month. Municipal water service works differently: you pay based on how much water you actually use each month, with no large upfront tank to buy or maintain. The consumption-based model in cloud computing works the same way — instead of buying and sizing infrastructure upfront for your highest possible demand, you pay based on what you actually use, adjusting automatically as your usage goes up or down.
What the consumption-based model is
The consumption-based model means paying for cloud resources based on actual usage — how long a virtual machine ran, how much storage was used, how many requests a service processed — rather than paying a fixed amount regardless of usage. This contrasts with the traditional model of purchasing fixed hardware capacity upfront.
How it changes cost planning
With traditional on-premises infrastructure, an organization typically has to estimate its peak future demand and buy hardware to cover it, even if that capacity sits idle most of the time. With a consumption-based model, an organization pays closer to what it actually uses, scaling costs up and down with actual demand rather than committing to fixed capacity in advance.
CapEx vs. OpEx
This shift is often described in terms of capital expenditure (CapEx) versus operating expenditure (OpEx). Buying physical servers is a capital expense — a large upfront investment in an asset the organization owns. Paying for cloud usage as it happens is an operating expense — an ongoing cost tied to actual consumption, without large upfront ownership.
Why this matters
The consumption-based model reduces the risk of either overprovisioning (paying for capacity that goes unused) or underprovisioning (not having enough capacity when demand spikes), since costs scale more closely with actual usage. It also means costs need active monitoring, since usage-based spending can grow if resources aren't managed carefully.
Understand what's being metered
Different resource types are metered differently — compute time, storage volume, data transfer, or number of requests, for example. Understanding what drives cost for a given service is the first step in managing it.
Compare against fixed-capacity planning
Traditional infrastructure required estimating peak demand and buying for it upfront. The consumption model instead lets cost follow actual usage more closely.
Recognize the CapEx-to-OpEx shift
Moving from owned hardware to consumption-based cloud spending shifts cost from a large upfront capital expense to an ongoing operating expense tied to usage.
Monitor usage actively
Because cost scales with usage, unmanaged or forgotten resources can accumulate unexpected costs — active monitoring and cleanup of unused resources is part of managing a consumption-based environment well.
A company running a seasonal e-commerce site scales up its compute resources during a busy sales period and scales back down afterward, paying only for the extra capacity while it's actually needed — something a fixed-capacity, owned-hardware setup couldn't do as efficiently.
A separate, common real-world issue: a development team spins up test resources for a project and forgets to delete them once the project is finished. Because those resources continue running, the organization keeps paying for capacity nobody is using — a reminder that a consumption-based model still requires active cost management, not just "set it and forget it."
Objective 1.4 expects candidates to understand what the consumption-based model means and how it contrasts with traditional, fixed-capacity infrastructure spending.
A common wrong answer is assuming consumption-based pricing is always cheaper than owning hardware outright — it depends on the usage pattern; a steady, predictable, always-on workload might sometimes cost more under a pure consumption model than a well-utilized owned asset, though the flexibility usually outweighs this for most organizations. Another common trap is confusing CapEx and OpEx — capital expenditure is a large upfront asset purchase, operating expenditure is an ongoing usage-based cost.
Stable terms: consumption-based model, CapEx, OpEx. Knowing that cloud spending is generally framed as OpEx, replacing traditional CapEx hardware purchases, is a frequently tested distinction.
Memory trick: CapEx = buy it once, own it. OpEx = pay for it as you use it. Cloud consumption-based pricing shifts spending from CapEx toward OpEx.
The consumption-based model means paying for cloud resources based on actual usage, not a fixed upfront cost.
This model generally shifts spending from capital expenditure (CapEx) toward operating expenditure (OpEx).
Consumption-based pricing reduces the risk of overprovisioning or underprovisioning capacity, since cost follows actual demand more closely.
Because cost scales with usage, active monitoring is needed to avoid unexpected spending from unused or forgotten resources.
These come up on the exam all the time. Here's how to tell them apart.
Traditional (CapEx) Model
Large upfront investment in owned hardware
Capacity sized for estimated peak demand
Costs are relatively fixed once purchased
Underused capacity still costs the same
Consumption-Based (OpEx) Model
Ongoing cost tied to actual usage
Capacity can scale with real-time demand
Costs vary based on consumption
Requires active monitoring to avoid unexpected spend
Mistake
Consumption-based pricing is always cheaper than owning hardware.
Correct
It depends on the workload's usage pattern — it's generally more efficient for variable or unpredictable demand, but isn't automatically the cheapest option in every single scenario.
Mistake
Consumption-based pricing means costs are fixed and predictable.
Correct
The opposite is often true — costs scale with actual usage, which means unmanaged or unexpectedly high usage can lead to unpredictable bills without active monitoring.
Mistake
CapEx and OpEx are just two names for the same thing.
Correct
CapEx is a large upfront investment in an owned asset; OpEx is an ongoing cost tied to usage. Cloud consumption-based pricing is generally treated as OpEx.
It means paying for cloud resources based on how much you actually use — compute time, storage, data transfer, and so on — rather than paying a fixed amount regardless of usage, as you would with owned, on-premises hardware.
CapEx (capital expenditure) is a large upfront investment in an owned asset, like buying physical servers. OpEx (operating expenditure) is an ongoing cost tied to usage, like a cloud subscription bill. Cloud consumption-based pricing is generally categorized as OpEx.
Not automatically — it depends on the workload. It's generally efficient for variable or unpredictable demand, but a steady, highly-utilized workload might sometimes be similarly or more cost-effective under a well-managed owned-hardware setup. Flexibility, not guaranteed lowest cost, is the main benefit.
You've just covered Consumption-Based Pricing Model — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?