220-1101 Virtualization and Cloud Computing Practice Question
A company hosts its e-commerce website on a public cloud IaaS platform. During a flash sale, traffic spikes to 10 times the normal volume. The cloud platform automatically provisions additional virtual servers to handle the increased load and then deprovisions them after the sale ends, requiring no manual intervention. Which essential cloud characteristic does this scenario BEST demonstrate?
⚠ Common exam trap
Many candidates confuse rapid elasticity with load balancing, but load balancing only distributes traffic across existing resources, whereas elasticity actually changes the number of resources to match demand.
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 scaling virtual server resources up and down in response to demand spikes, with no manual intervention. This is the defining characteristic of rapid elasticity, which allows resources to be provisioned and released elastically, often automatically, to match workload fluctuations. The key is the dynamic scaling triggered by traffic changes, not the mere presence of redundancy or distribution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
High availability
Why it's wrong here
High availability (HA) is a design goal focused on maximizing uptime by eliminating single points of failure through redundant components, failover clustering, and automated health checks. When one server or service fails, an HA system automatically switches to a standby component to keep the application running, but the total capacity remains unchanged. HA ensures business continuity during failures, not the ability to dynamically grow or shrink resources in response to user demand or e-commerce sales events.
When this WOULD be correct
A company deploys its critical application across multiple availability zones with automatic failover. If one zone fails, traffic is instantly redirected to another zone without interruption. This scenario demonstrates high availability.
- ✗
Fault tolerance
Why it's wrong here
Fault tolerance is an even stricter resilience model in which the system continues to operate completely transparently, without any interruption, even when a hardware or software fault occurs, thanks to redundant, actively synchronized components. It is about masking failures from the user so that no downtime is perceived, whereas rapid elasticity is about adjusting resource allocation to match current workload levels. Fault tolerance does not inspect utilization metrics to spin up extra instances; it merely maintains the same level of service in the presence of faults.
When this WOULD be correct
An exam question describing a cloud system that automatically reroutes traffic to healthy instances when a server fails, ensuring continuous operation without manual intervention, would make fault tolerance the correct answer.
- ✓
Rapid elasticity
Why this is correct
Rapid elasticity is a core NIST cloud characteristic that enables a public IaaS platform to provision or release compute, storage, or network resources automatically and near-instantaneously in response to fluctuating demand. For an e-commerce site, this means scaling out additional virtual machines or containers during a traffic spike and scaling back down when the spike subsides. The key differentiator is that the capacity change itself is part of the cloud's native behavior, driven by consumption thresholds rather than manual intervention or fixed infrastructure.
- ✗
Load balancing
Why it's wrong here
Load balancing is a traffic-management technique that distributes incoming requests across a predetermined set of backend servers to optimize utilization and prevent any single server from becoming a bottleneck. It operates on the existing resource pool, routing requests based on health checks or algorithms like round-robin, but it does not alter the number of servers in that pool. While a load balancer might redirect traffic when one server is overwhelmed, it cannot add new servers to handle an overall surge in traffic—that would require an external scaling mechanism.
When this WOULD be correct
A question describing a system that evenly distributes incoming traffic across multiple servers to prevent any single server from being overwhelmed, without mentioning automatic scaling, would make load balancing 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 220-1101 exam frequently reuses these exact scenarios with slightly different constraints.
✓Rapid elasticityCorrect answer▾
Why this is correct
Rapid elasticity is a core NIST cloud characteristic that enables a public IaaS platform to provision or release compute, storage, or network resources automatically and near-instantaneously in response to fluctuating demand. For an e-commerce site, this means scaling out additional virtual machines or containers during a traffic spike and scaling back down when the spike subsides. The key differentiator is that the capacity change itself is part of the cloud's native behavior, driven by consumption thresholds rather than manual intervention or fixed infrastructure.
✗High availabilityWrong answer — click to see why▾
Why this is wrong here
High availability focuses on minimizing downtime through redundant components, not on automatically scaling resources up and down based on demand. The scenario describes dynamic provisioning and deprovisioning of servers, which is rapid elasticity.
★ When this WOULD be the correct answer
A company deploys its critical application across multiple availability zones with automatic failover. If one zone fails, traffic is instantly redirected to another zone without interruption. This scenario demonstrates high availability.
Why candidates choose this
Candidates may confuse the automatic scaling of resources with maintaining uptime, but high availability is about fault tolerance and redundancy, not dynamic scaling.
✗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 despite component failures, not to automatically scaling resources up and down based on demand. The scenario describes scaling, not failure recovery.
★ When this WOULD be the correct answer
An exam question describing a cloud system that automatically reroutes traffic to healthy instances when a server fails, ensuring continuous operation without manual intervention, would make fault tolerance the correct answer.
Why candidates choose this
Candidates may confuse fault tolerance with rapid elasticity because both involve automatic responses to changing conditions, but fault tolerance focuses on failure resilience rather than scaling to meet demand spikes.
✗Load balancingWrong answer — click to see why▾
Why this is wrong here
Load balancing distributes traffic across existing servers but does not automatically provision or deprovision virtual servers; the scenario describes scaling resources, which is rapid elasticity.
★ When this WOULD be the correct answer
A question describing a system that evenly distributes incoming traffic across multiple servers to prevent any single server from being overwhelmed, without mentioning automatic scaling, would make load balancing the correct answer.
Why candidates choose this
Candidates may confuse load balancing with scaling because both handle increased traffic, but load balancing focuses on distribution, not resource provisioning.
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
This 220-1101 question is part of Courseiva's 896-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 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.