5V0-43.21 · Question #25
Applications are being deployed in a hosted environment. The platform owner has a requirement to reduce infrastructure costs by allowing servers to be deprovisioned at times of lower load without…
The correct answer is D. Fewest Tasks. Fewest Servers (D) is the algorithm designed specifically to consolidate active connections onto the minimum number of servers, allowing unused servers to be safely deprovisioned during low-traffic periods without dropping user sessions. Least Connections (A) routes new…
Question
Applications are being deployed in a hosted environment. The platform owner has a requirement to reduce infrastructure costs by allowing servers to be deprovisioned at times of lower load without impacting user traffic. Which load balancing algorithm is specifically designed to support this requirement?
Options
- ALeast Connections
- BLeast Load
- CFewest Servers
- DFewest Tasks
How the community answered
(43 responses)- A12% (5)
- B2% (1)
- C7% (3)
- D79% (34)
Explanation
Fewest Servers (D) is the algorithm designed specifically to consolidate active connections onto the minimum number of servers, allowing unused servers to be safely deprovisioned during low-traffic periods without dropping user sessions. Least Connections (A) routes new requests to whichever server has the fewest active connections, optimizing distribution but never actively consolidating traffic to free up servers. Least Load (B) routes based on overall server resource utilization (CPU, memory), again optimizing balance rather than minimizing the number of active servers. Fewest Tasks (D's near-cousin distractor) doesn't exist as a standard load balancing term - it's a fabricated option designed to confuse.
Memory tip: Think "Fewest Servers = fewer bills" - the algorithm's entire purpose is cost reduction by keeping only the minimum servers alive, making it the only option motivated by deprovisioning, not just balancing.
Topics
Community Discussion
No community discussion yet for this question.