NVIDIA AI Infrastructure NCP-AII Exam Questions

Answer : A

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.

Answer : A

With the advent of the NVIDIA Container Toolkit and modern Docker versions (19.03+), the --gpus flag is the official, verified method for resource allocation. To restrict a container to specific hardware IDs, the syntax requires a specific string format: --gpus ''device=0,2''. This tells the NVIDIA Container Runtime to map only those specific physical GPU devices into the container's namespace. While environment variables like NVIDIA_VISIBLE_DEVICES (Option B) were used in older 'nvidia-docker2' setups, they are now considered legacy and can be overridden by the more modern --gpus flag. Option D is incorrect because simply mapping the device nodes (/dev/nvidiaX) is insufficient; the container also needs the appropriate volume mounts for the NVIDIA drivers and libraries, which the --gpus flag handles automatically. This precise isolation is critical in multi-tenant AI environments to ensure that a single developer or job doesn't accidentally utilize the entire 8-GPU tray of a DGX H100.

Answer : A, B

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 a running Kubernetes cluster (Option B) to host the services. Secondly, Run:ai utilizes Helm, 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, the control plane itself 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.

Answer : A

Updating firmware on an NVIDIA DGX cluster is a critical operation that involves multiple sensitive components, including the GPU baseboard, the BMC, the motherboard tray (SBC), and the InfiniBand HCAs. In a production environment, 'Batching' is the industry standard to prevent a single corrupted firmware image or update failure from taking down the entire AI factory. The process must begin with 'Draining' the nodes in the workload scheduler (like Slurm or Kubernetes) to ensure no active training jobs are interrupted. Running pre-update diagnostics---using tools like nvsm show health or dcgmi diag---is vital to establish a baseline and ensure the hardware is stable before applying changes. Once the firmware is applied in a controlled batch, post-update verification is required to confirm the system returns to a 'Healthy' state and that all versions match the target manifest. This 'Rolling Update' strategy allows the engineer to pause the automation if a specific node fails to return to service, protecting the overall availability of the cluster. Skipping diagnostics (Option D) or leaving nodes on mismatched versions (Option C) creates 'configuration drift,' which leads to unpredictable performance in collective communication libraries.

Answer : C

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.

Answer : D

In a large-scale Spectrum-X Ethernet fabric, 'East-West' traffic refers to the cross-rack communication between compute nodes. To validate the 'Bisectional Bandwidth' (the throughput between two halves of the cluster), administrators use NCCL tests with specific environment variables to control traffic patterns. The NCCL_TESTS_SPLIT variable is used to partition the GPUs into distinct groups for the benchmark. Setting NCCL_TESTS_SPLIT='DIV 8' is a standard configuration for multi-node testing on 8-GPU systems. It effectively divides the total number of GPUs by the node count, creating a test environment where each GPU communicates with its corresponding rank on other nodes. By combining this with -g 1 (one GPU per process) across multiple nodes, the engineer can force data to travel across the leaf-and-spine switches rather than staying within the NVLink fabric of a single node. This isolates the physical network performance from the internal GPU-to-GPU bandwidth, providing a true measurement of the fabric's ability to handle high-speed AI traffic.

Answer : C

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.