NCP-AII NVIDIA AI Infrastructure Free Practice Exam Questions (2026 Updated)

The error " GPU fell off bus " is a critical failure where the PCIe link between the GPU and the CPU/PCIe Switch has collapsed, often due to thermal stress, power instability, or physical hardware defects. To isolate the root cause during an intensive workload like NVIDIA NeMo (Large Language Model framework), the administrator must collect high-fidelity telemetry. DCGM (Data Center GPU Manager) diagnostics are designed for exactly this scenario. By running dcgmi diag -r 3 (a comprehensive hardware stress test) or monitoring health via dcgmi health --check concurrently with the workload, the system can capture the exact moment parameters like PCIe replay counts, temperature spikes, or XID errors occur. This data allows the engineer to determine if a specific H100 module is faulty or if the issue is systemic (e.g., a failing PCIe switch on the motherboard). Lowering the workload (Option C or D) might hide the symptom, but it does not diagnose the hardware ' s inability to handle peak power and data throughput.

For 400G (NDR) InfiniBand and Ethernet links, signal integrity is managed through Forward Error Correction (FEC). While " Raw BER " accounts for errors before correction, the Effective BER (errors remaining after FEC) is the definitive metric for link stability. In a high-performance NVIDIA AI fabric, the Effective BER should ideally be zero. NVIDIA’s Cable Validation Tool (CVT) and Unified Fabric Manager (UFM) flag any link that shows an Effective BER greater than $1.5 \times 10^{-254}$ during standard monitoring periods. This specific threshold indicates that the FEC engine is working at its limit and cannot guarantee a " lossless " fabric. Unlike optical transceivers, Direct Attach Copper (DAC) cables do not have " Rx power " (Option A), as they are electrical, making BER the primary health indicator. A marginal cable failing this threshold will cause intermittent packet retransmissions, leading to massive performance degradation in NCCL collective operations.

The NVIDIA GPU Cloud (NGC) is the central repository for AI-optimized containers, pre-trained models, and specialized SDKs. To interact with the NGC registry via the command line, the ngc CLI must be authenticated to the user ' s account. The command ngc config set is the verified first step to configure these credentials. When this command is executed, the user is prompted to provide their API Key, which is generated from the NGC web portal. This configuration process creates a local config file (typically in ~/.ngc/config) that stores the authentication token, the preferred organization, and the team settings. Without running ngc config set, the CLI cannot authenticate requests to pull private containers or upload models. ngc init (Option B) is not a standard configuration command for the current NGC CLI architecture, and ngc config get (Option A) is only useful for viewing an existing configuration that has already been established.

Future-proofing AI storage requires balancing the massive throughput needs of training with the vast capacity needs of data lakes. A hybrid cloud model (Option C) is the most adaptable strategy because it allows organizations to maintain high-performance, low-latency " hot " data on-premises (near the DGX clusters) while leveraging the elastic, near-infinite scalability of cloud storage for " cold " archival data or sudden bursts in compute demand. This model supports data tiering, where active datasets live on NVMe-based local parallel file systems to saturate GPU memory, and older datasets migrate to lower-cost cloud object storage. While an all-flash array (Option A) is fast, it can become cost-prohibitive for multi-petabyte AI data lakes without a cloud-integrated tiering strategy. The hybrid approach provides the architectural flexibility to adopt new technologies over a five-year horizon without being locked into rigid on-premises hardware upgrade cycles.

The strongest indicator of a cable signal problem is repeated CRC errors combined with intermittent port flapping. CRC errors indicate corrupted frames at the link layer, often caused by poor signal integrity, damaged cables, bad transceivers, dirty optical connectors, excessive bend radius, marginal DAC quality, or unsupported media. Intermittent port flapping means the link repeatedly transitions down and back up, which strongly suggests a physical-layer instability rather than a higher-level application issue. Seeing the expected link speed in ifconfig is not enough to prove signal quality; a link can negotiate at the correct speed while still accumulating errors under load. Successful pings under 2 ms also do not validate high-speed fabric quality because ICMP traffic is lightweight and does not stress the link like RDMA, NCCL, or storage traffic. In NVIDIA AI clusters, physical-layer faults can severely affect distributed training because retransmissions, packet drops, and link resets create stragglers in collective communication. Cable validation should include switch counters, BER or FEC data where available, port stability, transceiver telemetry, and sustained workload or fabric testing.

