Free NVIDIA NCP-AII Practice Exam with Questions & Answers | Set: 2

The output provided is a result of theNVIDIA System Management (NVSM)tool, specifically the nvsm show healthinfo command. NVSM is an essential diagnostic framework for NVIDIA DGX systems that monitors hardware health, identifies faults, and helps ensure the system remains within its validated operational state.

In this specific diagnostic trace, the system reports that the "Verify installed GPU's" check has returned a status ofUnhealthy. To provide a root cause, NVSM cross-references the live hardware enumeration from the lspci command against the system's known "Golden Configuration" (the hardware manifest defined in the firmware). The explicit error message,"Missing GPU at PCI address '07:00.0'", indicates that the system expects a GPU module to be present at that specific PCIe bus address, but the hardware is not responding or visible to the bus.

This insight allows a system administrator to conclude that aGPU is missingfrom the logical perspective of the system. This is a critical hardware fault rather than a software or driver issue. In a DGX H100 or A100 system, this could be caused by a physical module failure, a power delivery issue to that specific segment of the GPU baseboard, or a failure in the PCIe switch fabric. Because the DGX relies on a full set of 8 GPUs for high-speed collective communications (NCCL), a single missing GPU will prevent the node from participating in large-scale training jobs, requiring physical inspection or a GPU tray replacement (RMA).

Fraud detection in financial services is a real-time AI workload. The system must ingest transaction data, retrieve historical customer profiles, and perform inference in milliseconds. This requires a storage architecture that supportsmulti-protocol access(such as S3 for ingestion and POSIX/NFS for inference engines) combined withlow latency. In these environments, storage latency directly impacts the "Time to Decision". An All-Flash storage tier is mandatory, as traditional HDD solutions (Option D) or moderate speed systems (Option B) introduce "Tail Latency" that can cause the fraud detection model to time out during peak transaction windows. Additionally, multi-site synchronization ensures that the latest model weights and historical data are available across different geographic data centers for high availability and localized inference.

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.

When a DGX system exhibits high fan speeds and performance degradation, it is typically engaging inThermal Throttling. High-performance GPUs like the A100 or H100 will automatically reduce their clock speeds (and thus performance) if they exceed safe temperature thresholds. The first and most critical diagnostic step is to run nvidia-smi. This utility provides immediate, real-time telemetry on GPU temperatures, power draw, and "Clocks Throttle Reasons." By reviewing the output, an administrator can see if "Thermal" is listed as the reason for reduced clocks. This identifies whether the issue is environmental (blocked airflow/hot aisle temperature) or hardware-specific (a failed GPU thermal interface or a dead internal fan). Running more workloads (Option A) would exacerbate the heat, while a power drain (Option C) is a "last resort" that doesn't provide diagnostic data. nvidia-smi provides the evidentiary data needed to determine if an RMA (Return Merchandise Authorization) is required for the GPU tray.

The definitive "smoke test" for an NVIDIA-accelerated container environment is running nvidia-smi from within a container pulled from theNVIDIA 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.

The ibnodes utility is a specialized script within the infiniband-diags suite used for high-level topology mapping. When executed, it scans the InfiniBand subnet and provides a concise list of every active node connected to the fabric, categorized by their type. Specifically, it displays all Host Channel Adapters (HCAs/CA) found in the servers (the "hosts") and all InfiniBand switches. This command is an essential first step in fabric validation after a "bring-up" or expansion because it allows an engineer to quickly verify if the expected number of nodes and switches have successfully joined the fabric. Unlike ibnetdiscover, which provides a verbose and complex output of every port-to-port connection, ibnodes focuses on the identity and type of the devices. This distinction is critical for troubleshooting connectivity; if a server's HCA is missing from the ibnodes list, the engineer knows to investigate the physical link or the local HCA driver state rather than searching through thousands of lines of switch-to-switch cabling data.

Uneven GPU utilization in a multi-node cluster is a classic symptom ofPCIe/NUMA imbalance. In a DGX H100, each set of GPUs is physically closer to a specific CPU socket and a specific set of high-speed NICs. If the workload (HPL) is launched without strict affinity, an MPI rank running on a CPU core attached to Socket 0 might attempt to control a GPU attached to Socket 1. This forces data to cross the inter-processor links (UPI/QPI), which have significantly higher latency and lower bandwidth than a direct PCIe path. This "bottlenecking" causes some GPUs to wait for data longer than others, leading to the uneven utilization observed. The verified solution is to use an orchestration script or flags that enforceAffinity. By setting --gpu-affinity and --cpu-affinity, the administrator ensures that each GPU is managed by a CPU core on its local NUMA node. This alignment minimizes latency and ensures that every GPU in the cluster receives data at the same rate, resulting in the flat, high-utilization profile required for a successful HPL burn-in record.

The physical installation of high-performance NVIDIA components, such as H100 PCIe GPUs or BlueField DPUs, requires strict adherence to data center safety and hardware preservation standards. Option D is the only "100% verified" procedure because it covers three critical pillars: Power, Compatibility, and Safety. First, high-end GPUs can draw up to 300W-450W individually; verifying the server's PDU and internal PSU capacity is essential to prevent over-current shutdowns. Second, verifying cable compatibility (such as 12VHPWR or specific PCIe power 8-pin layouts) is vital to avoid electrical damage. Third, "Cold Service" (ensuring the server is powered down and cables are removed) is the standard for non-hot-plug PCIe components to prevent short circuits. Finally, wearing an ESD (Electrostatic Discharge) bracelet is non-negotiable when handling NVIDIA hardware, as static charges can destroy the sensitive HBM (High Bandwidth Memory) or the GPU die itself. Skipping ESD protection (as suggested in Option A) or performing the install while the system is "up and running" (as suggested in Option C) are leading causes of hardware infant mortality in AI infrastructure.

On systems where UEFI Secure Boot is enabled, the Linux kernel strictly enforces a "Signature Verification" policy for all loaded kernel modules. The NVIDIA driver consists of several modules (like nvidia.ko and nvidia-uvm.ko) that provide the interface between the hardware and the NVIDIA Container Runtime. If these modules are not signed by a key trusted by the system's firmware, the kernel will block them from loading, leading to "Permission Denied" errors when the container attempts to access /dev/nvidiactl or the GPU device nodes. To resolve this without compromising the security of the host, the administrator must utilize aMachine Owner Key (MOK). The modules must be signed using this key, and the key itself must be "Enrolled" into the system's Secure Boot database via the MOK management interface during the boot process. This establishes a "Chain of Trust" that allows the drivers to function. Disabling SELinux (Option C) or using sudo (Option D) will not resolve this, as the blockage is happening at the kernel-firmware interface level, not at the user-space permission level.

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.