NVIDIA NCP-AII Questions & Answers

The option would apply to “After reboot, a previously assigned MIG layout disappears and the scheduler tries to place jobs on nonexistent device UUIDs”. The decisive evidence is that A controlled reboot restores the intended GPU and compute instances before accepting tenant jobs. This question instead requires “Tenant benchmark runs use only their allocated profiles with expected per-instance resource limits”.

The related but distinct situation is “Two tenants see the same MIG device assignment because an orchestration template reuses one accelerator identifier”. The strongest acceptance result is that A concurrent workload test shows distinct assigned MIG identifiers and authorized resource visibility, not merely that a command executed. For the stated problem, “Tenant benchmark runs use only their allocated profiles with expected per-instance resource limits” addresses the central condition.

This option serves the scenario “An administrator enables MIG mode on a supported GPU but creates no GPU or compute instances and the workload sees no device”. The strongest acceptance result is that The instance inventory lists valid GPU and compute instances and a sample job uses the assigned device, not merely that a command executed. The present scenario is distinguished by “Tenant benchmark runs use only their allocated profiles with expected per-instance resource limits”.

The related but distinct situation is “A network team enables a BlueField security mode that restricts host-side reads, then declares the card defective when a host monitoring tool loses access”. This case illustrates that Hardened BlueField modes intentionally remove some host privileges without causing hardware failure. The deciding requirement here is “DPU hardware health is not fully validated by link carrier or host-side driver initialization”.

This option serves the scenario “A BlueField-3 firmware update reports success but its active image is still the old slot after restart”. The operational evidence follows from the mechanism that Firmware staging and activation can be separate steps on devices with multiple firmware images. This question instead requires “DPU hardware health is not fully validated by link carrier or host-side driver initialization”.

This is an incorrect prioritization of the mechanism. The reported fault points to DPU hardware health is not fully validated by link carrier or host-side driver initialization, not the separate condition involving BlueField-3 adapters pass host Ethernet traffic but the embedded Arm software revision differs from the approved fabric interoperability matrix.

This option serves the scenario “An operator checks spine switches only by ping and does not inspect temperature, transceiver status or port error counters”. A completed remediation must demonstrate that The signed switch report records healthy sensors, expected interfaces and low error rates during burn-in. The present scenario is distinguished by “Switch inventory and active interface profiles match supported capabilities and all intended ports are operational”.

The candidate evidence checks Check the supported fabric software compatibility matrix and apply the approved staged version baseline in another context. Here the specific acceptance result is Switch inventory and active interface profiles match supported capabilities and all intended ports are operational.

The related but distinct situation is “A fabric switch reboot clears a temporary configuration and leaves performance counters and congestion policies different from the acceptance baseline”. The strongest acceptance result is that Post-restart readback matches policy and NCCL fabric performance remains within threshold, not merely that a command executed. For the stated problem, “Switch inventory and active interface profiles match supported capabilities and all intended ports are operational” addresses the central condition.

This alternative addresses the separate case “A node passes short GPU tests but its application intermittently throttles after twenty minutes of sustained work”. Without correction, Short acceptance tests can conceal thermally constrained GPUs that disrupt production jobs. For the stated problem, “Unvalidated user-space dependencies can cause failures after jobs are distributed to the cluster” addresses the central condition.

The option would apply to “A GPU server passes nvidia-smi query but CUDA sample binaries fail to allocate device memory under an ordinary user account”. Without correction, A scheduler may dispatch jobs to a node that cannot run real tenant workloads. The present scenario is distinguished by “Unvalidated user-space dependencies can cause failures after jobs are distributed to the cluster”.

This option serves the scenario “A server can execute one GPU benchmark but its expected GPU memory capacity is reduced by an unintended MIG partition profile”. The acceptance board should flag that Unexpected resource partitioning can prevent large models from loading even on powerful hardware. This question instead requires “Unvalidated user-space dependencies can cause failures after jobs are distributed to the cluster”.

The option would apply to “A third-party parallel file system is mounted on compute hosts with defaults that ignore required training read throughput and access permissions”. The decisive evidence is that Parallel readers from representative nodes reach the benchmark target and unapproved accounts are denied. This question instead requires “A representative training loader reads data correctly with documented consistency and performance behavior”.

The related but distinct situation is “A new AI storage array is configured for capacity only, while checkpoint bursts from many nodes overwhelm metadata operations”. A completed remediation must demonstrate that A full-scale checkpoint test meets completion and recovery targets without excessive metadata latency. For the stated problem, “A representative training loader reads data correctly with documented consistency and performance behavior” addresses the central condition.

This alternative addresses the separate case “A compute image mounts an NFS training share read-write for every job despite datasets intended to be immutable”. A completed remediation must demonstrate that A test job reads the dataset but cannot modify protected source examples while writing to its output area. The deciding requirement here is “A representative training loader reads data correctly with documented consistency and performance behavior”.

The related but distinct situation is “A new server passes isolated GPU tests but fails when eight GPUs and all NICs are stressed concurrently”. The appropriate intervention is Validate combined system stress with explicit GPU, NIC and thermal limits before acceptance. The deciding requirement here is “Correlate application status with management telemetry, kernel logs and accelerator hardware fault counters”.

