NCP-AII Premium File
- 170 Questions & Answers
- Last Update: Nov 6, 2026
At an AI infrastructure site, a rack of accelerators is connected to two PDUs, yet each feed individually lacks the capacity to support the planned peak draw during failover. Which evidence MOST directly shows that the specific blocker in this scenario has been corrected?
A supported failover test and power measurements stay within circuit limits with one feed unavailable. This observation tests the stated redundant power feed sizing correction rather than unrelated node health. The underlying principle is: Dual cables do not provide electrical redundancy when a surviving circuit cannot carry the load.
A test node successfully reboots, reports the intended version, and has a documented recovery path. That is acceptance evidence for firmware rollback contingency; it does not establish that redundant power feed sizing has been corrected. The relevant observation is: A supported failover test and power measurements stay within circuit limits with one feed unavailable.
A test kernel completes on each expected device with correct output and no driver or memory errors. That is acceptance evidence for representative cuda workload proof; it does not establish that redundant power feed sizing has been corrected. The relevant observation is: A supported failover test and power measurements stay within circuit limits with one feed unavailable.
Hardware inventory and NVIDIA SMI enumerate the full delivered GPU count after remediation. That is acceptance evidence for pcie server seating check; it does not establish that redundant power feed sizing has been corrected. The relevant observation is: A supported failover test and power measurements stay within circuit limits with one feed unavailable.
At an AI infrastructure site, a rack of accelerators is connected to two PDUs, yet each feed individually lacks the capacity to support the planned peak draw during failover. Which technical principle BEST explains the specific failure or solution in this scenario?
Dual cables do not provide electrical redundancy when a surviving circuit cannot carry the load. This is why the operational remedy in this scenario is: Validate the rack's actual peak consumption and redundant-feed capacity against the permitted electrical budget. A direct demonstration is: A supported failover test and power measurements stay within circuit limits with one feed unavailable.
An electrical link-up indicates connectivity, not that the intended topology has been cabled. That principle fits cable map acceptance, but does not explain the redundant power feed sizing failure mechanism. The applicable explanation is: Dual cables do not provide electrical redundancy when a surviving circuit cannot carry the load.
Physical NVLink presence does not establish configured and working peer access for a workload. That principle fits fabric peer-copy readiness, but does not explain the redundant power feed sizing failure mechanism. The applicable explanation is: Dual cables do not provide electrical redundancy when a surviving circuit cannot carry the load.
Hardware faults can be detected below the OS by BMC even when application monitoring is incomplete. That principle fits system management sensor reconciliation, but does not explain the redundant power feed sizing failure mechanism. The applicable explanation is: Dual cables do not provide electrical redundancy when a surviving circuit cannot carry the load.
At an AI infrastructure site, a rack of accelerators is connected to two PDUs, yet each feed individually lacks the capacity to support the planned peak draw during failover. If the described issue remains uncorrected, which consequence is the MOST direct operational risk?
One feed failure may trip the remaining breaker and drop the rack. This follows from the specific unresolved redundant power feed sizing condition. An appropriate mitigation is: Validate the rack's actual peak consumption and redundant-feed capacity against the permitted electrical budget.
Miswired devices can enter the cluster with ambiguous network ownership and cause a wider outage. That is a consequence of installation hold points, not the most direct risk of the stated redundant power feed sizing defect. The scenario-specific exposure is: One feed failure may trip the remaining breaker and drop the rack.
Incorrect polarity can isolate racks despite otherwise healthy switches and hosts. That is a consequence of fiber polarity troubleshooting, not the most direct risk of the stated redundant power feed sizing defect. The scenario-specific exposure is: One feed failure may trip the remaining breaker and drop the rack.
A real cooling failure may be missed if one monitoring layer is trusted alone. That is a consequence of system management sensor reconciliation, not the most direct risk of the stated redundant power feed sizing defect. The scenario-specific exposure is: One feed failure may trip the remaining breaker and drop the rack.
At an AI infrastructure site, gPU nodes are stable when idle but repeatedly reduce clocks during long matrix workloads near the data center's cooling limit. Which operational response MOST directly resolves the specific blocker described before this equipment or service is accepted?
Measure sustained inlet temperatures, fan behavior, airflow, and throttling before increasing workload density. This addresses the reported thermal headroom under load blocker, because thermal management limits component frequency or power to protect the hardware. The acceptance evidence is: A sustained stress test maintains supported temperatures and expected clocks with adequate thermal margin.
Correct airflow obstructions and validate inlet/outlet temperatures using vendor installation limits. This is an appropriate response to cold-aisle airflow obstruction, but the described incident is thermal headroom under load rather than that separate fault. It would not directly establish the required correction: Measure sustained inlet temperatures, fan behavior, airflow, and throttling before increasing workload density.
Configure the supported storage data network, client path, authorization, and mount parameters for the workload. This is an appropriate response to third-party storage network readiness, but the described incident is thermal headroom under load rather than that separate fault. It would not directly establish the required correction: Measure sustained inlet temperatures, fan behavior, airflow, and throttling before increasing workload density.
Align storage identity mapping and least-privilege write permissions with approved workload accounts. This is an appropriate response to storage permissions at initial bring-up, but the described incident is thermal headroom under load rather than that separate fault. It would not directly establish the required correction: Measure sustained inlet temperatures, fan behavior, airflow, and throttling before increasing workload density.
At an AI infrastructure site, gPU nodes are stable when idle but repeatedly reduce clocks during long matrix workloads near the data center's cooling limit. Which evidence MOST directly shows that the specific blocker in this scenario has been corrected?
A sustained stress test maintains supported temperatures and expected clocks with adequate thermal margin. This observation tests the stated thermal headroom under load correction rather than unrelated node health. The underlying principle is: Thermal management limits component frequency or power to protect the hardware.
Long-duration representative compute completes without errors or unsupported thermal or electrical excursions. That is acceptance evidence for workload power envelope signoff; it does not establish that thermal headroom under load has been corrected. The relevant observation is: A sustained stress test maintains supported temperatures and expected clocks with adequate thermal margin.
A test kernel completes on each expected device with correct output and no driver or memory errors. That is acceptance evidence for representative cuda workload proof; it does not establish that thermal headroom under load has been corrected. The relevant observation is: A sustained stress test maintains supported temperatures and expected clocks with adequate thermal margin.
Temperature sensors and sustained load show normal distribution after cable and blanking-panel remediation. That is acceptance evidence for cold-aisle airflow obstruction; it does not establish that thermal headroom under load has been corrected. The relevant observation is: A sustained stress test maintains supported temperatures and expected clocks with adequate thermal margin.
At an AI infrastructure site, gPU nodes are stable when idle but repeatedly reduce clocks during long matrix workloads near the data center's cooling limit. Which technical principle BEST explains the specific failure or solution in this scenario?
Thermal management limits component frequency or power to protect the hardware. This is why the operational remedy in this scenario is: Measure sustained inlet temperatures, fan behavior, airflow, and throttling before increasing workload density. A direct demonstration is: A sustained stress test maintains supported temperatures and expected clocks with adequate thermal margin.
A TPM provides protected measurement and key functions, while the presence of hardware alone does not prove policy enforcement. That principle fits tpm measured-boot evidence, but does not explain the thermal headroom under load failure mechanism. The applicable explanation is: Thermal management limits component frequency or power to protect the hardware.
Reliable maintenance needs persistent correspondence between a device and its current host/slot. That principle fits gpu replacement identity tracking, but does not explain the thermal headroom under load failure mechanism. The applicable explanation is: Thermal management limits component frequency or power to protect the hardware.
Hardware enumeration does not prove that the NIC firmware and physical link are operational together. That principle fits post-flash device fault detection, but does not explain the thermal headroom under load failure mechanism. The applicable explanation is: Thermal management limits component frequency or power to protect the hardware.
At an AI infrastructure site, gPU nodes are stable when idle but repeatedly reduce clocks during long matrix workloads near the data center's cooling limit. If the described issue remains uncorrected, which consequence is the MOST direct operational risk?
Repeated thermal throttling can slow training and precede service interruptions. This follows from the specific unresolved thermal headroom under load condition. An appropriate mitigation is: Measure sustained inlet temperatures, fan behavior, airflow, and throttling before increasing workload density.
Unauthorized users could gain a lower-level path into a secured training server. That is a consequence of bmc credential hardening, not the most direct risk of the stated thermal headroom under load defect. The scenario-specific exposure is: Repeated thermal throttling can slow training and precede service interruptions.
Unsafe handling can damage hardware or injure service personnel. That is a consequence of gpu field installation safety, not the most direct risk of the stated thermal headroom under load defect. The scenario-specific exposure is: Repeated thermal throttling can slow training and precede service interruptions.
Miswired devices can enter the cluster with ambiguous network ownership and cause a wider outage. That is a consequence of installation hold points, not the most direct risk of the stated thermal headroom under load defect. The scenario-specific exposure is: Repeated thermal throttling can slow training and precede service interruptions.
At an AI infrastructure site, new high-density rack doors and bundled cables obstruct front-to-back airflow on half the GPU servers. Which operational response MOST directly resolves the specific blocker described before this equipment or service is accepted?
Correct airflow obstructions and validate inlet/outlet temperatures using vendor installation limits. This addresses the reported cold-aisle airflow obstruction blocker, because airflow paths must carry adequate cool air through the server's designed thermal direction. The acceptance evidence is: Temperature sensors and sustained load show normal distribution after cable and blanking-panel remediation.
Check vendor-supported transceiver standard, wavelength, media, reach, and port compatibility, then correct the pair. This is an appropriate response to optical transceiver matching, but the described incident is cold-aisle airflow obstruction rather than that separate fault. It would not directly establish the required correction: Correct airflow obstructions and validate inlet/outlet temperatures using vendor installation limits.
Complete device-level and interconnect validation before signing off application-level workload acceptance. This is an appropriate response to burn-in acceptance order, but the described incident is cold-aisle airflow obstruction rather than that separate fault. It would not directly establish the required correction: Correct airflow obstructions and validate inlet/outlet temperatures using vendor installation limits.
Measure sustained inlet temperatures, fan behavior, airflow, and throttling before increasing workload density. This is an appropriate response to thermal headroom under load, but the described incident is cold-aisle airflow obstruction rather than that separate fault. It would not directly establish the required correction: Correct airflow obstructions and validate inlet/outlet temperatures using vendor installation limits.
At an AI infrastructure site, new high-density rack doors and bundled cables obstruct front-to-back airflow on half the GPU servers. Which evidence MOST directly shows that the specific blocker in this scenario has been corrected?
Temperature sensors and sustained load show normal distribution after cable and blanking-panel remediation. This observation tests the stated cold-aisle airflow obstruction correction rather than unrelated node health. The underlying principle is: Airflow paths must carry adequate cool air through the server's designed thermal direction.
Post-service inventory, power checks, and diagnostics confirm the new GPU is properly seated and operational. That is acceptance evidence for gpu field installation safety; it does not establish that cold-aisle airflow obstruction has been corrected. The relevant observation is: Temperature sensors and sustained load show normal distribution after cable and blanking-panel remediation.
Topology and host-to-device copy tests show the expected locality and transfer rates. That is acceptance evidence for numa locality in server placement; it does not establish that cold-aisle airflow obstruction has been corrected. The relevant observation is: Temperature sensors and sustained load show normal distribution after cable and blanking-panel remediation.
A sustained stress test maintains supported temperatures and expected clocks with adequate thermal margin. That is acceptance evidence for thermal headroom under load; it does not establish that cold-aisle airflow obstruction has been corrected. The relevant observation is: Temperature sensors and sustained load show normal distribution after cable and blanking-panel remediation.
At an AI infrastructure site, new high-density rack doors and bundled cables obstruct front-to-back airflow on half the GPU servers. Which technical principle BEST explains the specific failure or solution in this scenario?
Airflow paths must carry adequate cool air through the server's designed thermal direction. This is why the operational remedy in this scenario is: Correct airflow obstructions and validate inlet/outlet temperatures using vendor installation limits. A direct demonstration is: Temperature sensors and sustained load show normal distribution after cable and blanking-panel remediation.
Thermal management limits component frequency or power to protect the hardware. That principle fits thermal headroom under load, but does not explain the cold-aisle airflow obstruction failure mechanism. The applicable explanation is: Airflow paths must carry adequate cool air through the server's designed thermal direction.
Accelerator replacements involve electrical, thermal, mechanical, and firmware interfaces. That principle fits gpu field installation safety, but does not explain the cold-aisle airflow obstruction failure mechanism. The applicable explanation is: Airflow paths must carry adequate cool air through the server's designed thermal direction.
Transient idle health does not exercise power delivery and cooling under production demand. That principle fits workload power envelope signoff, but does not explain the cold-aisle airflow obstruction failure mechanism. The applicable explanation is: Airflow paths must carry adequate cool air through the server's designed thermal direction.
At an AI infrastructure site, new high-density rack doors and bundled cables obstruct front-to-back airflow on half the GPU servers. If the described issue remains uncorrected, which consequence is the MOST direct operational risk?
Hot spots can cause device resets or persistent performance throttling. This follows from the specific unresolved cold-aisle airflow obstruction condition. An appropriate mitigation is: Correct airflow obstructions and validate inlet/outlet temperatures using vendor installation limits.
Repeated thermal throttling can slow training and precede service interruptions. That is a consequence of thermal headroom under load, not the most direct risk of the stated cold-aisle airflow obstruction defect. The scenario-specific exposure is: Hot spots can cause device resets or persistent performance throttling.
Misidentified cables make failover and performance diagnosis unreliable. That is a consequence of cable map acceptance, not the most direct risk of the stated cold-aisle airflow obstruction defect. The scenario-specific exposure is: Hot spots can cause device resets or persistent performance throttling.
A partially updated platform may exhibit subtle management, link, or training instability. That is a consequence of coordinated hgx firmware baseline, not the most direct risk of the stated cold-aisle airflow obstruction defect. The scenario-specific exposure is: Hot spots can cause device resets or persistent performance throttling.
Please check your mailbox for a message from support@examlabs.com and follow the directions.