MSDEVBUILD / azure

Reliability

Users Region A (primary) Region B (copy) data replicated⚡Running normally in region ADisaster in A, failed over to region B ✓
Disaster in one region? The app recovers in another region, because the data was copied there.

😟 THE PROBLEM

A flood knocks out the region where your booking system runs.

😊 THE SOLUTION

Keep a copy in another region and fail over to it.

  • A whole region goes down✓ Fail over to a second region
  • Data is deleted or corrupted✓ Restore from Azure Backup
  • Hoping the DR plan works✓ Test failover regularly
🛠️ Solved with: Region pairs · Azure Site Recovery · Backup
Try it yourself in the Azure simulator No Azure account needed. Storage accounts and redundancy 🗄️ Try it ❯
Module 1: Cloud Concepts ⏱ 8 min read Updated 11 Nov 2026

Quick answer

Reliability is the ability of a system to recover from failures and continue to function correctly. The cloud improves reliability because its decentralised design (many regions and availability zones around the world) lets you deploy resources in multiple places, so if one location has a problem, another can take over, sometimes automatically.

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

A flood knocks out an entire city's power for two days. Does your hospital booking system still work?

If it runs in one server room in that city, no. Patients cannot book, and doctors cannot see schedules.

If it is designed to recover, with copies of the data and the app ready in another city, it switches over and keeps running. That ability to bounce back is reliability.

Explain it like I’m 10

The technical explanation

Reliability is the ability of a workload to recover from failures and continue to function as expected. The cloud’s decentralised design, with dozens of regions worldwide, most with multiple availability zones, gives you building blocks to survive failures at every scale:

  1. 1 Component

    Instance crashes → load balancer routes to healthy instances.

  2. 2 Datacenter

    Zone failure → zone-redundant services continue in other zones.

  3. 3 Region

    Regional outage → fail over to a second region (geo-replication, Site Recovery).

  4. 4 Data

    Corruption or deletion → restore from backups (Azure Backup, point-in-time restore).

Reliability at every scale

Reliability vs high availability

High availability

  • Focus: maximum uptime
  • Measured with SLA percentages
  • Achieved with redundancy (no single point of failure)
  • Question: "Is it up right now?"

Reliability

  • Focus: recover and keep working correctly
  • Measured with RTO, RPO, failure rates
  • Achieved with redundancy plus recovery: backup, failover, DR
  • Question: "When something breaks, do we come back?"
Two related but different benefits

Azure features that support reliability

FeatureProtects against
Availability zones and zone-redundant servicesDatacenter failure
Region pairs and geo-redundant storage (GRS/GZRS)Regional disaster
Azure BackupData loss, corruption, ransomware
Azure Site RecoveryVM and server outages (replicate and fail over to another region)
Azure SQL Database failover groupsDatabase regional outage
Azure Front Door / Traffic ManagerRoute users away from an unhealthy region
Architect level Reliability engineering in practice

The Reliability pillar of the Azure Well-Architected Framework recommends:

  • Define targets with the business for each flow: availability, RTO and RPO. Not every flow needs the same.
  • Failure mode analysis: list what can fail and how each failure is detected and mitigated.
  • Self-healing: retries with exponential back-off, circuit breakers, health probes, automatic instance replacement.
  • Test: chaos experiments with Azure Chaos Studio, DR drills, backup restore tests.
  • Observe: health models in Azure Monitor that reflect user experience, not just CPU.

A useful mental model: you design for high availability, but you prove reliability by recovering under realistic failure.

Real-world business scenario

Healthcare

A national healthcare appointments service

The problem
A single-region deployment meant a regional incident could stop citizens booking appointments for hours, with possible data loss.
What they used
Zone-redundant App Service and Azure SQL Database in the primary region, auto-failover group to a second region, Azure Front Door for routing, Azure Backup for long-term retention, quarterly DR drills.
Why that choice
Zones handle datacenter failures automatically; the secondary region and failover group meet the RTO of one hour and RPO of minutes for regional disasters.
The result
A real zone incident later caused no downtime, and DR drills keep the regional failover runbook proven.

When to use it and when not to

✓ Use it when…

  • Systems where outages or data loss harm customers, revenue or safety.
  • Regulated workloads that require documented, tested disaster recovery.
  • Any production system. At minimum, tested backups.