The definitive " smoke test " for an NVIDIA-accelerated container environment is running nvidia-smi from within a container pulled from the NVIDIA GPU Cloud (NGC). Option D is the only 100% verified command because it includes all three necessary components:

--gpus all: This flag is required by the NVIDIA Container Toolkit to map the host ' s GPU device nodes and driver libraries into the container. Without it (as in Option C), the container will not " see " any GPUs.

nvcr.io/nvidia/cuda: Using an official CUDA base image from NGC ensures that the container has the necessary user-space libraries to communicate with the NVIDIA driver on the host.

nvidia-smi: This command specifically queries the driver and hardware. If it successfully prints the GPU table (showing the H100/A100 modules, their temperatures, and memory), it proves that the entire stack—from the physical hardware and kernel driver to the container runtime and toolkit—is functioning correctly.

Running ls -la (Option B) or systemctl (Option A) only tests that the container can run, but it does nothing to verify GPU accessibility or driver communication.

Firmware consistency is a pillar of stable InfiniBand fabric performance. When a cluster is expanded, new transceivers or cables may arrive with newer or older firmware than the existing base, leading to " FW Version Mismatch " alerts in management consoles like UFM (Unified Fabric Manager). The flint tool (or mstflint) is the correct utility for querying the specific firmware levels embedded within the transceivers. While iblinkinfo provides data on link speeds and port states, it does not provide the deep hardware-level firmware telemetry required for version validation. flint allows the administrator to query the device, compare the current burn version against the target image, and perform the necessary updates to bring the cluster into a uniform state. In NVIDIA AI infrastructure, maintaining uniform firmware across the fabric ensures that features like Adaptive Routing and Congestion Control operate predictably. Without version parity, inconsistent behavior in Forward Error Correction (FEC) or link-up negotiation can lead to intermittent performance drops that are difficult to diagnose at the application (NCCL) level.

The correct command is show asic-version. In NVIDIA Spectrum and Mellanox/NVIDIA switch environments, system software version alone does not prove that all switch modules or ASIC-related firmware components are aligned. NVIDIA documentation states that after firmware updates, administrators should run show asic-version; this command lists switch modules with their firmware versions and should be checked to ensure versions match the expected default or approved firmware baseline. show version is useful for the operating system or software image level, but it does not provide the same module-level ASIC firmware validation. show interfaces status confirms port state, but ports can be up even when firmware is inconsistent or unsupported. show inventory is helpful for asset identification and serial numbers, but it is not the primary firmware-compliance command. During AI cluster bring-up, switch firmware consistency matters because inconsistent module firmware can cause unpredictable link behavior, degraded fabric performance, or supportability issues before NCCL, RDMA, or Spectrum-X workload validation.

The storage system should prioritize multi-protocol data access with low latency. Fraud detection workloads often depend on near-real-time inference, rapid lookup of transaction history, feature retrieval, and integration across multiple systems or sites. In an NVIDIA AI infrastructure environment, storage must support the AI workflow without starving GPUs, inference servers, or analytics pipelines. Multi-protocol access allows different applications and environments to access data through suitable interfaces, such as file or object protocols, while maintaining interoperability across on-premises and cloud-connected platforms. Low latency is essential because fraud decisions are time-sensitive; delayed data access can reduce model usefulness or prevent immediate action. Tape backup systems are useful for archival retention but are not suitable for live inference or fast analytics. Low-cost HDD-only storage may provide capacity but usually cannot meet latency and throughput requirements. High capacity with moderate speed is also insufficient when the business requirement is rapid retrieval across sites. For production AI operations, storage should be designed for responsiveness, availability, protocol compatibility, and consistent performance under concurrent workload demand.

The ib_write_lat test is used to check low-level RDMA write latency between two nodes in an InfiniBand fabric. In NVIDIA AI infrastructure, latency validation is important because distributed training workloads depend on fast GPU-to-GPU synchronization across servers. Operations such as all-reduce, reduce-scatter, and parameter synchronization are sensitive to delay, especially as the number of nodes increases. The ib_write_lat utility is part of the RDMA perftest toolset and is commonly used during fabric validation to confirm that adapters, switches, cabling, routing, firmware, and Subnet Manager configuration are working correctly. ib_read_bw measures RDMA read bandwidth, not latency. ib_write_bw measures RDMA write bandwidth, not the lowest latency behavior. ib_read_lat measures read latency, but write latency is commonly used as a practical low-level latency check for RDMA fabric health. Consistently low and stable ib_write_lat results help confirm that the fabric is ready for higher-level validation with NCCL, HPL, and distributed AI workload tests.

