Courseiva
Describe cloud conceptsmediumMultiple ChoiceObjective-mapped

AZ-900 Describe cloud concepts Practice Question

A startup expects rapid growth and wants its cloud infrastructure to automatically add or remove compute resources based on real-time demand without manual intervention. Which cloud characteristic does this describe?

⚠ Common exam trap

Candidates often confuse elasticity with high availability, mistakenly thinking that automatically recovering from failures (HA) is the same as automatically adjusting capacity to meet demand (elasticity).

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

Elasticity

Elasticity is the cloud characteristic that enables automatic scaling of compute resources up or down in response to real-time demand. This startup's requirement to add or remove resources without manual intervention directly matches the definition of elasticity, which is a core benefit of cloud computing.

Answer analysis

Option-by-option breakdown

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

  • High availability

    Why it's wrong here

    High availability is incorrect because it ensures the service remains accessible and operational for a high percentage of uptime, typically through redundant infrastructure and failover mechanisms. It does not automatically alter the number of resources to match fluctuating demand; it only guarantees that the same fixed capacity is continuously reachable. Rapid growth requiring additional compute or storage would not be satisfied by high availability alone.

    When this WOULD be correct

    A question asking about a cloud system that remains operational with minimal downtime, even if individual components fail, would have high availability as the correct answer.

  • Elasticity

    Why this is correct

    Elasticity is the correct answer because a startup expecting rapid growth needs a cloud model that automatically provisions and de-provisions compute resources to match real-time demand. Azure Virtual Machine Scale Sets and Autoscale capabilities add or remove instances based on metrics like CPU load or queue length, ensuring the application can handle spikes without manual intervention and avoid over-provisioning during lulls. This dynamic scaling directly addresses unpredictable growth patterns, making elasticity the foundational characteristic for this scenario.

  • Fault tolerance

    Why it's wrong here

    Fault tolerance is incorrect because it focuses on preserving system functionality when individual components fail, using redundancy such as multiple availability zones or load-balanced replicas. While critical for reliability, fault tolerance does not involve adjusting capacity in response to workload changes; it merely keeps the existing resources operational despite failures. A startup needing to scale up quickly would still face capacity limits even if the system is fault-tolerant.

    When this WOULD be correct

    A question asking about a system's ability to continue functioning despite hardware or software failures, such as 'Which cloud characteristic ensures service continuity when a server fails?' would make fault tolerance correct.

  • Disaster recovery

    Why it's wrong here

    Disaster recovery is incorrect because it is a reactive process for restoring services and data after a major outage or catastrophic event, using backup sites and recovery plans. It is not concerned with real-time scaling during normal operations and typically involves predefined RTO/RPO targets that take minutes or hours to execute. The need for immediate, automatic growth is unrelated to disaster recovery's post-disruption restoration focus.

    When this WOULD be correct

    A question asking about the ability to recover from a major outage or natural disaster, such as 'Which cloud characteristic ensures business continuity by replicating data and workloads across geographically separated regions?' would make disaster recovery the correct answer.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-900 exam frequently reuses these exact scenarios with slightly different constraints.

ElasticityCorrect answer

Why this is correct

Elasticity is the correct answer because a startup expecting rapid growth needs a cloud model that automatically provisions and de-provisions compute resources to match real-time demand. Azure Virtual Machine Scale Sets and Autoscale capabilities add or remove instances based on metrics like CPU load or queue length, ensuring the application can handle spikes without manual intervention and avoid over-provisioning during lulls. This dynamic scaling directly addresses unpredictable growth patterns, making elasticity the foundational characteristic for this scenario.

High availabilityWrong answer — click to see why

Why this is wrong here

High availability ensures that applications remain accessible despite failures, but it does not automatically adjust resource capacity based on demand; it focuses on uptime, not scaling.

★ When this WOULD be the correct answer

A question asking about a cloud system that remains operational with minimal downtime, even if individual components fail, would have high availability as the correct answer.

Why candidates choose this

Candidates may confuse high availability with elasticity because both involve maintaining performance, but they mistakenly think availability includes scaling to meet demand.

Fault toleranceWrong answer — click to see why

Why this is wrong here

Fault tolerance focuses on maintaining system operation during component failures, not on dynamically adjusting resources based on demand.

★ When this WOULD be the correct answer

A question asking about a system's ability to continue functioning despite hardware or software failures, such as 'Which cloud characteristic ensures service continuity when a server fails?' would make fault tolerance correct.

Why candidates choose this

Candidates may confuse fault tolerance with elasticity because both involve handling changes, but fault tolerance is about failure resilience, not scaling to meet demand.

Disaster recoveryWrong answer — click to see why

Why this is wrong here

Disaster recovery focuses on restoring IT infrastructure and data after a catastrophic failure, not on automatically scaling resources based on real-time demand.

★ When this WOULD be the correct answer

A question asking about the ability to recover from a major outage or natural disaster, such as 'Which cloud characteristic ensures business continuity by replicating data and workloads across geographically separated regions?' would make disaster recovery the correct answer.

Why candidates choose this

Candidates may confuse disaster recovery with elasticity because both involve responding to changes, but disaster recovery is reactive to failures, not proactive to demand fluctuations.

Analysis generated from the official AZ-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

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

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.