This alternative addresses the separate case “A new GPU node passes nvidia-smi inventory but its first long compute test reports intermittent GPU Xid faults”. Therefore Run a controlled single-node accelerator stress and correlate Xid messages, ECC, thermals and power readings. For the stated problem, “Correlate application status with management telemetry, kernel logs and accelerator hardware fault counters” addresses the central condition.

The option would apply to “An acceptance engineer benchmarks only GPU number zero on an eight-GPU HGX server and records the entire node as healthy”. Therefore Stress every installed accelerator simultaneously and reconcile per-GPU health and performance results. The present scenario is distinguished by “Correlate application status with management telemetry, kernel logs and accelerator hardware fault counters”.

This option serves the scenario “GPU utilization stalls during checkpoint writes while parallel storage servers show high metadata latency rather than low network throughput”. The appropriate intervention is Profile checkpoint file counts, metadata operations and storage layout, then tune with the storage vendor's supported method. The present scenario is distinguished by “Measure throughput end-to-end from compute nodes, including mounts, NICs, permissions and congestion”.

This alternative addresses the separate case “A storage optimization changes striping width for a parallel filesystem without measuring actual training and checkpoint traffic patterns”. The appropriate intervention is Benchmark representative reader and writer concurrency before choosing supported filesystem striping parameters. The deciding requirement here is “Measure throughput end-to-end from compute nodes, including mounts, NICs, permissions and congestion”.

That change may help in a different context, but it would not establish that A scheduled multi-node data-loader test reaches target throughput with bounded tail latency. The relevant response is Measure throughput end-to-end from compute nodes, including mounts, NICs, permissions and congestion.

This alternative addresses the separate case “A network acceptance uses iperf TCP between CPU hosts and assumes it proves GPU RDMA collective bandwidth”. The operational evidence follows from the mechanism that CPU TCP throughput does not establish GPU communication performance or RDMA configuration. For the stated problem, “Network congestion and traffic competition can reduce throughput even before obvious hard link failures appear” addresses the central condition.

The option would apply to “A new AI cluster runs NCCL collective tests with payloads so small that latency dominates and then reports the network cannot meet its bulk-training bandwidth target”. The operational evidence follows from the mechanism that Collective throughput and communication latency have different bottlenecks across message sizes. The present scenario is distinguished by “Network congestion and traffic competition can reduce throughput even before obvious hard link failures appear”.

The related but distinct situation is “Two node sets obtain different NCCL bandwidth because one job uses a different network interface or HCA selection”. The operational evidence follows from the mechanism that Distributed collective results depend on the network interface and runtime transport actually selected. The deciding requirement here is “Network congestion and traffic competition can reduce throughput even before obvious hard link failures appear”.

The option would apply to “A Base Command Manager cluster relies on one head node and loses both DHCP provisioning and Slurm scheduling whenever that node powers off”. The appropriate intervention is Install and verify supported primary and secondary BCM head-node high availability with safe ownership transfer. This question instead requires “Distinguish fixed primary/secondary identity from changing active/passive operational roles in HA validation”.

The related but distinct situation is “A BCM deployment configures two management heads but both depend on the same power feed and switch without alternate management paths”. Therefore Separate critical HA failure domains across the designed network and power infrastructure. For the stated problem, “Distinguish fixed primary/secondary identity from changing active/passive operational roles in HA validation” addresses the central condition.

This alternative addresses the separate case “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 appropriate intervention is Use the documented BCM HA quorum and split-brain prevention procedure before changing service ownership. The deciding requirement here is “Distinguish fixed primary/secondary identity from changing active/passive operational roles in HA validation”.

The related but distinct situation is “A compute image mounts an NFS training share read-write for every job despite datasets intended to be immutable”. The direct fix is Apply dataset-specific read-only access and controlled output paths using approved identities. The deciding requirement here is “Validate storage network path, supported client settings, capacity and authorized mount options before distributed training”.

This option addresses an alternative scenario (A new AI storage array is configured for capacity only, while checkpoint bursts from many nodes overwhelm metadata operations); the reported issue instead calls for Validate storage network path, supported client settings, capacity and authorized mount options before distributed training.

This alternative addresses the separate case “A vendor deploys object storage for large training data but users assume POSIX rename semantics without checking workload behavior”. The appropriate intervention is Validate the application access pattern against object or file storage semantics before choosing mount and API parameters. For the stated problem, “Validate storage network path, supported client settings, capacity and authorized mount options before distributed training” addresses the central condition.

This option serves the scenario “A training partition accepts jobs from every team even though it is meant for one restricted research group”. The decisive evidence is that An unauthorized user cannot submit to the protected partition while an approved user runs a test job. The present scenario is distinguished by “A canary node receives the intended change and the affected-node list matches the approved rollout scope”.

The option would apply to “A BCM cluster is ready for general users but no tenant can access the training filesystem from compute nodes”. A completed remediation must demonstrate that An approved user reads and writes expected project files within a scheduled task and receives consistent ownership. This question instead requires “A canary node receives the intended change and the affected-node list matches the approved rollout scope”.

The proposed validation does not isolate the reported fault. An effective closure test requires evidence that A canary node receives the intended change and the affected-node list matches the approved rollout scope.