Several municipal workloads share a constrained compute pool; performance collapses when noisy neighbors consume disproportionate capacity. Which deployment issue does this describe?
Select an answer to reveal the explanation.
Short Explanation
Too many roommates fighting over one small fridge—that is noisy-neighbor oversubscription. Shared pools can starve workloads when others hog CPU or I/O. Look at contention and capacity limits before rewriting the whole app.
Full Explanation
Oversubscription in shared compute pools allows noisy neighbors to degrade others’ performance when capacity is constrained. Dedicated isolation, DNS TTLs, or assumed perfect scaling are not the diagnosis when contention symptoms appear. Cloud+ deployment troubleshooting includes recognizing oversubscription as a cause of performance collapse after deploy.