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.

• ✗

  Measured service

  Why it's wrong here

  Measured service refers to the cloud provider's ability to meter usage—such as CPU hours, storage capacity, and network bandwidth—and then report that usage for billing and cost control under a pay-as-you-go model. This gives teams transparency and chargeback insight, but it is fundamentally a monitoring and accounting function, not a provisioning mechanism. The development team's problem is about avoiding the wait for manual approval to acquire resources, and measured service does nothing to remove that human step.

  When this WOULD be correct

  A question asking: 'Which cloud characteristic allows a company to track and optimize resource consumption for cost allocation?' would make measured service the correct answer, as it involves monitoring and controlling usage.

• ✓

  On-demand self-service

  Why this is correct

  On-demand self-service is the defining NIST characteristic that lets a cloud consumer unilaterally provision computing resources—such as Azure VMs, storage accounts, or database services—via the portal, CLI, PowerShell, or REST API, with no need for a human approval queue or provider intervention. In a migration scenario, developers can spin up the exact services they need at any moment, which directly satisfies the requirement to provision resources automatically without waiting on a technician.

• ✗

  Rapid elasticity

  Why it's wrong here

  Rapid elasticity focuses on the dynamic scaling of resources in response to fluctuating demand, automatically increasing or decreasing capacity outward and inward as workloads change. This is an operational capability that handles post-provisioning adjustments—like autoscaling an Azure App Service during a traffic burst—not the initial act of requesting and receiving a resource. Therefore, while elasticity improves agility over time, it cannot address the specified need for the development team to create resources on-demand without human interaction at the outset.

  When this WOULD be correct

  A question like 'A company experiences sudden spikes in traffic and needs its cloud resources to automatically increase and decrease capacity to handle the load. Which cloud characteristic addresses this?' would make rapid elasticity the correct answer.

• ✗

  Resource pooling

  Why it's wrong here

  Resource pooling describes the provider's shared, multi-tenant infrastructure, where physical and virtual resources are dynamically assigned to multiple customers while maintaining isolation through virtualization and logical separation. This architectural principle is what makes cloud economics efficient, but it does not empower the user to allocate anything unilaterally; a customer may be drawing from a pooled resource yet still require a manual ticket or an admin to act on that request. Thus, pooling is about the provider's internal model, not the user's ability to self-provision.

  When this WOULD be correct

  A question asking which cloud characteristic allows the provider to achieve economies of scale by serving multiple customers from shared infrastructure would make resource pooling 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?”