NVIDIA Spectrum-X is the world’s first high-performance Ethernet fabric designed specifically for AI, combining Spectrum-4 switches with BlueField-3 SuperNICs. To achieve the high-throughput, low-latency requirements of East-West (server-to-server) AI traffic, the BlueField-3 hardware must be correctly provisioned. The first requirement is ensuring the physical ports are operating in Ethernet mode; LINK_TYPE_P1=2 (and P2=2 for the second port) toggles the hardware from InfiniBand to Ethernet mode. Secondly, the BlueField-3 can operate in several " modes. " While " DPU mode " (Option D) offloads the entire OS to the ARM cores, " NIC mode " (or SuperNIC mode) allows the host to manage the networking while leveraging the Internal CPU Offload Engine. Setting INTERNAL_CPU_OFFLOAD_ENGINE=1 is a specific configuration step for Spectrum-X that allows the SuperNIC to handle RoCE (RDMA over Converged Ethernet) and Congestion Control (CC) algorithms more efficiently at 400G speeds. This setup is vital for AI workloads like LLM training, where consistent latency and zero-packet-loss are non-negotiable for collective communications.

NVIDIA NeMo and large language model (LLM) training workloads are extremely demanding on HBM (High Bandwidth Memory). Out-of-Memory (OOM) errors often occur not because the total dataset is too large, but because memory fragmentation or sudden spikes in allocation (spikes during data shuffling or batch loading) exceed the available GPU memory. To mitigate this during intensive burn-in tests, engineers utilize the RMM (RAPIDS Memory Manager) library, which provides an asynchronous allocator. Enabling RMM asynchronous allocation allows the system to pre-allocate a pool of memory and manage it more efficiently than the standard CUDA allocator, reducing the overhead of constant allocations and deallocations. Furthermore, setting a specific blocksize (e.g., 1GB) for data loading ensures that the data ingestion pipeline reads data in manageable, deterministic chunks. This prevents the system from attempting to load massive files entirely into memory at once, which is the primary cause of OOMs in question-answering tasks involving large Parquet or JSON datasets. Switching to FP32 (Option B) would actually double the memory footprint and increase the likelihood of an OOM error.

Managing a large-scale AI fabric requires centralized visibility into the physical layer. The NVIDIA Unified Fabric Manager (UFM) provides a comprehensive Dashboard for InfiniBand networks. To check transceiver firmware—which is critical for ensuring feature parity and stability across the fabric—the administrator can use the UFM Enterprise GUI. By navigating to the " Devices " section and selecting a specific switch, the " Cables " tab will aggregate telemetry for every occupied port. This view displays the manufacturer, part number, and the specific firmware version of the transceivers (LinkX) or Active Optical Cables (AOC). This consolidated view is far more efficient than manual CLI queries (Option C) for 200+ ports. Maintaining uniform firmware across transceivers ensures that optimizations like Adaptive Routing and Congestion Control perform consistently across the entire 400G or 200G fabric.

The correct command sequence is sudo apt-get purge nvidia-* & & sudo apt-get autoremove. Purging removes NVIDIA driver packages and their configuration files, while autoremove removes dependency packages that were installed automatically and are no longer required. NVIDIA’s current data center driver removal guidance for Ubuntu 22.04 and 24.04 uses apt remove --autoremove --purge with NVIDIA-related package patterns, including driver, Fabric Manager, firmware, headless, DKMS, compute, decode, encode, and related libraries. A simple apt-get remove nvidia-driver-550 removes only one package and may leave DKMS modules, libraries, configuration files, Fabric Manager packages, or version-specific dependencies behind. Manually deleting /usr/lib/nvidia is unsafe because it bypasses package management and can leave the system in an inconsistent state. ubuntu-drivers uninstall is not the most complete answer for fully purging all NVIDIA driver components during conflict troubleshooting. After removal, administrators should verify loaded modules, package state, and reboot before installing the intended validated driver stack. Clean removal is important in AI infrastructure because driver conflicts can break CUDA, NCCL, DCGM, Fabric Manager, and container runtime behavior.

