D-PEMX-DY-23 · Question #114
An administrator is receiving notifications about insufficient power for a PowerEdge MX7000 chassis. The chassis is fed from two different power grids. What is the best policy to maximize power and…
The correct answer is D. No Redundancy. No Redundancy (D) is correct because it dedicates the full capacity of all PSUs to the power budget without reserving any for failover, resolving the insufficient power notifications. Since the chassis is already physically connected to two separate power grids, uptime is…
Question
An administrator is receiving notifications about insufficient power for a PowerEdge MX7000 chassis. The chassis is fed from two different power grids. What is the best policy to maximize power and maintain uptime?
Options
- APSU Pairing
- BGrid Redundancy
- CPSU Redundancy
- DNo Redundancy
How the community answered
(22 responses)- A9% (2)
- B5% (1)
- C5% (1)
- D82% (18)
Explanation
No Redundancy (D) is correct because it dedicates the full capacity of all PSUs to the power budget without reserving any for failover, resolving the insufficient power notifications. Since the chassis is already physically connected to two separate power grids, uptime is protected at the infrastructure level - making software-level redundancy policies unnecessary overhead.
Grid Redundancy (B) splits PSUs across two grids and reserves one grid's capacity as a standby, which cuts the usable power budget roughly in half - the opposite of what's needed here. PSU Redundancy (C) similarly keeps spare PSUs in reserve rather than contributing to the available wattage. PSU Pairing (A) pairs PSUs together for coordinated failover, which also reduces the effective power budget and doesn't leverage the dual-grid infrastructure already in place.
Memory tip: Think "No Redundancy = No reservation = No power shortage." When the physical infrastructure (dual grids) already handles uptime, the chassis policy should maximize power - and No Redundancy is the only option that puts every PSU to work.
Topics
Community Discussion
No community discussion yet for this question.