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

Managing a large-scale AI fabric requires centralized visibility into the physical layer. The NVIDIAUnified 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.

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 theInternal 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.

Interpreting NCCL (NVIDIA Collective Communications Library) results requires understanding the difference between theoretical link rate and effective bus bandwidth. A 400G (NDR) InfiniBand link has a theoretical unidirectional capacity of 50 GB/s. In an 8-GPU DGX system, where each GPU is typically mapped to its own 400G HCA, the aggregate theoretical bandwidth is 400 GB/s. However, NCCL performance benchmarks reportBus Bandwidth, which accounts for the mathematical overhead of collective operations like all_reduce. Achieving350 GB/s(Option A) is widely considered optimal and representative of a healthy, well-configured fabric. This indicates that the system is effectively utilizing GPUDirect RDMA to bypass host memory and that the network switches are routing traffic without significant congestion or packet drops. Expecting >390 GB/s (Option C) is unrealistic once protocol headers and algorithmic overhead are subtracted from the raw bit rate. Rerunning with CPU stress (Option D) would not provide insights into the InfiniBand/GPU fabric health.

NVIDIA Base Command Manager (powered by Bright) relies on a High Availability (HA) pair of head nodes to ensure the AI factory remains operational if the primary controller fails. The cmsh (Bright Shell) is the definitive management interface for this stack. Running the status command within cmsh provides a real-time summary of the cluster’s health, specifically identifying which head node currently holds the "Active" role and which is in "Standby." It also monitors the status of the heartbeat and the synchronization of the database (MariaDB/MySQL). While nvsm (Option B) is essential for DGX hardware health, it does not manage the logic of the Bright Cluster Manager software. Checking connectivity via ping (Option D) only confirms network reachability but does not verify that the management services (CMDaemon) are actually ready to perform a stateful failover. Thus, cmsh status is the only verified way to confirm that the control plane's redundancy logic is active.

When evaluating NVIDIA Collective Communications Library (NCCL) performance, it is vital to distinguish betweenAlgorithm BandwidthandBus Bandwidth. For an all_reduce operation, the Bus Bandwidth represents the effective data transfer rate across the hardware links, which includes the overhead of the ring or tree collective algorithm. In an NDR (400G) InfiniBand fabric, the theoretical peak per link is 50 GB/s (unidirectional). In a 64-GPU cluster (8 nodes of 8 GPUs), achieving a bus bandwidth of 656 GB/s indicates that the fabric is efficiently utilizing the multiple 400G rails available on the DGX H100. This result is considered optimal as it reflects near-line-rate performance when accounting for network headers and synchronization overhead. Algorithm bandwidth is naturally lower because it represents the "useful" data moved from the application's perspective. If the bus bandwidth were significantly lower, it would suggest congestion, cable faults, or sub-optimal routing.

For 400G (NDR) InfiniBand and Ethernet links, signal integrity is managed through Forward Error Correction (FEC). While "Raw BER" accounts for errors before correction, theEffective 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-smi (NVIDIA System Management Interface) utility is the primary tool for monitoring and managing the state of NVIDIA GPUs. When a node exhibits "jitter" or lower performance compared to its peers in a cluster, nvidia-smi provides the necessary granular data to identify the bottleneck. It reports critical metrics such as GPU utilization percentages, memory usage, and, most importantly, "Clocks Throttle Reasons." If a GPU is running slower due to power capping, thermal issues, or a hardware error (like an uncorrectable ECC error), nvidia-smi will display this state immediately. While lspci (Option A) can confirm if the GPU is physically visible on the PCIe bus, it cannot provide any telemetry regarding its operational performance or health. iblinkinfo (Option D) is a network-level tool that only monitors InfiniBand link states. In an AI infrastructure context, nvidia-smi is the first-line diagnostic to determine if a GPU is "healthy" and operating at its intended clock speeds.

The ibstat command is a fundamental diagnostic tool in the NVIDIA InfiniBand stack used to query the status of local Host Channel Adapters (HCAs). In the provided output, the most critical data points are the Physical state, the State, and the SM lid.

The Physical state: Linkup confirms that the electrical or optical connection between the server's HCA and the neighboring switch port is established and healthy at the physical layer. This immediately rules out a disconnected cable (Option D) or a completely dead hardware port (Options A and C). However, the State: Initializing indicates that while the "wires" are connected, the logical InfiniBand protocol has not finished its handshake.

