Free Practice Questions for NVIDIA NCP-AII Exam

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.

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.

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.

The correct answer is to ensure stability, bandwidth, and compatibility across the cluster. In high-speed NVIDIA AI fabrics, optical transceivers and active cables are not passive details; they participate in link training, signal quality behavior, firmware-controlled operation, diagnostics, and compatibility with switches and adapters. If transceiver firmware versions are inconsistent across a fabric, links may negotiate differently, report inconsistent telemetry, show intermittent errors, or underperform under sustained workloads. This matters greatly for AI training because NCCL collectives are sensitive to latency, retransmissions, and bandwidth variation. While inventory reporting is useful, it is not the main reason to align firmware. Heterogeneous transceiver firmware is not desirable simply for discovery, and it can make troubleshooting harder. GPU memory consumption is unrelated to switch transceiver firmware. During physical-layer validation, engineers should confirm supported transceiver models, firmware versions, link speed, error counters, BER health, and port stability before approving the fabric for production. Firmware alignment helps create a predictable and supportable baseline across the entire AI cluster.

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.

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.