A transit authority must power multi-PSU HGX nodes for a municipal training row. Which power validation best supports redundancy policy?
Select an answer to reveal the explanation.
Short Explanation
Multi-PSU HGX boxes are like twin trolley poles—you want power paths that still work when one feed hiccups. Balance the branch circuits across the PSU feeds so transit’s redundancy policy is real, not just a sticker on the chassis.
Full Explanation
Multi-PSU HGX nodes in a transit-authority municipal training row are designed so redundant power supplies can keep the chassis online when one feed or branch fails. The power validation that best supports that redundancy policy is to balance branch circuits across PSU feeds so the nodes retain their designed redundancy domains under expected GPU load. Balancing means each PSU path lands on an independent, adequately sized circuit rather than collapsing all feeds onto one overloaded breaker. Under training load, that layout preserves the redundancy the platform documentation assumes and avoids a single branch trip taking down the entire HGX chassis mid-job.
Plugging every PSU into a single overloaded branch so one breaker controls the whole chassis destroys redundancy by design: any trip or overload on that branch drops all supplies together. Leaving half the PSUs unplugged until the first production job fails postpones redundancy validation until a rider-facing or schedule-critical training failure, which is the opposite of bring-up policy. Balancing loads only on decorative LED strips while ignoring PSU redundancy domains confuses cosmetic indicators with electrical topology and does not prove feed diversity under GPU draw.
Exam caveat: HGX multi-PSU redundancy is only real when PSUs are fed from independent, balanced branches sized for expected GPU load—common-branch wiring is a false redundancy. Operational check: map each PSU to its PDU/branch, verify diversity against the transit row power plan, measure or estimate draw under expected GPU load, confirm no single branch is the sole path for all supplies, and document the feed map before declaring the municipal training row power-validated.