220-1101 Virtualization and Cloud Computing Practice Question
A company hosts a web application on a public cloud IaaS platform. The application experiences unpredictable traffic spikes. The cloud platform automatically adds virtual machines when CPU usage exceeds 80% and removes them when usage drops below 30%. The IT team does not need to manually approve the additions or removals. Which essential cloud characteristic does this BEST describe?
⚠ Common exam trap
Watch out — candidates often confuse on-demand self-service (user-initiated provisioning) with automatic scaling, but rapid elasticity specifically describes the system's ability to automatically and dynamically adjust resources without manual approval.
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
The scenario describes the cloud platform automatically adding and removing virtual machines based on CPU utilization thresholds (80% and 30%) without manual intervention. This is the defining behavior of rapid elasticity, which allows resources to scale out and in automatically to match demand. Unlike on-demand self-service, which focuses on user-initiated provisioning, rapid elasticity emphasizes the system's ability to dynamically adjust capacity without requiring human action.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
On-demand self-service
Why it's wrong here
On-demand self-service lets consumers provision capabilities automatically without human interaction with each provider, but here the platform itself scales capacity from CPU thresholds. That automated elasticity is the characteristic described; on-demand self-service concerns the consumer's unilateral provisioning, not provider-initiated scaling.
When this WOULD be correct
A scenario where a user can provision a virtual machine through a web portal without contacting IT support would make on-demand self-service the correct answer. For example: 'A developer creates a new server instance via the cloud provider's API without any manual approval.'
- ✓
Rapid elasticity
Why this is correct
Rapid elasticity is the cloud characteristic whereby resources scale automatically with demand, adding and removing virtual machines without manual intervention. The CPU thresholds and unapproved provisioning described in the stem are precisely this automated, demand-driven scaling behaviour.
- ✗
Resource pooling
Why it's wrong here
Resource pooling means providers serve multiple tenants from shared physical infrastructure, masking location. It does not scale capacity in response to load. Elasticity, triggered by the 80% and 30% CPU thresholds, is what adds and removes VMs here; pooling would answer a multi-tenancy question.
When this WOULD be correct
Resource pooling would be the correct answer if the question described how the cloud provider uses shared infrastructure (e.g., servers, storage) to serve multiple customers, where resources are assigned and reassigned on demand without the customer knowing the exact physical location.
- ✗
Measured service
Why it's wrong here
Measured service reports consumption for billing; it does not add or remove capacity. Elasticity, driven by CPU thresholds here, is the characteristic that provisions and deprovisions VMs automatically. Measured service would be the answer if the question asked how usage is metered and charged per unit consumed.
When this WOULD be correct
A company uses a cloud provider that charges based on the number of virtual machine hours consumed, with detailed usage reports for each department. The question asks which characteristic enables this pay-per-use billing model.
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 220-1101 exam frequently reuses these exact scenarios with slightly different constraints.
✓Rapid elasticityCorrect answer▾
Why this is correct
Rapid elasticity is the cloud characteristic whereby resources scale automatically with demand, adding and removing virtual machines without manual intervention. The CPU thresholds and unapproved provisioning described in the stem are precisely this automated, demand-driven scaling behaviour.
✗On-demand self-serviceWrong answer — click to see why▾
Why this is wrong here
On-demand self-service refers to a user provisioning resources without human interaction, but the question emphasizes automatic scaling based on CPU thresholds, which is rapid elasticity, not the ability to self-provision.
★ When this WOULD be the correct answer
A scenario where a user can provision a virtual machine through a web portal without contacting IT support would make on-demand self-service the correct answer. For example: 'A developer creates a new server instance via the cloud provider's API without any manual approval.'
Why candidates choose this
Candidates may confuse the automatic scaling (rapid elasticity) with the ability to self-service resources, as both involve automation and lack of manual intervention, but self-service is about initial provisioning, not dynamic scaling.
✗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 according to customer demand. This question describes automatic scaling of VMs based on load, which is rapid elasticity, not resource pooling.
★ When this WOULD be the correct answer
Resource pooling would be the correct answer if the question described how the cloud provider uses shared infrastructure (e.g., servers, storage) to serve multiple customers, where resources are assigned and reassigned on demand without the customer knowing the exact physical location.
Why candidates choose this
Candidates may confuse resource pooling with elasticity because both involve dynamic resource allocation, but resource pooling focuses on multi-tenancy and location independence, not automatic scaling based on demand.
✗Measured serviceWrong answer — click to see why▾
Why this is wrong here
Measured service refers to the metering and billing of cloud resource usage, not the automatic scaling of resources based on demand. The question describes automatic addition/removal of VMs, which is rapid elasticity, not measured service.
★ When this WOULD be the correct answer
A company uses a cloud provider that charges based on the number of virtual machine hours consumed, with detailed usage reports for each department. The question asks which characteristic enables this pay-per-use billing model.
Why candidates choose this
Candidates may confuse measured service with any automated cloud behavior, thinking that automatic scaling involves monitoring and thus measurement, but measured service specifically relates to usage tracking and billing.
Analysis generated from the official 220-1101blueprint 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
About these practice questions
One of 896 original 220-1101 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1101 practice question is part of Courseiva's free CompTIA 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 220-1101 exam.