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.

• ✗

  Rapid elasticity

  Why it's wrong here

  Incorrect. Rapid elasticity refers to the ability to quickly scale resources up or down based on demand. While provisioning a VM is related to scaling, the scenario specifically highlights the ability to provision resources automatically without human interaction, which is on-demand self-service.

  When this WOULD be correct

  A question describing a company's e-commerce site that automatically adds more virtual machines during peak shopping hours and removes them when traffic subsides, without manual intervention, would illustrate rapid elasticity.

• ✓

  On-demand self-service

  Why this is correct

  On-demand self-service is a core NIST cloud characteristic that lets a user provision computing capabilities—such as virtual machines, storage, or network resources—automatically through a portal or API, without requiring human interaction from the service provider. In the scenario, the user deploys a VM directly, and the provider's automated orchestration handles the request immediately, eliminating manual approval steps. This is fundamentally different from traditional on-premises procurement, where IT staff or vendor representatives must manually configure hardware.

• ✗

  Resource pooling

  Why it's wrong here

  Resource pooling is the cloud characteristic where the provider's compute, storage, and network resources are aggregated into a shared pool and dynamically assigned across multiple customers (multi-tenancy), with location independence at a high level. The scenario's focus is on the self-service provisioning action, not on how the underlying physical or virtual resources are shared or reassigned among tenants. Even if resource pooling occurs behind the scenes, it is not the defining characteristic demonstrated by a user simply creating a VM without human intervention.

  When this WOULD be correct

  A question that asks about the characteristic where a cloud provider's physical and virtual resources are dynamically assigned and reassigned among multiple customers based on demand, such as: 'Which cloud characteristic allows a provider to serve multiple customers from the same physical hardware?'

• ✗

  Measured service

  Why it's wrong here

  Measured service is the cloud characteristic that automatically meters and optimizes resource usage at an abstraction level appropriate to the service (e.g., CPU time, storage, bandwidth, active accounts), enabling pay-per-use billing and usage transparency. The scenario only describes the act of provisioning a VM; it says nothing about monitoring, metering, cost reporting, or usage-based billing that would occur after the resource is deployed. Therefore, measured service is not the characteristic being highlighted in this specific provisioning action.

  When this WOULD be correct

  A question describing how Azure automatically tracks and bills for each hour of VM usage, or how a company monitors resource consumption to optimize costs, would make measured service 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.

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