In an InfiniBand fabric, the Subnet Manager (SM) is the centralized "brain" responsible for discovering nodes, assigning Local Identifiers (LIDs), and configuring routing tables. The output shows Base lid: 0 and SM lid: 0, which signifies that the port has not been assigned a LID and cannot find an active Subnet Manager to talk to. Without a running SM to transition the port from "Initializing" to "Active," no RDMA traffic can pass through the fabric. This scenario typically occurs if the SM service has crashed on the management node, or if the SM is disabled on the managed switches. Therefore, the root cause is the absence of an operational Subnet Manager in the fabric to complete the logical link initialization.

In large-scale InfiniBand fabrics, such as those in NVIDIA DGX SuperPODs, maintaining an exact cabling topology is mandatory for theAdaptive RoutingandFat-Treealgorithms to function correctly. A "Wrong-neighbor" error occurs when the Unified Fabric Manager (UFM) detects that a cable is connected to a port other than the one specified in the master topology map (often a .csv or .topology file). UFM uses LLDP (Link Layer Discovery Protocol) or Subnet Management packets to identify the GUIDs on both ends of a link. The most efficient remediation is to cross-reference the live LLDP data provided by UFM with the intended design. This allows the engineer to identify if the error is a physical mis-cabling (swapped ports) or a logical error in the topology file. Rebooting switches (Option A) will not fix a physical patch error, and disabling FEC (Option D) would lead to catastrophic signal loss on 400G (NDR) links without addressing the underlying routing logic issue. Correcting the physical patch or updating the topology file ensures the fabric's "Ground Truth" is restored.

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.

High-Performance Linpack (HPL) is a memory-intensive benchmark that allocates a large portion of available GPU memory to store the matrix $N$. While a server may have 2TB of physical system RAM, the "not enough memory" error usually refers to theHBM (High Bandwidth Memory)on the GPUs themselves. In a DGX H100 system, each GPU has 80GB of HBM3. If the problem size ($N$) specified in the HPL.dat file is too large, the required memory for the matrix will exceed the aggregate capacity of the GPU memory. Reducing the problem size ($N$) while maintaining the optimal block size ($NB$) ensures that the problem fits within the GPU memory limits while still pushing the computational units to their peak performance. Increasing the block size (Option C) would actually increase the memory footprint of certain internal buffers, potentially worsening the issue. Reducing $N$ is the standard procedure to stabilize the run during the initial tuning phase of an AI cluster bring-up.

"GPU-Host latency" issues in NVIDIA DGX or HGX systems are frequently caused by incorrect PCIe affinity or sub-optimal NUMA (Non-Uniform Memory Access) mapping. If a GPU is forced to communicate with a CPU core or an HCA that is not on its local PCIe switch/root complex, latency increases significantly as data must cross the QPI/UPI inter-processor links. The command nvidia-smi topo -m provides a detailed matrix of the system's internal topology, showing how GPUs, CPUs, and NICs are connected. It identifies whether the connection is via a single PCIe switch (PIX), multiple switches (PXB), or across the CPU (SYS). By inspecting this map, an administrator can identify if a software process is pinned to the wrong NUMA node or if a hardware path is unexpectedly degraded. While DCGM (Option C) is good for checking component health, it doesn't map the logical-to-physical affinity paths that cause specific latency "threshold" warnings.

When deploying NVIDIA vGPU on VMware ESXi, the NVIDIA driver provides several scheduling policies to determine how GPU physical resources are shared among multiple virtual machines. The default behavior is often the "Best Effort" scheduler, but for environments requiring predictable performance across all users, the "Equal Share" scheduler is preferred. This scheduler gives each vGPU an equal "time slice" of the physical GPU's engines. The configuration is managed via module parameters passed to the nvidia kernel driver during host boot. The specific registry key for this behavior is RmPVMRL. Setting RmPVMRL=0x01 enables the Equal Share scheduler (Option A). Conversely, 0x00 would revert to the default time-sliced behavior. It is critical to use system module parameters set to ensure the setting persists across reboots and is applied globally to the NVIDIA driver stack. This ensures that no single "noisy neighbor" VM can monopolize the GPU cycles, which is a common requirement in shared AI research labs or virtual desktop infrastructures where consistency is more important than raw peak throughput of a single task.

NVIDIA DGX BasePOD and SuperPOD reference architectures mandate strict network segmentation to ensure performance, security, and manageability.

Compute Network: Typically InfiniBand (or high-speed Spectrum-X Ethernet), dedicated solely to GPU-to-GPU collective communications (NCCL).

Storage Network: A high-bandwidth Ethernet or InfiniBand fabric specifically for data ingestion and model checkpointing, often utilizing GPUDirect Storage (GDS).

Management Network: Used for standard cluster administration, SSH, and software orchestration (e.g., Bright Cluster Manager or Kubernetes control plane traffic).

