Free NVIDIA AI Infrastructure NCP-AII Exam Questions

Modern NVIDIA BlueField DPUs include an integrated Baseboard Management Controller (BMC) that supports the industry-standard Redfish API for out-of-band management. While CLI tools like mlxconfig (Option A) or mstflint (Option C) can be used from the host OS to check the NIC firmware, they cannot easily query the BMC-specific components like the ARM Trusted Firmware (ATF), the Board Support Package (BSP), or the UEFI bootloader of the DPU. The Redfish standard specifies a common URI for hardware inventory. The FirmwareInventory endpoint (Option D) is the correct RESTful path to retrieve a comprehensive JSON object containing the versioning details for all firmware-controllable components on the DPU. This is the preferred method for automated data center management systems (like NVIDIA Base Command Manager) to verify that DPUs are at the correct 'Golden Image' version during the staging phase. Note that 'FirmwareList' (Option B) is not a standard Redfish URI for this specific data.

High-Performance Linpack (HPL) is the standard benchmark for stress-testing the computational stability and thermal endurance of an AI cluster. It solves a massive dense system of linear equations, and its mathematical configuration is highly sensitive. The HPL.dat configuration file defines the Problem Size ($N$) and the Block Size ($NB$). A fundamental requirement of the HPL algorithm is that the workload must be distributed evenly across the MPI processes and GPU threads. If the total matrix size $N$ is not an exact multiple of the block size $NB$, or if the grid dimensions ($P \times Q$) do not align with the hardware topology, the solver may encounter an 'illegal value' error or a 'residual too large' failure at the very beginning of the run. This is a configuration error, not a hardware fault. Reducing the precision (Option A) would invalidate the test, as HPL must run in FP64 to be considered a standard 'burn-in.' Verifying that $N$ is divisible by $NB$ ensures the mathematical integrity of the test while allowing the hardware to be pushed to its theoretical performance limits.

In an InfiniBand fabric, the Subnet Manager (SM) is the 'brain' of the network, responsible for discovering the topology, assigning Local Identifiers (LIDs), and calculating routing tables. In a multi-node fabric, there is typically one Master SM and several Standby SMs for high availability. To identify the master, the sminfo command is first used; it queries the fabric and returns the LID of the current Master SM. Once the LID is obtained, the engineer must map that numerical LID to a physical server name or Node Description. The smpquery ND (Node Description) command is then executed, targeting that specific LID. This sequence is vital for troubleshooting fabric-wide issues, as logs on the Master SM server provide the definitive record of sweeps, traps, and topology changes. Using smpquery NI (Node Info) would provide hardware-level details like the GUID and device ID, but it does not return the human-readable string (server name) defined in the Node Description, which is necessary for rapid identification in a crowded data center.

Scaling an AI cluster to 256 GPUs (32 nodes of DGX H100) creates a massive 'Incast' problem for the storage fabric. During large-scale training, every node frequently reads huge batches of data simultaneously. NVIDIA's reference architectures (BasePOD/SuperPOD) specify that for high-performance training, each node must be able to sustain a minimum throughput---often 8 GiB/s or more---to keep all 8 GPUs saturated. If the storage system can handle one node at high speed but chokes when all 32 nodes request data, the 'Scaling Efficiency' of the AI model will drop drastically as GPUs sit idle waiting for IO. Therefore, validating consistent per-node throughput under full cluster load is the most critical metric for an AI Factory. While IOPS (Option D) are important for small files, modern AI datasets are often sharded into large binary formats (like WebDataset or TFRecord) where sequential throughput becomes the primary bottleneck.

In large-scale InfiniBand fabrics, such as those in NVIDIA DGX SuperPODs, maintaining an exact cabling topology is mandatory for the Adaptive Routing and Fat-Tree algorithms 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.

UEFI Secure Boot is a security standard that ensures only digitally signed code is allowed to execute during the boot process. Since NVIDIA GPU drivers include kernel modules (nvidia.ko), they must be signed by a key trusted by the system's firmware. When drivers are installed on a DGX system with Secure Boot active, the installation process generates a unique Machine Owner Key (MOK). However, the Linux kernel will not trust this key until the user manually authenticates it at the 'Shim' level before the OS loads. Upon the first reboot after installation, the system enters the 'MOK Management' blue screen. The administrator must select 'Enroll MOK' and enter the temporary password created during the driver installation. Failing to do this results in the kernel rejecting the nvidia module, leading to an 'Unable to determine the device handle for GPU' error in nvidia-smi. Disabling Secure Boot (Option A) would resolve the symptom but violates the security posture of the AI infrastructure.

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.

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 a Machine 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.

On an NVIDIA DGX system, the Baseboard Management Controller (BMC) is an independent processor that runs even if the main CPU and Operating System fail to load. If a server reboots and the administrator can access the BMC web interface or IPMI console, but the OS (Ubuntu/DGX OS) does not load, the most likely cause is a boot disk failure. The DGX H100 uses NVMe drives in a RAID-1 configuration for the OS boot volume. If both drives in the mirror fail, or if the boot partition becomes corrupted, the system will hang at the BIOS or UEFI prompt, unable to find a bootable device. While failed power supplies (Option D) or network links (Option A) can cause issues, they would typically prevent the BMC from being reachable at all or prevent remote network traffic respectively. A GPU failure (Option C) would not stop the OS from booting; the system would simply boot with a degraded GPU count. Therefore, checking the storage health via the BMC 'Storage' logs is the correct diagnostic step.

While object storage is excellent for massive scale and metadata, NVIDIA AI infrastructure best practices for training workloads---especially video analysis---heavily prioritize Parallel File Systems (PFS). Modern AI frameworks (PyTorch, TensorFlow) and NVIDIA's own SDKs (like DeepStream or NeMo) are optimized to read from POSIX-compliant file systems. For video content analysis, the training process involves 'sharding' large video files and performing random-access reads across a massive dataset. A high-performance file system (such as Lustre, Weka, or IBM Storage Scale) provides the high throughput and low-latency metadata operations required to keep 8 or more H100 GPUs per node saturated with data. File storage allows for the hierarchical organization that data scientists use to manage datasets (e.g., /datasets/train/videos/) and supports GPUDirect Storage (GDS), which allows the GPU to pull data directly from the storage fabric into GPU memory, bypassing the CPU to maximize ingestion throughput.