Benefits of Cloud Services

AZ-900 AZ-900 · Describe cloud concepts

By Abu Anns · Last updated 20 November 2026Exam version: AZ-900 (skills measured as of July 20, 2026)

Why move to the cloud at all?

The exam's benefits section answers a business question: what does an organisation actually gain from cloud services? Microsoft's objectives name seven benefits — high availability, scalability, reliability, predictability, security, governance, and manageability — and the exam tests them through scenarios. The skill is matching a situation to the right benefit word, and the traps are the near-synonyms: scalability versus elasticity, high availability versus reliability versus disaster recovery. Learn the distinctions, not just the definitions.

High availability and scalability

High availability means a service stays up and reachable. It is measured as uptime, usually expressed as a percentage in a service level agreement (SLA) — 99.9% uptime allows about 43 minutes of downtime a month, while 99.99% allows about 4 minutes. Availability comes from redundancy: running more than one copy of a workload so that if one fails, another takes over. In Azure, availability sets and availability zones are the mechanisms (covered in the architecture guide), but the benefit itself is simple: the service keeps working when a component fails.

Scalability means the ability to increase or decrease resources in response to demand. There are two directions. Vertical scaling (scaling up) means making a single resource bigger — a larger virtual machine with more CPU and memory. Horizontal scaling (scaling out) means adding more instances — going from two web servers to ten. Cloud platforms make both easy, but horizontal scaling is the cloud's signature move: add instances when demand rises, remove them when it falls.

Closely related is elasticity: the ability to scale automatically as demand changes. Scalability is the ability to change size; elasticity is doing it dynamically, without manual intervention. A system that an administrator scales up by hand on Monday morning is scalable. A system that adds instances itself when CPU passes 70% and removes them when it drops is elastic. The exam tests this distinction directly, often with a scenario about traffic that rises and falls during the day: the benefit being described is elasticity, not just scalability.

Reliability and predictability

Reliability is the ability of a system to recover from failures and keep operating. It overlaps with availability, but the emphasis differs: availability is about staying up, reliability is about recovering well. A reliable system detects a failed component, routes around it, and restores service — ideally before users notice. Azure supports reliability through redundancy across zones and regions, health monitoring, and automated recovery. Disaster recovery is the bigger sibling: the ability to restore service after a large-scale failure, such as a whole datacenter or region going down, usually by failing over to another region. Availability handles a failed server; disaster recovery handles a failed datacenter.

Predictability has two faces, and the exam tests both. Performance predictability means a workload behaves the same way every time — autoscaling and load balancing keep response times steady even as demand changes. Cost predictability means spending is knowable in advance: the Azure pricing calculator estimates costs before deployment, and Cost Management tracks actual spending against budgets. A question about knowing what a deployment will cost before building it is a cost-predictability question; a question about response times staying steady under load is a performance-predictability question.

Security, governance, and manageability

Security in the cloud benefits from the provider's scale: Microsoft operates datacenters with physical security, dedicated security teams, and threat intelligence that no single customer could afford to replicate. Cloud services add platform features — encryption, identity controls, network isolation, DDoS protection — that are available to every customer. The shared-responsibility point still applies: the provider secures the platform, and the customer secures its data and access. The benefit is that the platform side is done by specialists at a scale the customer could not match.

Governance means the ability to set and enforce rules across an environment: who can create resources, which regions they can use, which configurations are allowed, and whether everything complies. In Azure this is the job of management groups, Azure Policy, and resource locks (covered in the governance guide). The cloud benefit is that governance can be applied centrally and automatically, rather than relying on people following a written policy. Manageability is the matching operational benefit: managing an entire environment from one place, with centralised tools, automation, and templates, instead of logging into servers one at a time. The Azure portal, Cloud Shell, and infrastructure as code are the manageability tools.

Two more benefits the exam implies

Two further benefits appear across the objectives even though they are not in the benefits list itself. Agility is speed: a team can provision a test environment in minutes instead of waiting weeks for hardware procurement. Geo-distribution is reach: deploying an application in regions close to its users reduces latency and improves the experience — a customer in Sydney gets fast responses from an Australia-based region rather than waiting on traffic from Europe. Geo-distribution also underpins disaster recovery, since a second region can take over if the first fails.

Worked example: the seasonal retailer

An online retailer does 40% of its annual sales in December. In its old datacenter, it bought servers sized for December — which sat mostly idle for eleven months — and a single hardware failure during the Christmas rush could take the site down. Moving to Azure changes every benefit at once. Elasticity lets the site scale out automatically as December traffic rises and scale back in January, so the retailer pays for peak capacity only during the peak. High availability from running across availability zones means a single datacenter failure no longer takes the site down. Disaster recovery to a paired region covers the worst case. Cost predictability from the pricing calculator tells the retailer what December will cost before it happens. And manageability means the small IT team runs the whole environment from the portal instead of racking servers. One migration, seven benefits — and exam questions are usually built exactly this way, with one scenario testing whether you can name the benefit being described.

Telling the lookalikes apart

If the scenario describes...The benefit is...
Adding more instances to handle more usersScalability (horizontal / scale out)
Resources adjusting automatically as demand rises and fallsElasticity
The service staying up when a component failsHigh availability
The system recovering quickly from a failureReliability
Restoring service after a datacenter or region failsDisaster recovery
Knowing the cost before deployingCost predictability
Response times staying steady under varying loadPerformance predictability
Enforcing rules and auditing compliance centrallyGovernance
Running everything from one central place with automationManageability
Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A web application slows down whenever traffic increases. The team fixes it by adding more identical web servers behind a load balancer whenever demand rises. Which benefit of cloud services is the team using?

Report an error

Q2.An e-commerce site automatically adds servers when traffic spikes during a sale and removes them when traffic falls back, with no administrator involvement. Which term best describes this behaviour?

Report an error

Q3.A company's application keeps running when one of its servers fails, because a second server immediately takes over. Users never notice the failure. Which benefit does this describe?

Report an error

Q4.A company's primary datacenter is hit by a flood. Within an hour, its systems are running again from a secondary site in another region, with only minutes of data loss. Which capability made this possible?

Report an error

Q5.Before deploying a new application, a finance team wants to know what it will cost to run each month. They use the Azure pricing calculator to produce an estimate. Which cloud benefit are they using?

Report an error

Q6.A company has customers in Europe, Asia, and North America. It deploys its application in Azure regions on each continent so every customer connects to a nearby copy. Which benefit is the company gaining?

Report an error

Q7.A system detects that one of its database replicas has failed, automatically promotes a healthy replica, and continues serving requests with only a brief interruption. Which benefit does this best illustrate?

Report an error

Q8.An IT team manages all of its Azure resources — virtual machines, storage, networking, and databases — from a single web portal, and deploys new environments from templates instead of configuring each server by hand. Which benefit does this describe?

Report an error