Out-of-Band (OOB) Network: A physically isolated network connected to the BMC ports for low-level system monitoring, power control, and remote console access, even when the OS is down.

A single VLAN (Option A) would cause massive congestion during training, as storage and management traffic would compete with high-frequency compute packets. The four-network model ensures that a "storm" in the storage fabric does not prevent an administrator from accessing the system via the management or OOB networks, which is essential for maintaining an AI Factory at scale.

For the "North-South" and "Management/Storage" Ethernet fabrics in an NVIDIA AI Factory, high availability is paramount. Unlike the InfiniBand compute fabric, which uses its own routing logic, the Ethernet side relies on standard data center protocols. To provide true hardware redundancy and double the available bandwidth (Load Balancing), NVIDIA recommendsMLAG (Multi-Chassis Link Aggregation). MLAG allows two physical switches to appear as a single logical unit to the DGX nodes. The DGX can then bond its two Ethernet NICs (e.g., in an 802.3ad LACP bond) and connect one cable to each switch. This configuration provides several benefits: if one switch fails, the traffic seamlessly stays on the other link without the slow convergence times associated with Spanning Tree Protocol (Option A). Furthermore, it allows the cluster to utilize the combined bandwidth of both links for heavy storage traffic (like NFS or S3 ingestion). Using a single switch (Option C) or unmanaged hardware (Option D) creates single points of failure and lacks the traffic isolation (VLANs) required for secure AI infrastructure.

During the initial "first boot" setup of an NVIDIA DGX system (such as the DGX H100 or A100), the installation wizard requires the creation of a primary administrative user. This account is pivotal because it is used not only for local OS login but is also synchronized to provide access to the Baseboard Management Controller (BMC) and the GRUB bootloader. NVIDIA best practices emphasize security by mandating the use of a unique, strong password. Using a lower-case username is a standard Linux convention that ensures compatibility across various authentication services. By setting this up correctly during the first boot, the system ensures that "out-of-band" management (via BMC) and "pre-boot" configuration (via GRUB) are protected from unauthorized access. Relying on default credentials (Option B) or weak passwords (Option D) is a significant security risk in AI infrastructure, as the BMC often has high-level control over power, firmware, and remote console access.

NVIDIA Run:ai is an advanced orchestration platform designed to optimize GPU resource allocation within Kubernetes environments. Because Run:ai is cloud-native, its control plane and worker agents are deployed as Kubernetes resources. Therefore, the absolute first prerequisite is arunning Kubernetes cluster(Option B) to host the services. Secondly, Run:ai utilizesHelm, the package manager for Kubernetes, to manage its complex installation charts, deployments, and service configurations. Without Helm installed on the administrative machine (Option A), the installation scripts will fail to execute. While having GPUs (Option C) is the ultimate goal for the worker nodes, thecontrol planeitself can be installed on a cluster before all GPU hardware is physically present. Disabling NTP (Option D) is never recommended; in fact, accurate time synchronization is vital for the TLS certificates and logging used by Run:ai and Kubernetes.

In an NVIDIA DGX BasePOD or SuperPOD environment, "Cluster Health" is a binary state: either the entire fabric and all compute resources are ready, or the cluster is considered degraded. Using the Bright Cluster Manager (BCM) shell (cmsh), administrators can aggregate telemetry from every node in the cluster. For a system to be considered "Production Ready," every single GPU across the multi-node deployment must report a status of Health = OK. This verification ensures that the hardware is communicating correctly over the PCIe bus, the NVLink fabric is initialized, and no ECC (Error Correction Code) memory errors are present. If even a single GPU in a 32-node cluster is unhealthy, collective communication libraries like NCCL may hang or experience significant performance penalties during "All-Reduce" operations, as the entire job typically scales to the speed of the slowest/unhealthiest component. Therefore, seeing Status_Health = OK for every device is the mandatory exit criterion for the bring-up phase.

In a Bright Cluster Manager HA setup, the database (MySQL/MariaDB) must remain perfectly synchronized between the active and standby head nodes to allow for a seamless transition. This synchronization typically occurs over a dedicated management or heartbeat network. If cmsh status shows the database service as [FAIL] on the secondary node, it almost always points to a communication breakdown. Without a stable network path, the secondary node cannot receive the binary logs from the primary node to keep its local copy up to date. While licensing (Option A) is important, a license failure usually disables management capabilities entirely rather than just the MySQL sync. Furthermore, head nodes are management servers and do not require GPU drivers (Option C) for their primary function. Ensuring low-latency, reliable connectivity between the two head nodes is the primary troubleshooting step for resolving "MySQL FAIL" states in BCM.