Cloud Elasticity vs Scalability: Which One Automatically Scales Resources?
A company hosts a web application on a public cloud IaaS platform. During a promotional event, traffic spikes to five times the normal volume. The cloud platform automatically provisions additional virtual machines to handle the load and then deprovisions them when traffic returns to normal. The IT team does not need to perform any manual intervention. Which essential cloud characteristic does this scenario BEST demonstrate?
Quick Answer
Cloud computing has a set of essential characteristics, and this question is testing whether you can distinguish elasticity from related but narrower concepts like scalability or on-demand self-service. Elasticity specifically describes a system's ability to automatically expand capacity when demand increases and automatically shrink it back down when demand falls, all without a human approving or triggering either action. In this scenario, the platform adds virtual machines during the traffic spike and removes them once traffic returns to normal, entirely on its own, which is the complete elasticity cycle rather than just the ability to scale in one direction. Plain scalability describes a system's capacity to grow to meet demand, but it does not necessarily include the automatic contraction back down or the complete absence of manual steps; a system could be scalable while still requiring an administrator to provision additional resources by hand. Because this scenario explicitly states that no manual intervention is needed for either the addition or removal of virtual machines, and both actions happen automatically in response to traffic, elasticity is the more precise and complete answer. When a scenario describes resources both growing and shrinking automatically to track demand, without anyone approving the changes, that two-directional automatic behavior is the signal to choose elasticity.
⚠ Common exam trap
A common mix-up: candidates confuse scalability with elasticity, assuming any scaling is elasticity, but the key differentiator is the automatic bidirectional scaling (both up and down) without manual intervention, which is explicitly tested in this question.
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
✓
Elasticity
The scenario describes automatic provisioning and deprovisioning of virtual machines in response to fluctuating demand, which is the defining characteristic of elasticity in cloud computing. Elasticity specifically refers to the ability to dynamically scale resources up and down automatically, often in near real-time, to match workload changes without manual intervention. This goes beyond mere scalability by including the automatic removal of resources when they are no longer needed, which is exactly what the cloud platform does during the promotional event.
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 this is correct
Elasticity automatically scales compute resources out during demand spikes and back in afterwards, with no manual intervention. This matches the stem's automatic provisioning and deprovisioning of VMs as traffic rises fivefold and returns to normal.
- ✗
Scalability
Why it's wrong here
Scalability describes a system's capacity to grow, but the stem emphasises automatic provisioning and deprovisioning without manual intervention as load changes. That elasticity — rapid, demand-driven resource adjustment — is the characteristic demonstrated. Scalability alone would describe growth capacity, not the automatic, reversible response to spikes.
- ✗
High availability
Why it's wrong here
High availability keeps services accessible by eliminating single points of failure through redundancy across zones. The stem describes capacity automatically expanding and contracting with traffic, not surviving an outage. High availability would be correct if an instance or zone failed while the application remained reachable.
When this WOULD be correct
A question describes a system that remains operational despite the failure of one or more components, such as a web application hosted across multiple availability zones that automatically fails over if a zone goes down.
- ✗
Fault tolerance
Why it's wrong here
Fault tolerance is the ability to continue operating despite component failure, typically via redundancy and failover. Here no component fails; capacity expands and contracts with demand. Fault tolerance would be correct if a zone or instance failed and the application kept serving traffic uninterrupted.
When this WOULD be correct
A question describing a cloud application that automatically fails over to a standby instance in another availability zone when the primary instance crashes, ensuring continuous operation despite hardware or software failures. This would demonstrate fault tolerance.
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.
✓ElasticityCorrect answer▾
Why this is correct
Elasticity automatically scales compute resources out during demand spikes and back in afterwards, with no manual intervention. This matches the stem's automatic provisioning and deprovisioning of VMs as traffic rises fivefold and returns to normal.
✗High availabilityWrong answer — click to see why▾
Why this is wrong here
High availability focuses on minimizing downtime through redundancy and failover, not on automatically scaling resources up and down in response to demand changes.
★ When this WOULD be the correct answer
A question describes a system that remains operational despite the failure of one or more components, such as a web application hosted across multiple availability zones that automatically fails over if a zone goes down.
Why candidates choose this
Candidates may confuse automatic scaling with maintaining uptime, or think that handling increased traffic implies high availability, but the key here is dynamic resource adjustment, not fault tolerance.
✗Fault toleranceWrong answer — click to see why▾
Why this is wrong here
Fault tolerance refers to a system's ability to continue operating without interruption in the event of component failures, not to automatic scaling based on demand. The scenario describes dynamic provisioning and deprovisioning of VMs to handle traffic spikes, which is elasticity, not fault tolerance.
★ When this WOULD be the correct answer
A question describing a cloud application that automatically fails over to a standby instance in another availability zone when the primary instance crashes, ensuring continuous operation despite hardware or software failures. This would demonstrate fault tolerance.
Why candidates choose this
Candidates may confuse fault tolerance with the ability to handle increased load, or they might think that automatically adding VMs is a form of tolerating traffic spikes, but fault tolerance specifically addresses component failures, not load variations.
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
Learn chapter
Thermal Paste Application
Key term
Anything As A Service
A model where you rent any IT resource or service over the internet instead of owning it.
Key term
Software as a Service
Software as a Service (SaaS) is a cloud computing model where users access software applications over the internet on a subscription basis, without installing or maintaining the software locally.
About these practice questions
Courseiva writes every 220-1101 question from scratch — 896 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
6 more ways this is tested on 220-1101
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company runs its customer-facing web application on a public cloud platform. The application experiences dramatic traffic spikes during promotional events. The cloud platform automatically increases the number of virtual server instances during high demand and reduces them when demand subsides. The company only pays for the compute resources consumed during the billing cycle. Which cloud computing characteristic does this configuration BEST exemplify?
hard- A.On-demand self-service
- ✓ B.Rapid elasticity
- C.Resource pooling
- D.Measured service
Why B: The scenario describes the cloud platform automatically scaling virtual server instances up and down in response to traffic spikes, which is the defining characteristic of rapid elasticity. This allows the company to provision and release compute resources dynamically, paying only for what is used, which is a core benefit of cloud computing.
Variation 2. A company hosts a web application on a virtual machine in a public cloud. During lunch hours, traffic increases dramatically, and the cloud provider automatically provisions additional compute resources to handle the load. When traffic subsides, the extra resources are automatically released. Which essential characteristic of cloud computing does this scenario BEST describe?
easy- A.Resource pooling
- B.Measured service
- ✓ C.Rapid elasticity
- D.On-demand self-service
Why C: The scenario describes automatic scaling up and down of compute resources in response to demand, which is the defining behavior of rapid elasticity. This characteristic allows cloud resources to be provisioned and released quickly, often automatically, to match workload fluctuations. The key here is the dynamic, automated scaling triggered by traffic changes, not just the ability to request resources manually.
Variation 3. A company runs a web application on a virtual machine in a public cloud. During a marketing campaign, the application experiences a sudden spike in traffic. The cloud platform automatically adds more virtual server instances to handle the load and then removes them when traffic subsides. Which cloud computing characteristic does this represent?
medium- A.Resource pooling
- B.Measured service
- ✓ C.Rapid elasticity
- D.On-demand self-service
Why C: Rapid elasticity is the cloud characteristic that enables resources to scale out (add instances) and scale in (remove instances) automatically in response to demand spikes, such as during a marketing campaign. This is distinct from resource pooling, which refers to multi-tenant sharing of physical infrastructure, not dynamic scaling.
Variation 4. A company uses a public cloud IaaS provider to host a web application. The application experiences occasional spikes in traffic. The cloud provider offers a service that automatically adds or removes virtual machine instances based on CPU utilization. This is an example of which cloud characteristic?
medium- ✓ A.Rapid elasticity
- B.Measured service
- C.On-demand self-service
- D.Resource pooling
Why A: The scenario describes a cloud service that automatically scales virtual machine instances up or down in response to CPU utilization spikes. This ability to provision and release resources quickly and automatically to match demand is the defining characteristic of rapid elasticity, which allows resources to appear unlimited to the consumer and scale elastically based on workload.
Variation 5. A company runs a web application on a virtual machine in a public cloud IaaS environment. The application experiences unpredictable traffic spikes lasting 10–15 minutes. The company wants to automatically add more VM instances during spikes and remove them when traffic subsides, paying only for the resources used. Which cloud characteristic should the administrator configure to meet this requirement?
medium- ✓ A.Elasticity
- B.High availability
- C.Fault tolerance
- D.Load balancing
Why A: Elasticity is the cloud characteristic that automatically scales resources up or down based on demand, enabling the company to add VM instances during traffic spikes and remove them when traffic subsides, paying only for what is used. This matches the requirement for handling unpredictable, short-duration spikes (10–15 minutes) in an IaaS environment.
Variation 6. A company runs a web application on a virtual machine (VM) in a public cloud IaaS environment. The application experiences unpredictable traffic spikes throughout the day, sometimes lasting 30 minutes. The company wants to ensure consistent performance during spikes while minimizing costs. The current single VM (4 vCPUs, 8 GB RAM) is sufficient for normal load but becomes slow during spikes. Which cloud characteristic should the administrator implement to address this requirement?
hard- ✓ A.Elasticity
- B.High availability
- C.Load balancing
- D.Fault tolerance
Why A: Elasticity is the correct answer because it allows the cloud infrastructure to automatically scale resources up during traffic spikes and scale down when demand decreases, ensuring consistent performance while minimizing costs. In an IaaS environment, this is typically achieved through auto-scaling groups that add or remove VM instances based on metrics like CPU utilization or request count, matching the unpredictable, short-duration spikes described.
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.