✕ Think twice when…

  • Building multi-region active-active for low-impact internal tools. The cost and complexity are not justified.
  • Designing DR you never test.

↔ Alternatives to consider

  • **Backup-and-restore only** for low-criticality systems (cheapest, slowest recovery).
  • **Pilot light / warm standby** to balance cost and recovery time.
Ready for more?The full lesson adds the technical explanation, when to use it, interview questions and revision notes.

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 reliability mean in the cloud?

Model answer

Reliability means a system can recover from failures and keep working. Azure helps because it has regions and availability zones all over the world, so I can run copies of my app and data in more than one place and fail over if one has a problem.

Interviewer follows up

Is reliability the same as high availability?

You

They are related but not the same. High availability is about maximising uptime. Reliability is broader. It is about the system recovering from failures and working correctly over time, including recovering data and restoring service after a disaster.

Intermediate What are RTO and RPO, and why do they matter?

Model answer

RTO is how quickly service must be restored after a failure; RPO is how much data loss is acceptable, measured in time. They drive design and cost. An RPO of zero needs synchronous replication; an RTO of minutes needs a warm or active standby. Backups alone give longer RTO and RPO but cost far less.

Experienced developer How would you validate that a system is actually reliable rather than just designed to be?

Model answer

Test failure on purpose. Run regular failover drills, restore backups into a clean environment, and use fault injection with Azure Chaos Studio to kill instances, add latency or simulate a zone outage. Observe with health models and alerts. Document runbooks and automate failover where possible. A DR plan that has never been tested is a hope, not a plan.

Scenario A hospital appointments system must recover within one hour after a regional outage with at most five minutes of data loss. What would you suggest?

Model answer

RTO of one hour and RPO of five minutes. Replicate the database to a second region with asynchronous geo-replication (for example Azure SQL failover groups), keep the app deployable in the secondary region via infrastructure as code (or a warm standby), use Azure Site Recovery for any VMs, put Azure Front Door in front for traffic switching, and test the failover regularly.

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.

Question 1

Question 1 of 4

Which cloud benefit refers to the ability of a system to recover from failures and continue to function?

Question 2

Question 2 of 4

How does the cloud's decentralised design improve reliability?

Question 3

Question 3 of 4

Which Azure service replicates on-premises or Azure VMs to another location so they can fail over during a disaster?

Question 4

Question 4 of 4

A business states it can tolerate losing at most 15 minutes of data after a disaster. What is this requirement called?

Quick revision

Key points

  • Reliability = ability to recover from failures and keep functioning.
  • The cloud's decentralised design (regions, zones) makes reliable architectures easier.
  • Key tools include availability zones, region pairs, geo-redundant storage, Azure Backup and Azure Site Recovery.
  • RTO = how fast you recover; RPO = how much data you can lose.
  • Reliability must be tested (failover drills, restore tests, chaos experiments).

Important terminology

Reliability
The ability of a system to recover from failures and keep functioning correctly.
Disaster recovery (DR)
The plans and tooling to restore service after a major incident, such as a regional outage.
RTO
Recovery Time Objective. The maximum acceptable time to restore service after a failure.
RPO
Recovery Point Objective. The maximum acceptable amount of data loss, measured in time.
Failover
Switching to a standby component or location when the primary fails.

Common mistakes

  • Treating backups as a disaster recovery plan without ever testing restores.
  • Confusing reliability (recover and keep working) with predictability (consistent performance and cost).

Exam tips

  • "Recover from failures" / "continue to function" / "decentralised design" = reliability.
  • "Maximum uptime" / "SLA percentage" = high availability.

Five quick revision questions

  1. 1.What does reliability allow a system to do?Show

    Recover from failures and continue to function.

  2. 2.What does RTO stand for?Show

    Recovery Time Objective, the maximum time to restore service.

  3. 3.What does RPO stand for?Show

    Recovery Point Objective, the maximum acceptable data loss measured in time.

  4. 4.Which Azure service replicates VMs to another region for disaster recovery?Show

    Azure Site Recovery.

  5. 5.Why does the cloud's global footprint help reliability?Show

    You can deploy in multiple regions and zones, so a failure in one place does not stop the service.

Official references

Make it stick: play a quick gameSort It, Match the Pairs, Lightning Round and Who Am I? Earn XP and badges. Play ❯

Finished this lesson? Tick it off. Your progress is saved in this browser.

Next up: Predictability