NCP-AII Premium File
- 170 Questions & Answers
- Last Update: Nov 6, 2026
At an AI infrastructure site, a newly cabled high-speed fabric has one optical pair down; transceiver alarms indicate no receive light although transmit power is normal. Which evidence MOST directly shows that the specific blocker in this scenario has been corrected?
Receive optical power and both directional link indicators return to supported ranges. This observation tests the stated fiber polarity troubleshooting correction rather than unrelated node health. The underlying principle is: Optical receivers need light delivered through the correct end-to-end fiber path.
NVIDIA SMI reports the expected devices, driver version, state, and telemetry without errors. That is acceptance evidence for nvidia smi bring-up baseline; it does not establish that fiber polarity troubleshooting has been corrected. The relevant observation is: Receive optical power and both directional link indicators return to supported ranges.
A physical link map and switch neighbor records match the intended host-to-leaf attachments. That is acceptance evidence for cable map acceptance; it does not establish that fiber polarity troubleshooting has been corrected. The relevant observation is: Receive optical power and both directional link indicators return to supported ranges.
All four nodes report approved firmware versions, with post-update health and rollback evidence. That is acceptance evidence for coordinated hgx firmware baseline; it does not establish that fiber polarity troubleshooting has been corrected. The relevant observation is: Receive optical power and both directional link indicators return to supported ranges.
At an AI infrastructure site, a newly cabled high-speed fabric has one optical pair down; transceiver alarms indicate no receive light although transmit power is normal. Which technical principle BEST explains the specific failure or solution in this scenario?
Optical receivers need light delivered through the correct end-to-end fiber path. This is why the operational remedy in this scenario is: Inspect connector orientation, fiber polarity, and patch continuity using an approved test method. A direct demonstration is: Receive optical power and both directional link indicators return to supported ranges.
BMC and host networking are separate logical endpoints even when they belong to the same physical server. That principle fits bmc versus host ip identity, but does not explain the fiber polarity troubleshooting failure mechanism. The applicable explanation is: Optical receivers need light delivered through the correct end-to-end fiber path.
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 fiber polarity troubleshooting failure mechanism. The applicable explanation is: Optical receivers need light delivered through the correct end-to-end fiber path.
Airflow paths must carry adequate cool air through the server's designed thermal direction. That principle fits cold-aisle airflow obstruction, but does not explain the fiber polarity troubleshooting failure mechanism. The applicable explanation is: Optical receivers need light delivered through the correct end-to-end fiber path.
At an AI infrastructure site, a newly cabled high-speed fabric has one optical pair down; transceiver alarms indicate no receive light although transmit power is normal. If the described issue remains uncorrected, which consequence is the MOST direct operational risk?
Incorrect polarity can isolate racks despite otherwise healthy switches and hosts. This follows from the specific unresolved fiber polarity troubleshooting condition. An appropriate mitigation is: Inspect connector orientation, fiber polarity, and patch continuity using an approved test method.
Tenant compromise could expose remote power controls or firmware configuration. That is a consequence of out-of-band network isolation, not the most direct risk of the stated fiber polarity troubleshooting defect. The scenario-specific exposure is: Incorrect polarity can isolate racks despite otherwise healthy switches and hosts.
A single switch failure would disconnect all accelerators in its rack. That is a consequence of fabric redundancy design, not the most direct risk of the stated fiber polarity troubleshooting defect. The scenario-specific exposure is: Incorrect polarity can isolate racks despite otherwise healthy switches and hosts.
An early workload failure can conceal unsafe installation or an unverified dependency and delay root-cause isolation. That is a consequence of rack acceptance sequencing, not the most direct risk of the stated fiber polarity troubleshooting defect. The scenario-specific exposure is: Incorrect polarity can isolate racks despite otherwise healthy switches and hosts.
At an AI infrastructure site, after a rack move, physical labels show GPU host ports connected to the wrong leaf-switch ports while link LEDs remain green. Which operational response MOST directly resolves the specific blocker described before this equipment or service is accepted?
Reconcile cable serials and endpoint mappings with the authorized design before production admission. This addresses the reported cable map acceptance blocker, because an electrical link-up indicates connectivity, not that the intended topology has been cabled. The acceptance evidence is: A physical link map and switch neighbor records match the intended host-to-leaf attachments.
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 cable map acceptance rather than that separate fault. It would not directly establish the required correction: Reconcile cable serials and endpoint mappings with the authorized design before production admission.
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 cable map acceptance rather than that separate fault. It would not directly establish the required correction: Reconcile cable serials and endpoint mappings with the authorized design before production admission.
Reconcile firmware/PCIe enumeration with device visibility and isolate the missing hardware path before acceptance. This is an appropriate response to pcie enumeration consistency, but the described incident is cable map acceptance rather than that separate fault. It would not directly establish the required correction: Reconcile cable serials and endpoint mappings with the authorized design before production admission.
At an AI infrastructure site, after a rack move, physical labels show GPU host ports connected to the wrong leaf-switch ports while link LEDs remain green. Which evidence MOST directly shows that the specific blocker in this scenario has been corrected?
A physical link map and switch neighbor records match the intended host-to-leaf attachments. This observation tests the stated cable map acceptance correction rather than unrelated node health. The underlying principle is: An electrical link-up indicates connectivity, not that the intended topology has been cabled.
Attestation records contain valid boot measurements tied to the intended platform configuration. That is acceptance evidence for tpm measured-boot evidence; it does not establish that cable map acceptance has been corrected. The relevant observation is: A physical link map and switch neighbor records match the intended host-to-leaf attachments.
Both ends negotiate the intended link with stable signal margin and zero recurring physical errors. That is acceptance evidence for optical transceiver matching; it does not establish that cable map acceptance has been corrected. The relevant observation is: A physical link map and switch neighbor records match the intended host-to-leaf attachments.
The acceptance package includes GPU diagnostics, link checks, thermal data, and representative workload results for both servers. That is acceptance evidence for burn-in acceptance order; it does not establish that cable map acceptance has been corrected. The relevant observation is: A physical link map and switch neighbor records match the intended host-to-leaf attachments.
At an AI infrastructure site, after a rack move, physical labels show GPU host ports connected to the wrong leaf-switch ports while link LEDs remain green. Which technical principle BEST explains the specific failure or solution in this scenario?
An electrical link-up indicates connectivity, not that the intended topology has been cabled. This is why the operational remedy in this scenario is: Reconcile cable serials and endpoint mappings with the authorized design before production admission. A direct demonstration is: A physical link map and switch neighbor records match the intended host-to-leaf attachments.
Memory ECC signals can reveal data integrity defects that temperature alone cannot detect. That principle fits ecc health at acceptance, but does not explain the cable map acceptance failure mechanism. The applicable explanation is: An electrical link-up indicates connectivity, not that the intended topology has been cabled.
A PCIe device needs proper physical connection and power before software can initialize it. That principle fits pcie server seating check, but does not explain the cable map acceptance failure mechanism. The applicable explanation is: An electrical link-up indicates connectivity, not that the intended topology has been cabled.
Dual cables do not provide electrical redundancy when a surviving circuit cannot carry the load. That principle fits redundant power feed sizing, but does not explain the cable map acceptance failure mechanism. The applicable explanation is: An electrical link-up indicates connectivity, not that the intended topology has been cabled.
At an AI infrastructure site, after a rack move, physical labels show GPU host ports connected to the wrong leaf-switch ports while link LEDs remain green. If the described issue remains uncorrected, which consequence is the MOST direct operational risk?
Misidentified cables make failover and performance diagnosis unreliable. This follows from the specific unresolved cable map acceptance condition. An appropriate mitigation is: Reconcile cable serials and endpoint mappings with the authorized design before production admission.
Unverified GPUs can fail under real model load after the equipment has been formally accepted. That is a consequence of burn-in acceptance order, not the most direct risk of the stated cable map acceptance defect. The scenario-specific exposure is: Misidentified cables make failover and performance diagnosis unreliable.
Starting production jobs before driver readiness creates avoidable failures. That is a consequence of nvidia smi bring-up baseline, not the most direct risk of the stated cable map acceptance defect. The scenario-specific exposure is: Misidentified cables make failover and performance diagnosis unreliable.
Training traffic may intermittently fail while ordinary hardware discovery appears healthy. That is a consequence of post-flash device fault detection, not the most direct risk of the stated cable map acceptance defect. The scenario-specific exposure is: Misidentified cables make failover and performance diagnosis unreliable.
At an AI infrastructure site, a field engineer is asked to replace a GPU in a live high-density chassis with no confirmed service isolation or ESD protection. Which operational response MOST directly resolves the specific blocker described before this equipment or service is accepted?
Follow the hardware service guide for quiescence, power isolation, antistatic handling, and supported replacement steps. This addresses the reported gpu field installation safety blocker, because accelerator replacements involve electrical, thermal, mechanical, and firmware interfaces. The acceptance evidence is: Post-service inventory, power checks, and diagnostics confirm the new GPU is properly seated and operational.
Follow the approved physical-to-logical bring-up sequence: inventory, power and cooling, BMC, firmware, links, driver visibility, then workload tests. This is an appropriate response to rack acceptance sequencing, but the described incident is gpu field installation safety rather than that separate fault. It would not directly establish the required correction: Follow the hardware service guide for quiescence, power isolation, antistatic handling, and supported replacement steps.
Stop admission and complete a dependency-gated commissioning checklist before integrating the rack with live cluster services. This is an appropriate response to installation hold points, but the described incident is gpu field installation safety rather than that separate fault. It would not directly establish the required correction: Follow the hardware service guide for quiescence, power isolation, antistatic handling, and supported replacement steps.
Take the server out of service and inspect supported slot seating, risers, auxiliary power, and vendor service documentation. This is an appropriate response to pcie server seating check, but the described incident is gpu field installation safety rather than that separate fault. It would not directly establish the required correction: Follow the hardware service guide for quiescence, power isolation, antistatic handling, and supported replacement steps.
At an AI infrastructure site, a field engineer is asked to replace a GPU in a live high-density chassis with no confirmed service isolation or ESD protection. Which evidence MOST directly shows that the specific blocker in this scenario has been corrected?
Post-service inventory, power checks, and diagnostics confirm the new GPU is properly seated and operational. This observation tests the stated gpu field installation safety correction rather than unrelated node health. The underlying principle is: Accelerator replacements involve electrical, thermal, mechanical, and firmware interfaces.
The BIOS hardware inventory, operating system, and SMI agree on eight operational adapters across reboots. That is acceptance evidence for pcie enumeration consistency; it does not establish that gpu field installation safety has been corrected. The relevant observation is: Post-service inventory, power checks, and diagnostics confirm the new GPU is properly seated and operational.
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 gpu field installation safety has been corrected. The relevant observation is: Post-service inventory, power checks, and diagnostics confirm the new GPU is properly seated and operational.
Receive optical power and both directional link indicators return to supported ranges. That is acceptance evidence for fiber polarity troubleshooting; it does not establish that gpu field installation safety has been corrected. The relevant observation is: Post-service inventory, power checks, and diagnostics confirm the new GPU is properly seated and operational.
At an AI infrastructure site, a field engineer is asked to replace a GPU in a live high-density chassis with no confirmed service isolation or ESD protection. Which technical principle BEST explains the specific failure or solution in this scenario?
Accelerator replacements involve electrical, thermal, mechanical, and firmware interfaces. This is why the operational remedy in this scenario is: Follow the hardware service guide for quiescence, power isolation, antistatic handling, and supported replacement steps. A direct demonstration is: Post-service inventory, power checks, and diagnostics confirm the new GPU is properly seated and operational.
Dual cables do not provide electrical redundancy when a surviving circuit cannot carry the load. That principle fits redundant power feed sizing, but does not explain the gpu field installation safety failure mechanism. The applicable explanation is: Accelerator replacements involve electrical, thermal, mechanical, and firmware interfaces.
Out-of-band control interfaces can power-cycle hosts independently of the host operating system. That principle fits out-of-band network isolation, but does not explain the gpu field installation safety failure mechanism. The applicable explanation is: Accelerator replacements involve electrical, thermal, mechanical, and firmware interfaces.
Each deployment layer depends on the electrical and management readiness of the layer below it. That principle fits rack acceptance sequencing, but does not explain the gpu field installation safety failure mechanism. The applicable explanation is: Accelerator replacements involve electrical, thermal, mechanical, and firmware interfaces.
At an AI infrastructure site, a field engineer is asked to replace a GPU in a live high-density chassis with no confirmed service isolation or ESD protection. If the described issue remains uncorrected, which consequence is the MOST direct operational risk?
Unsafe handling can damage hardware or injure service personnel. This follows from the specific unresolved gpu field installation safety condition. An appropriate mitigation is: Follow the hardware service guide for quiescence, power isolation, antistatic handling, and supported replacement steps.
A single switch failure would disconnect all accelerators in its rack. That is a consequence of fabric redundancy design, not the most direct risk of the stated gpu field installation safety defect. The scenario-specific exposure is: Unsafe handling can damage hardware or injure service personnel.
A node may look healthy in inventory while failing its first production kernel. That is a consequence of representative cuda workload proof, not the most direct risk of the stated gpu field installation safety defect. The scenario-specific exposure is: Unsafe handling can damage hardware or injure service personnel.
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 gpu field installation safety defect. The scenario-specific exposure is: Unsafe handling can damage hardware or injure service personnel.
Please check your mailbox for a message from support@examlabs.com and follow the directions.