Free Practice Questions for NVIDIA NCP-AIN Exam

Virtual Routing and Forwarding (VRF) is the most effective method to achieve network segmentation and isolation in a multi-tenant environment.

From the NVIDIA Cumulus Linux Documentation – VRF Section :

"VRF allows multiple instances of routing tables to coexist within the same switch, effectively isolating traffic between tenants or departments."

Each department can:

Operate in its own VRF domain

Have independent routing tables

Maintain strict separation of Layer 3 paths

Incorrect Options:

A (Port Mirroring) – Used for traffic monitoring, not isolation.

C (ACLs) – Useful for fine-grained filtering, but not scalable tenant isolation.

D (LLDP) – Used for neighbor discovery, not security or isolation.

In NVIDIA Spectrum-X, congestion is evaluated based on egress queue loads. Spectrum-4 switches assess the load on each egress queue and select the port with the minimal load for packet transmission. This approach ensures that all ports are well-balanced, optimizing network performance and minimizing congestion.

The NVIDIA Spectrum-X networking platform is an Ethernet-based solution optimized for AI workloads, combining Spectrum-4 switches, BlueField-3 SuperNICs, and advanced software to deliver high performance and low latency. Gathering telemetry data is critical for optimizing Spectrum-X networks, as it provides visibility into network performance, congestion, and potential issues. The question asks for the tool used to collect telemetry data in a Spectrum-X network.

According to NVIDIA’s official documentation, NVIDIA NetQ is the primary tool for gathering telemetry data in Ethernet-based networks, including those running on Spectrum-X platforms with Cumulus Linux or SONiC. NetQ is a network operations toolset that provides real-time monitoring, telemetry collection, and analytics for network health, enabling administrators to optimize performance, troubleshoot issues, and validate configurations. It collects detailed telemetry data such as link status, packet drops, latency, and congestion metrics, which are essential for Spectrum-X optimization.

Exact Extract from NVIDIA Documentation:

“NVIDIA NetQ is a highly scalable network operations tool that provides telemetry-based monitoring and analytics for Ethernet networks, including NVIDIA Spectrum-X platforms. NetQ collects real-time telemetry data from switches and hosts, offering insights into network performance, congestion, and connectivity. It supports Cumulus Linux and SONiC environments, making it ideal for optimizing Spectrum-X networks by providing visibility into key metrics like latency, throughput, and packet loss.”

— NVIDIA NetQ User Guide

This extract confirms that option C, NetQ, is the correct tool for gathering telemetry data in a Spectrum-X network. NetQ’s integration with Spectrum-X switches and its ability to collect and analyze telemetry data make it the go-to solution for network optimization tasks.

From NVIDIA Performance Tuning Guide (ib_write_bw Tool Usage) :

"-S < SL > : Specifies the Service Level (SL) to use for the InfiniBand traffic. SL is used for setting priority and mapping to virtual lanes (VLs) on the IB fabric."

This flag is useful when testing QoS-aware setups or validating SL/VL mappings.

Incorrect Options:

A – No such flag for burst size.

B – -q defines number of QPs.

C – --rate or -R is used for rate-limiting.

MLNX_OFED (Mellanox OpenFabrics Enterprise Distribution) is an NVIDIA-tested and packaged version of the OpenFabrics Enterprise Distribution (OFED) for Linux. It provides the necessary drivers and tools to support InfiniBand and Ethernet interconnects using the same RDMA (Remote Direct Memory Access) and kernel bypass APIs. MLNX_OFED enables high-performance networking capabilities essential for AI clusters, including support for up to 400Gb/s InfiniBand and RoCE (RDMA over Converged Ethernet).​

Reference Extracts from NVIDIA Documentation:

"MLNX_OFED is an NVIDIA tested and packaged version of OFED that supports two interconnect types using the same RDMA (remote DMA) and kernel bypass APIs called OFED verbs – InfiniBand and Ethernet."​

"Up to 400Gb/s InfiniBand and RoCE (based on the RDMA over Converged Ethernet standard) over 10/25/40/50/100/200/400GbE are supported."​

The "What Just Happened" (WJH) service on Cumulus switches provides real-time visibility into network problems by monitoring various layers and components, including layer 1, layer 2, layer 3, tunnel, buffer, and Access Control List (ACL) related issues. WJH streams detailed and contextual telemetry data, enabling administrators to diagnose and troubleshoot network problems effectively.​

Reference Extracts from NVIDIA Documentation:

"WJH can monitor layer 1, layer 2, layer 3, tunnel, buffer and ACL related issues."​

"The WJH service enables you to diagnose network problems by looking at dropped packets."​

In DPU Mode , the ARM cores on BlueField own the NIC data path , while still allowing the host system to access the DPU OS (via OOB or virtio) .

From NVIDIA BlueField Documentation:

"In DPU Mode, the data path is offloaded to the BlueField Arm cores, enabling advanced security and networking functions, while still allowing host access to the BlueField OS."

This is different from:

NIC Mode : Data path controlled by host, ARM cores inactive.

Separated Host Mode : Complete isolation; host cannot access DPU OS.

Restricted Mode : Limited host access to DPU OS, but without full offload capabilities.

The mlxlink tool is used to check and debug link status and issues related to them. The tool can be used on different links and cables (passive, active, transceiver, and backplane). It is intended for advanced users with appropriate technical background.​

The tool specifically designed for testing InfiniBand connectivity is **ibping**. It functions similarly to the traditional ping utility but is optimized for InfiniBand fabrics .

From the NVIDIA InfiniBand Diagnostic Utilities Documentation :

"ibping tests the connectivity of InfiniBand nodes by sending management datagrams (MADs) and verifying the response from the destination LID or GUID."

Tests basic node-to-node reachability

Supports testing via LID, GUID , or port number

Helps verify subnet manager routing and fabric health

Incorrect Options:

ping and traceroute are IP-based, not fabric-aware.

ibnetdiscover maps topology but doesn't test live connectivity.

The MINHOP routing protocol, while efficient in finding minimal paths, does not inherently prevent credit loops. This can lead to deadlocks in the network. In contrast, routing protocols like UPDOWN and FAT TREE are designed to avoid such loops, ensuring more reliable network operation.​