DU0-001 · Question #94
What are three benefits of rack-oriented cooling architecture? (Choose three.)
The correct answer is A. It reduces CRAC fan power required. Note: This question asks you to "Choose three," so the complete correct answer set is A, B, and D - not A alone. The three benefits of rack-oriented cooling are that it reduces CRAC fan power required (A), utilizes the entire rated CRAC capacity (B), and is easy to deploy for…
Question
Options
- AIt reduces CRAC fan power required.
- BIt utilizes the entire rated CRAC capacity.
- CIt eliminates the need for humidity control.
- DIt is easy to deploy for high density applications.
- EIt reduces the number of air conditioning devices.
How the community answered
(21 responses)- A86% (18)
- B5% (1)
- C5% (1)
- D5% (1)
Explanation
Note: This question asks you to "Choose three," so the complete correct answer set is A, B, and D - not A alone. The three benefits of rack-oriented cooling are that it reduces CRAC fan power required (A), utilizes the entire rated CRAC capacity (B), and is easy to deploy for high-density applications (D). Rack-oriented cooling places cooling units directly adjacent to heat sources, so fans do not need to push air across an entire raised-floor room, which reduces fan energy and allows each CRAC unit to operate at or near its full rated output rather than cycling inefficiently.
Option C is incorrect because humidity control remains necessary regardless of cooling architecture - moisture management is a separate concern from heat removal. Option E is incorrect because rack-oriented approaches typically require more cooling devices, not fewer, since units are distributed throughout the data center rather than centralized.
Memory tip: Think of rack-oriented cooling as "close-coupled" - proximity to the heat source means fans work less (lower fan power), each unit works fully (full rated capacity), and dense racks get enough cooling (high-density friendly). The things it does NOT help with are humidity and device count.
Topics
Community Discussion
No community discussion yet for this question.