Resource Pooling: Why Your VM Slows Down Even at Low CPU/Memory Usage
A company runs its customer relationship management (CRM) application on a single virtual machine (VM) in a public cloud IaaS environment. During the workday, the application's response time becomes highly variable and often slow, even though the VM's CPU and memory utilization rarely exceed 50%. The cloud provider states that the physical host is a shared multi-tenant server. Which cloud computing concept is MOST likely causing this performance degradation?
⚠ Common exam trap
Candidates often assume high CPU or memory utilization is the only cause of poor performance, ignoring that shared I/O resources (disk and network) are often the hidden bottleneck in multi-tenant environments.
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
✓
Resource pooling leading to the 'noisy neighbor' effect
The performance degradation is most likely due to resource pooling in a multi-tenant IaaS environment, where the 'noisy neighbor' effect occurs. Even though the VM's own CPU and memory utilization are low, another VM on the same physical host may be consuming shared resources like disk I/O or network bandwidth, causing contention. This is a classic symptom of a shared hypervisor where one tenant's workload starves others of critical I/O resources.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Resource pooling leading to the 'noisy neighbor' effect
Why this is correct
Resource pooling is a foundational cloud characteristic in which CPU, memory, storage, and network bandwidth from a physical host are shared among multiple VMs. Even when the affected VM's own CPU and memory utilization are low, contention on shared resources such as memory bandwidth, disk I/O queues, and last-level cache can cause severe performance degradation. This 'noisy neighbor' effect occurs when another tenant on the same hypervisor consumes an outsized share of a contended resource, making the CRM's response times erratic without any change in its own load. The correct answer identifies this shared-infrastructure interference as the root cause.
- ✗
Rapid elasticity causing the VM to be moved between hosts
Why it's wrong here
Rapid elasticity is the cloud capability to quickly add or remove resources—such as vCPUs, memory, or instances—in response to load changes. While live migration of a VM between hosts during load balancing can cause a brief pause or performance hit, it is not a natural outcome of elasticity, and nothing in the scenario indicates frequent or even occasional VM moves. The symptom of consistent, variable performance under low utilization is better explained by ongoing contention on shared physical resources than by a one-time administrative operation. Thus, elasticity does not cause the VM to be 'moved' between hosts as a matter of normal operation.
When this WOULD be correct
A question where a VM experiences performance degradation during scaling events (e.g., sudden traffic spikes) and the cloud provider mentions automatic scaling or resource provisioning. The correct answer would be rapid elasticity causing resource allocation delays.
- ✗
Measured service billing that throttles the VM
Why it's wrong here
Measured service in cloud computing means that resource usage is monitored, tracked, and billed to the customer, often giving transparency for cost allocation. It does not by itself impose any performance constraint; throttling would only occur if the provider enforces a metered usage limit or a quota policy, and the provider in this scenario explicitly confirms that no such resource limits are in place. Without those limits, metering is purely a billing function and cannot explain the observed performance degradation. Therefore, measured service is not the root cause of the inconsistent CRM behavior.
When this WOULD be correct
A question where a cloud provider imposes a bandwidth or API call limit based on a subscription tier, and the application experiences slowdowns or throttling errors when exceeding that limit, even though resource utilization is low.
- ✗
Lack of scalability in the application design
Why it's wrong here
Lack of scalability in the application design refers to the application's inability to handle increased load effectively, such as by scaling out horizontally or scaling up vertically. This would manifest as consistently degrading performance as user count or transaction volume climbs, rather than intermittent slowdowns occurring while the VM's own resource consumption remains low. In this scenario, the performance issue appears independent of the application's actual demand on its allocated resources, pointing to external resource contention rather than an architectural scaling deficiency. Therefore, while poor scalability can lead to performance problems, it does not explain the sporadic, low-utilization spikes described here.
When this WOULD be correct
This option would be correct if the question described an application that cannot handle increased load because it is not designed to scale horizontally or vertically, such as a single-threaded application that maxes out CPU on a single VM, leading to performance degradation during peak usage.
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.
✓Resource pooling leading to the 'noisy neighbor' effectCorrect answer▾
Why this is correct
Resource pooling is a foundational cloud characteristic in which CPU, memory, storage, and network bandwidth from a physical host are shared among multiple VMs. Even when the affected VM's own CPU and memory utilization are low, contention on shared resources such as memory bandwidth, disk I/O queues, and last-level cache can cause severe performance degradation. This 'noisy neighbor' effect occurs when another tenant on the same hypervisor consumes an outsized share of a contended resource, making the CRM's response times erratic without any change in its own load. The correct answer identifies this shared-infrastructure interference as the root cause.
✗Rapid elasticity causing the VM to be moved between hostsWrong answer — click to see why▾
Why this is wrong here
Rapid elasticity refers to the ability to quickly scale resources up or down, not to moving VMs between hosts. The performance issue described is due to contention for shared physical resources, not elasticity.
★ When this WOULD be the correct answer
A question where a VM experiences performance degradation during scaling events (e.g., sudden traffic spikes) and the cloud provider mentions automatic scaling or resource provisioning. The correct answer would be rapid elasticity causing resource allocation delays.
Why candidates choose this
Candidates may confuse 'elasticity' with 'mobility' or think that moving VMs between hosts (live migration) is part of elasticity, leading them to incorrectly attribute performance issues to VM relocation.
✗Measured service billing that throttles the VMWrong answer — click to see why▾
Why this is wrong here
Measured service billing typically involves pay-per-use metering and may throttle only if usage exceeds a purchased plan, but the scenario describes variable response time without exceeding CPU/memory limits, and throttling would likely show high utilization or explicit rate limiting, not just slow response with low utilization.
★ When this WOULD be the correct answer
A question where a cloud provider imposes a bandwidth or API call limit based on a subscription tier, and the application experiences slowdowns or throttling errors when exceeding that limit, even though resource utilization is low.
Why candidates choose this
Candidates may confuse 'measured service' with any performance degradation in a cloud environment, assuming billing-related throttling is the cause when the real issue is resource contention from multi-tenancy.
✗Lack of scalability in the application designWrong answer — click to see why▾
Why this is wrong here
The question describes a performance issue caused by resource contention on a shared physical host, not by a lack of scalability in the application design. The application's slow response time is due to other tenants' activities (noisy neighbor), not an inability to scale.
★ When this WOULD be the correct answer
This option would be correct if the question described an application that cannot handle increased load because it is not designed to scale horizontally or vertically, such as a single-threaded application that maxes out CPU on a single VM, leading to performance degradation during peak usage.
Why candidates choose this
Candidates may confuse performance degradation due to resource contention with application scalability issues, especially when the symptoms (slow response time) are similar, and they may not fully understand the implications of multi-tenant environments.
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
Printer Connection Types: USB, Network, Wireless
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.
Key term
Anything As A Service
A model where you rent any IT resource or service over the internet instead of owning it.
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.