AZ-900 Describe cloud concepts Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Elasticity

  Why it's wrong here

  Elasticity is incorrect because it refers to the ability of a cloud system to automatically add or remove compute, storage, or networking resources in response to fluctuating demand, typically within a single provider's autoscaling service. While this is a key cloud characteristic, it operates only at the infrastructure provisioning layer and does not address moving application code, data, or configuration between Azure, AWS, or GCP. Thus, elasticity cannot reduce dependence on a single cloud vendor.

  When this WOULD be correct

  A company expects sudden spikes in traffic and needs to automatically add or remove virtual machines to handle load without manual intervention. Which cloud characteristic is most essential?

• ✗

  Scalability

  Why it's wrong here

  Scalability is incorrect here because it is the capability of a workload to handle increasing load by adding resources, either by scaling up (larger VMs or higher service tiers) or scaling out (more instances), usually through Azure autoscaling or service plans. This concept is about performance growth and capacity management, not about the architecture needed to migrate code and data between cloud environments. A scalable system can still be tightly coupled to Azure-specific services, so scalability alone does not address dependency on a single provider.

  When this WOULD be correct

  A company expects rapid growth in user demand and needs to automatically adjust resources to maintain performance. The question would ask: 'Which cloud characteristic allows a system to handle varying workloads by scaling resources up or down?'

• ✓

  Portability

  Why this is correct

  Portability is correct because it is the design property that allows a workload, along with its data and configurations, to be moved between cloud providers with minimal modifications. In Azure, this is achieved through open standards, containers (e.g., Docker images on Azure Kubernetes Service), infrastructure as code (e.g., Terraform), and abstraction services like Azure Arc that manage resources across clouds. By enabling redeployment to a different provider, portability directly prevents lock-in and supports a multi-cloud strategy.

• ✗

  Fault tolerance

  Why it's wrong here

  Fault tolerance is incorrect in this context because it is a resilience pattern that keeps a system operational when a component inside the same cloud environment fails, often through redundancy such as availability zones or multiple instance replicas. It addresses failure within a single provider or region, not the strategic movement of workloads between distinct cloud vendors. While fault tolerance may improve uptime, it does not by itself allow you to shift a dependency to another provider, so it does not solve single-vendor dependency.

  When this WOULD be correct

  A question asking: 'Which cloud characteristic ensures an application remains available despite hardware or software failures?' would make fault tolerance the correct answer, as it focuses on redundancy and failover mechanisms.

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.

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?”

Go deeper

Related to this question