Courseiva
Describe cloud conceptsmediumMultiple ChoiceObjective-mapped

Fault Tolerance in Cloud Computing

What does the term 'fault tolerance' mean in cloud computing?

Quick Answer

The answer is the ability to continue operating despite component failures. This means a fault-tolerant system in cloud computing is designed to absorb hardware or software failures without any interruption to service, typically by deploying redundant components—such as multiple servers, network paths, or power supplies—so that if one element fails, another instantly takes over. On the Microsoft Azure Fundamentals AZ-900 exam, this concept tests your understanding of how Azure achieves resilience through features like Availability Zones and redundant infrastructure, and it is often contrasted with high availability, which allows for brief downtime. A common trap is confusing the two: remember that high availability aims for minimal downtime, while fault tolerance demands zero downtime even during a failure. A useful memory tip is to think of fault tolerance as a “no-break” system—like a car with a spare tire already spinning—so the ride never stops.

⚠ Common exam trap

Many exam-takers confuse 'fault tolerance' with 'high availability' or 'disaster recovery', but the key differentiator is that fault tolerance implies zero downtime and no data loss during a failure, whereas high availability may involve a brief interruption and disaster recovery involves a longer recovery time objective (RTO).

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

The ability to continue operating despite component failures

Fault tolerance is the ability of a system to continue operating without interruption when one or more of its components fail. In Azure, this is achieved through redundancy at multiple layers—such as using Availability Zones or redundant hardware—so that a failure in a single server, network path, or power supply does not bring down the entire workload. This is distinct from high availability, which focuses on minimizing downtime, whereas fault tolerance aims for zero downtime even during failures.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The ability to scale resources up and down automatically

    Why it's wrong here

    Automatic scaling is elasticity, not fault tolerance.

  • The ability to continue operating despite component failures

    Why this is correct

    Fault tolerance means the system remains functional even when individual components fail, through redundancy and failover.

  • The ability to recover data after accidental deletion

    Why it's wrong here

    Data recovery after deletion is backup/restore capability, not fault tolerance.

  • The ability to deploy applications across multiple regions

    Why it's wrong here

    Multi-region deployment supports both high availability and disaster recovery but is not the definition of fault tolerance.

About these practice questions

One of 981 original AZ-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on AZ-900

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. What is 'fault tolerance' in cloud computing?

easy
  • A.The ability to automatically scale resources during peak usage
  • B.The ability to continue operating correctly despite component failures
  • C.The ability to restore data after a major disaster
  • D.The ability to deploy applications in multiple geographic regions

Why B: Fault tolerance in cloud computing refers to a system's ability to continue operating correctly, without interruption, even when one or more of its components fail. This is achieved through redundancy—such as duplicate hardware, software, or data paths—so that if a component fails, another automatically takes over without any impact on the user. It is a core design principle for high-availability systems, ensuring zero downtime despite failures.

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.