NVIDIA NCP-AII Questions & Answers

This option serves the scenario “A rack diagram claims both InfiniBand rails are independent, but an LLDP or switch inventory shows one server connected twice to rail A”. The appropriate intervention is Trace each cable endpoint against the approved rail map and correct the crossed connection. The present scenario is distinguished by “Use a physical topology reconciliation with port identifiers and approved network role assignments”.

The option would apply to “A migration swaps two similarly labeled fabric cables and only one of four MPI ranks loses inter-node connectivity”. The direct fix is Use a per-port peer discovery and rank-to-node cable map to isolate the incorrect physical connection. This question instead requires “Use a physical topology reconciliation with port identifiers and approved network role assignments”.

The related but distinct situation is “After replacing several DAC cables, a technician fails to check switch port breakout profiles and the same rack has mismatched lane mappings”. Therefore Reconcile breakout cable legs, configured port modes and server interfaces against the reference topology. For the stated problem, “Use a physical topology reconciliation with port identifiers and approved network role assignments” addresses the central condition.

The candidate evidence checks Investigate PCIe link health, slot topology and firmware before assigning the problem to NCCL software in another context. Here the specific acceptance result is A controlled reproduction isolates the failing accelerator and repeated validation runs stop producing the Xid events.

The option would apply to “A node experiences intermittent network errors only during peak HPL and NCCL workload overlap, and the team assumes it is a faulty transceiver”. The strongest acceptance result is that A synchronized stress test after the identified power fix has no fabric errors or voltage excursions, not merely that a command executed. The present scenario is distinguished by “A controlled reproduction isolates the failing accelerator and repeated validation runs stop producing the Xid events”.

This option serves the scenario “The operator sees repeated training slowdowns after a rack cooling change but assumes the NCCL library is defective”. A completed remediation must demonstrate that After cooling remediation, GPU clock limits normalize and iteration times recover. This question instead requires “A controlled reproduction isolates the failing accelerator and repeated validation runs stop producing the Xid events”.

Another failure mode is possible in general, but the stated condition most directly creates the exposure that Confusing NIC and DPU modes can leave expected independent data-path protection inactive.

This option serves the scenario “A tenant host administrator can still flash the BlueField firmware even though the project mandates zero-trust DPU management separation”. The direct failure mode is that Host privilege reaching DPU firmware can undermine the intended isolation boundary. The present scenario is distinguished by “Confusing NIC and DPU modes can leave expected independent data-path protection inactive”.

This alternative addresses the separate case “A GPU server's DPU has an approved high-speed physical link but no functioning OOB path for emergency firmware recovery”. The direct failure mode is that Loss of independent management can prolong outages when the DPU blocks host data paths. The deciding requirement here is “Confusing NIC and DPU modes can leave expected independent data-path protection inactive”.

The related but distinct situation is “An HGX server has eight SXM accelerators but a runbook treats it as eight independent PCIe cards for service procedures”. Therefore Use the platform-specific HGX service and identification documentation before installation or replacement. The deciding requirement here is “Complete installation with controlled elevation and configure separate least-privilege operations accounts before service handover”.

This option serves the scenario “A server shows NVIDIA GPUs in the PCI bus but nvidia-smi fails with a driver communication error”. The appropriate intervention is Check kernel driver load, supported module version and secure boot signing before reattempting workloads. This question instead requires “Complete installation with controlled elevation and configure separate least-privilege operations accounts before service handover”.

For this finding, Align the CUDA runtime and NVIDIA driver with the documented compatibility requirements for the workload image is less direct than Complete installation with controlled elevation and configure separate least-privilege operations accounts before service handover, because One-time deployment privileges are not a reason to retain broad operational access to hardware management and host OS.

This option serves the scenario “A compute fleet boots an OS image with a kernel version unsupported by the chosen GPU driver and fails after installation”. A completed remediation must demonstrate that A cloned host loads the expected NVIDIA module and runs the approved CUDA sample without kernel errors. The present scenario is distinguished by “A controlled restart loads the approved OS and mounts only the specified root and data volumes”.

The option would apply to “A Linux image is cloned with duplicate machine identities and static network parameters across otherwise identical GPU servers”. The strongest acceptance result is that Provisioned nodes have unique host keys and names and register individually with the management controller, not merely that a command executed. This question instead requires “A controlled restart loads the approved OS and mounts only the specified root and data volumes”.

The proposed validation does not isolate the reported fault. An effective closure test requires evidence that A controlled restart loads the approved OS and mounts only the specified root and data volumes.

This alternative addresses the separate case “A deployment moves from an Intel to an AMD host while preserving all x86 CPU tuning flags without verifying the new platform topology”. The direct failure mode is that Blind tuning reuse can degrade performance or disable platform-specific reliability protections. For the stated problem, “Unreviewed power-saving defaults can make an expensive GPU node look underutilized” addresses the central condition.

