AZ-900 Describe cloud concepts Practice Question
A company wants to be able to increase and decrease resources automatically based on demand without manual intervention. Which cloud characteristic does this describe?
⚠ Common exam trap
Many exam-takers confuse 'on-demand self-service' (manual provisioning without provider interaction) with 'automatic scaling,' but the question explicitly requires 'without manual intervention,' which only rapid elasticity satisfies.
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
✓
Rapid elasticity
Rapid elasticity is the cloud characteristic that enables resources to be automatically and dynamically scaled out (increased) or scaled in (decreased) in response to real-time demand, without requiring manual intervention. This is typically implemented through autoscaling policies that monitor metrics like CPU utilization or request count and trigger provisioning or de-provisioning of virtual machines or containers via APIs. The key differentiator is that scaling happens automatically and often in near real-time, matching the elasticity definition in NIST SP 800-145.
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 is incorrect because it describes the capability of a cloud platform to automatically monitor, control, and optimize resource usage through metering, enabling pay-per-use billing and usage transparency. It is about analyzing and reporting consumption for cost allocation, not about automatically increasing or decreasing resources. The mechanism of metering tracks resources after they are provisioned, whereas elasticity directly alters the amount of provisioned resources.
When this WOULD be correct
A question asking which cloud characteristic enables pay-per-use billing or resource usage tracking would have measured service as the correct answer.
- ✗
Resource pooling
Why it's wrong here
Resource pooling is incorrect because it refers to the multi-tenant model where a provider's compute, storage, and network resources are aggregated to serve multiple customers, with physical and virtual resources dynamically assigned and reassigned according to consumer demand. While there is some dynamic assignment, the defining characteristic is shared infrastructure, not scaling based on workload. Pooling explains how resources are commonly hosted, but it does not address the automatic increase and decrease described in the question.
When this WOULD be correct
A question that asks: 'Which cloud characteristic describes the provider's ability to serve multiple customers using the same physical infrastructure, with resources dynamically assigned?' would have resource pooling as the correct answer.
- ✓
Rapid elasticity
Why this is correct
Rapid elasticity is the cloud characteristic that allows resources to be automatically and dynamically scaled outward and inward to match fluctuating workload demand. From the consumer's perspective, this capability appears unlimited, as they can provision or de-provision resources instantly without manual intervention. This is the correct answer because the question explicitly describes the ability to increase and decrease resources automatically, which is the definition of elasticity.
- ✗
On-demand self-service
Why it's wrong here
On-demand self-service is incorrect because it refers to a user's ability to provision computing capabilities—such as virtual machines or storage—unilaterally, without requiring human interaction with the service provider. This is a user-initiated action, whereas automatic scaling happens in response to demand metrics, not at the user's direct request. The focus here is on eliminating manual procurement delays, not on dynamic capacity adjustment.
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.
✓Rapid elasticityCorrect answer▾
Why this is correct
Rapid elasticity is the cloud characteristic that allows resources to be automatically and dynamically scaled outward and inward to match fluctuating workload demand. From the consumer's perspective, this capability appears unlimited, as they can provision or de-provision resources instantly without manual intervention. This is the correct answer because the question explicitly describes the ability to increase and decrease resources automatically, which is the definition of elasticity.
✗Measured serviceWrong answer — click to see why▾
Why this is wrong here
Measured service refers to monitoring and reporting resource usage for billing, not automatically adjusting resources based on demand.
★ When this WOULD be the correct answer
A question asking which cloud characteristic enables pay-per-use billing or resource usage tracking would have measured service as the correct answer.
Why candidates choose this
Candidates may confuse 'measured' with 'metered' scaling, or think that measuring usage implies automatic adjustment of resources.
✗Resource poolingWrong answer — click to see why▾
Why this is wrong here
Resource pooling refers to the provider's computing resources being pooled to serve multiple customers, with physical and virtual resources dynamically assigned and reassigned according to demand. It does not describe the automatic scaling of resources based on demand, which is the key characteristic of rapid elasticity.
★ When this WOULD be the correct answer
A question that asks: 'Which cloud characteristic describes the provider's ability to serve multiple customers using the same physical infrastructure, with resources dynamically assigned?' would have resource pooling as the correct answer.
Why candidates choose this
Candidates may confuse resource pooling with elasticity because both involve dynamic allocation, but resource pooling is about multi-tenancy and shared infrastructure, not automatic scaling based on demand.
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
Learn chapter
What is Cloud Computing?
Key term
Elasticity
Elasticity is the ability of a cloud system to automatically add or remove computing resources (like servers, storage, or bandwidth) in response to real-time changes in demand.
Key term
Trigger
In Azure data services, a trigger is a predefined automatic action that initiates a process when a specific event occurs, such as data arriving or a schedule being met.
About these practice questions
This AZ-900 question is part of Courseiva's 981-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
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.