The correct command is sudo nvsm stress-test --force. NVIDIA recommends using NVSM for the DGX pre-flight stress test before putting a DGX H100 system into production or after servicing. The documented NVSM stress test can run checks across supported components, including GPUs, CPU, memory, and storage, and the recommended command for all supported components is sudo nvsm stress-test --force. nvidia-smi -q provides detailed GPU information, but it does not execute a full platform stress test. The Linux stress command can load CPU and I/O subsystems, but it is generic and does not validate the DGX platform using NVIDIA’s health model. gpu_burn may stress GPUs, but it does not cover CPU, system memory, storage, and DGX-specific platform checks in the recommended way. During server bring-up, NVSM is preferred because it understands DGX hardware components and can identify platform health issues before the node is released to production workloads.

The correct best practice is to install only the GPU and DOCA driver versions that are validated for the current operating system, kernel, hardware platform, and NVIDIA software release. In NVIDIA AI infrastructure, driver compatibility is critical because GPU drivers, CUDA libraries, DCGM, Fabric Manager, DOCA-OFED, network adapters, DPUs, and kernel modules must align. Installing the newest driver without checking compatibility can cause driver/library mismatches, failed nvidia-smi, broken RDMA, or unsupported DOCA behavior. NVIDIA DGX documentation notes that DGX OS updates include coordinated OS, kernel, GPU driver, CUDA toolkit, and DCGM updates, and NVIDIA AI Enterprise provides support matrices to confirm supported platform combinations. DOCA-OFED is also tied to the operating system and kernel environment, so version selection must be deliberate. Legacy drivers may lack required fixes or hardware support, and default distribution drivers are usually not sufficient for validated DGX or AI Enterprise deployments. After installation, administrators should reboot if required, validate GPU visibility, confirm networking driver status, and run health checks before returning the node to production.

NVIDIA ' s Cable Validation Tool (CVT) and the Unified Fabric Manager (UFM) use strict Bit Error Rate (BER) thresholds to ensure the stability of NDR (400G) and HDR (200G) InfiniBand fabrics. Because modern high-speed links rely on Forward Error Correction (FEC) to fix minor bit flips, a " Raw BER " (errors before FEC) is expected, but must remain within a specific envelope—typically better than $10^{-12}$. However, the " Effective BER " (errors after FEC) should ideally be zero or incredibly low (less than $1.5 \times 10^{-254}$) over a long observation window. If these thresholds are exceeded within a standard 6-hour monitoring period, it indicates that the signal-to-noise ratio is too low for the FEC to maintain a reliable stream. This leads to packet drops and " Symbol Errors " that trigger InfiniBand " Retransmissions, " which are catastrophic for the performance of AI collectives like all_reduce. While Rx power variance (Option A) and temperature (Option D) are health indicators, they are causes of poor BER, not the BER threshold itself.

The first hardware check should be cable compatibility and connector inspection. A “No Signal” result from the Cable Validation Tool indicates that the physical layer is not establishing a usable signal, even though the cable appears to be inserted. In DGX H100 and NVIDIA high-speed networking environments, DAC cables must be validated for the correct speed, adapter generation, switch platform, firmware compatibility, and physical form factor. A damaged connector, unsupported cable, poorly seated latch, excessive bend radius, or wrong cable type can cause intermittent “Link Down” events. Replacing an optical transceiver is not appropriate because the issue is on a DAC connection, not an optical link. Reconfiguring the port to 100G may mask the failure but does not validate the required 200G operation. Upgrading all switches for RS-FEC is too broad and does not address a local “No Signal” condition. Proper physical-layer bring-up requires confirming the cable is supported, visually inspecting both ends, reseating it, and checking whether the link comes up cleanly before moving to firmware or switch-level troubleshooting.

In NVIDIA Base Command Manager (BCM), the management and storage traffic often requires redundancy via NIC bonding (Link Aggregation). The cmsh utility uses a hierarchical command structure to modify node configurations. To create a bond, the administrator must first navigate to the specific node ' s interface configuration (device use < node > ). The correct sequence involves adding a new interface of type " bond " (interfaces add bond bond0). After the bond object is created, the physical slave interfaces must be associated with it using the append interfaces command. Finally, the bonding mode (e.g., Mode 1 for Active-Backup or Mode 4 for LACP) and the logical network assignment must be defined. Option B correctly follows this logic. Assigning networks directly to physical ports (Option C) would prevent the use of a unified bond IP, and Option A incorrectly attempts to add a VLAN before the underlying bond is established. This configuration is essential for ensuring the control plane remains reachable even if a single management cable or switch port fails.