The related but distinct situation is “A GPU data loader on a dual-socket AMD server places CPU worker threads far from the PCIe root complex hosting the selected GPU”. The acceptance board should flag that Poor NUMA placement can starve otherwise healthy accelerators and reduce training throughput. The deciding requirement here is “Unreviewed power-saving defaults can make an expensive GPU node look underutilized”.

This option serves the scenario “An engineer enables every possible CPU thread for data loading without checking memory locality and context-switch overhead on a multi-socket host”. The primary exposure is that Oversubscribed host threads can slow training and introduce intermittent batch starvation. This question instead requires “Unreviewed power-saving defaults can make an expensive GPU node look underutilized”.

For this finding, Validate the group and user identity mapping plus supported shared mount configuration for compute and login nodes is less direct than Correct the BCM category or node-specific settings for the intended fabric and shared storage before reprovisioning, because A managed cluster category defines common provisioning and network behavior that can affect many assigned nodes.

The related but distinct situation is “A maintenance engineer changes a BCM node category directly in production without checking how many compute nodes inherit it”. The direct fix is Use a controlled category change review, affected-node preview and staged canary provisioning. For the stated problem, “Correct the BCM category or node-specific settings for the intended fabric and shared storage before reprovisioning” addresses the central condition.

That change may help in a different context, but it would not establish that Nodes in the corrected category mount the expected storage and appear on the correct data interfaces after boot. The relevant response is Correct the BCM category or node-specific settings for the intended fabric and shared storage before reprovisioning.

This option serves the scenario “A Base Command Manager cluster relies on one head node and loses both DHCP provisioning and Slurm scheduling whenever that node powers off”. Without correction, An untested single head node can become a cluster-wide control-plane outage. This question instead requires “Assuming unfenced automatic failover can leave a cluster unavailable or vulnerable to dual writers”.

This alternative addresses the separate case “A BCM deployment configures two management heads but both depend on the same power feed and switch without alternate management paths”. The acceptance board should flag that A shared network or power dependency can neutralize the planned control-plane redundancy. For the stated problem, “Assuming unfenced automatic failover can leave a cluster unavailable or vulnerable to dual writers” addresses the central condition.

The option would apply to “A network partition causes a passive BCM head to see the active head as unreachable, and an operator immediately promotes it without quorum checks”. The direct failure mode is that Premature takeover can damage cluster state and prevent reliable subsequent recovery. The present scenario is distinguished by “Assuming unfenced automatic failover can leave a cluster unavailable or vulnerable to dual writers”.

That principle would support Confirm and configure a supported DPU embedded mode with the correct control-plane ownership and authorized policies under different conditions, whereas this scenario is primarily explained by In DPU mode embedded function ownership affects how host networking becomes available during initialization.

This statement could explain another scenario: A tenant host administrator can still flash the BlueField firmware even though the project mandates zero-trust DPU management separation. In the present case the more specific mechanism is that In DPU mode embedded function ownership affects how host networking becomes available during initialization.

The option would apply to “A security engineer assumes BlueField telemetry and control counters can always be read from the host after enabling zero-trust restrictions”. The controlling explanation is that Zero-trust restrictions may intentionally block host-side hardware counters or tracing functions. This question instead requires “In DPU mode embedded function ownership affects how host networking becomes available during initialization”.

This alternative addresses the separate case “A high-speed NIC link shows error spikes only after adjacent power cables are rerouted tightly against the data assembly”. The decisive evidence is that The rerouted cable passes the sustained link-quality test with stable error counters. For the stated problem, “All lanes pass approved BER and FEC thresholds during a full-speed traffic exercise” addresses the central condition.

The candidate evidence checks Inspect FEC and symbol counters, optical power and cable condition rather than using carrier state alone in another context. Here the specific acceptance result is All lanes pass approved BER and FEC thresholds during a full-speed traffic exercise.

That observation does not establish operating effectiveness of Run per-lane high-speed error and eye or signal diagnostics using supported tools. The needed evidence is that All lanes pass approved BER and FEC thresholds during a full-speed traffic exercise.

The option would apply to “An eight-GPU server is assigned to a PDU feed sized for average power rather than accelerator transient peaks”. The acceptance board should flag that An undersized circuit can trip during synchronized load and interrupt an entire training rack. This question instead requires “Shared power infrastructure can defeat otherwise redundant PSU hardware”.

The related but distinct situation is “A rack of fan-cooled AI nodes is installed with blanking panels removed and mixed front-to-rear airflow direction”. Without correction, Poor rack airflow can cause clustered thermal alarms and unpredictable GPU clock reductions. For the stated problem, “Shared power infrastructure can defeat otherwise redundant PSU hardware” addresses the central condition.

This alternative addresses the separate case “A liquid-cooled AI server is powered before facility coolant flow and leak sensing are commissioned”. The primary exposure is that Missing cooling interlocks can expose accelerators and facilities to overheating or coolant incidents. The deciding requirement here is “Shared power infrastructure can defeat otherwise redundant PSU hardware”.