Predictability
😟 THE PROBLEM
The app is fast one day and slow the next, and the bill keeps surprising finance.
😊 THE SOLUTION
Make performance and cost predictable with autoscale, estimates and budgets.
- Performance goes up and down✓ Autoscale and load balancing
- No idea what it will cost✓ Estimate first with the pricing calculator
- Surprise bills✓ Budgets with alerts in Cost Management
Quick answer
Predictability in the cloud means you can move forward with confidence, knowing roughly how your system will perform and what it will cost. Performance predictability comes from autoscaling, load balancing and high availability, so users get a consistent experience. Cost predictability comes from tools like the pricing calculator, budgets and cost analysis, which let you forecast and track spend.
Exam objective: 1.2.2 Describe the benefits of reliability and predictability in the cloud. (Skills measured as of July 20, 2026)
Start with a question
Would you trust a bus company if the bus sometimes takes 10 minutes and sometimes 2 hours, and the fare changes every day?
Even if the bus usually arrives, you cannot plan your life around it. Businesses feel the same about technology. They need to know how it will perform and what it will cost before they commit to it.
That confidence is called predictability.
Explain it like I’m 10
The technical explanation
Microsoft’s AZ-900 material splits predictability into two parts:
Performance predictability
- Predict the resources needed for a good experience
- Autoscaling adds capacity before users feel it
- Load balancing spreads traffic evenly
- High availability keeps it running
Cost predictability
- Forecast spend before and after deployment
- Pricing calculator to estimate
- Cost Management to track, forecast and set budgets
- Reservations or savings plans to fix steady costs
Tools that support predictability
| Need | Azure tool |
|---|---|
| Estimate costs before building | Azure pricing calculator |
| Track, analyse and forecast actual spend | Microsoft Cost Management (cost analysis, budgets, alerts) |
| Lock in lower prices for steady usage | Reservations, savings plans |
| Keep performance consistent under load | Autoscale, load balancers, caching |
| Get best-practice recommendations | Azure Advisor, Azure Well-Architected Framework |
| Prevent expensive surprises | Azure Policy (for example, allowed VM sizes and regions) |
Real-world business scenario
A software company selling a SaaS HR product
- The problem
- Customers complained that the app was fast some days and slow on payroll days, and finance could not predict hosting costs per customer.
- What they used
- Autoscale based on request queue length, Redis caching for reports, budgets per environment in Cost Management, tags per customer tier, and a savings plan for the baseline compute.
- Why that choice
- Autoscale and caching gave consistent response times; budgets, tags and committed pricing made spend forecastable and attributable.
- The result
- Payroll-day latency stayed within target, and finance could price new customer contracts using a known cost per tenant.
When to use it and when not to
Predictability is a goal, not a single service. Prioritise it when:
✓ Use it when…
- You must commit prices to customers or budgets to management.
- User experience has to be consistent (customer-facing apps, SLAs to your clients).
- Your workloads have known patterns you can plan capacity and commitments for.
✕ Think twice when…
- Over-optimising predictability for early experiments. Flexibility matters more at that stage.
- Locking into long commitments before you understand usage.
Interview preparation
Say your answer out loud first, then open the model answer. Interviewers care more about your reasoning than the exact words.
Beginner What does predictability mean as a cloud benefit?
Model answer
It means being able to predict how the system will perform and how much it will cost. For performance, things like autoscaling and load balancing keep the experience consistent. For cost, tools like the pricing calculator and budgets help forecast and track spending.
Interviewer follows up
Which Azure tool helps you estimate costs before deploying?
You
The Azure pricing calculator. After deployment, Microsoft Cost Management helps track actual and forecast spend.
Intermediate Pay-as-you-go sounds unpredictable. How do you make cloud costs predictable?
Model answer
Estimate up front with the pricing calculator, set budgets with alerts in Cost Management, use cost analysis and forecasts, tag resources by owner and project, buy reservations or savings plans for steady workloads to lock in prices, and put guardrails with Azure Policy such as allowed VM sizes or regions.
Experienced developer How do you achieve performance predictability for a multi-tenant SaaS product on Azure?
Model answer
Set clear performance targets (for example p95 latency), load-test against them, autoscale on the metrics that matter, isolate noisy tenants (separate pools or throttling per tenant), use provisioned-throughput or premium tiers where consistent latency is required, cache hot data, and watch dependencies with Application Insights. The Performance Efficiency and Cost Optimization pillars of the Well-Architected Framework provide the checklists.
Scenario A finance director asks, "How do I know we will not get a surprise cloud bill next month?" What do you show them?
Model answer
A pricing calculator estimate for the planned architecture, a Cost Management budget with alerts at 50/80/100% and forecast-based alerts, cost analysis views by department using tags, and reservations covering the steady baseline so most of the bill is fixed.
Test yourself with exercises
4 original practice questions in the AZ-900 style. Pick your answers, then check them. You will see why each option is right or wrong. Score 75% or more and this topic is marked complete.
Quick revision
Key points
- Predictability has two parts, performance and cost.
- Performance: autoscaling, load balancing, high availability give a consistent experience.
- Cost: pricing calculator (estimate), Cost Management (track, forecast, budgets, alerts).
- Reservations and savings plans make steady spend more predictable.
- The Well-Architected Framework provides guidance for both.
Important terminology
- Performance predictability
- Confidence that the system will deliver a consistent user experience under expected load.
- Cost predictability
- Confidence in what the cloud will cost, through forecasting, monitoring and controls.
- Azure Well-Architected Framework
- Microsoft's guidance built around five pillars (reliability, security, cost optimization, operational excellence, performance efficiency).
- Budget
- A spending threshold in Microsoft Cost Management that triggers alerts when actual or forecast cost approaches it.
Common mistakes
- Thinking predictability means "costs never change". It means costs are forecastable and controlled.
- Confusing predictability with reliability.
Exam tips
- "Forecast costs" / "budget" / "consistent performance" = predictability.
- Remember the two types, performance predictability and cost predictability.
Five quick revision questions
-
1.What are the two kinds of predictability in the cloud?Show
Performance predictability and cost predictability.
-
2.Which tool estimates Azure costs before you deploy?Show
The Azure pricing calculator.
-
3.Which tool tracks actual spend and sends budget alerts?Show
Microsoft Cost Management.
-
4.Name a feature that improves performance predictability.Show
Autoscaling (also load balancing, high availability).
-
5.Which Microsoft framework gives best-practice guidance across reliability, security, cost, operations and performance?Show
The Azure Well-Architected Framework.
Official references
Finished this lesson? Tick it off. Your progress is saved in this browser.
Next up: Security in the Cloud