Free NVIDIA NCP-AIN Practice Exam with Questions & Answers

To enable RDMA over Converged Ethernet (RoCE) on a Cumulus switch, the correct command is:​

nv set qos roce enable on

This command configures the Quality of Service (QoS) settings to support RoCE, ensuring that the necessary parameters for lossless Ethernet are applied.​

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."​

For optimal performance in multi-node, multi-GPU AI workloads:

NVLink provides high-speed, low-latency communication between GPUs within the same node.

InfiniBand offers efficient, scalable communication between nodes in a data center. Combining these technologies ensures both intra-node and inter-node communication needs are effectively met.​

AI workloads, particularly in large-scale training scenarios, are characterized by a small number of high-bandwidth, long-lived flows known as "elephant flows." These flows can dominate network traffic and are prone to causing congestion if not managed effectively.​

Traditional flow-based load balancing mechanisms, such as Equal-Cost Multipath (ECMP), distribute traffic based on flow hashes. However, in AI workloads with low entropy (i.e., limited variability in flow characteristics), ECMP can lead to uneven traffic distribution and congestion on certain paths.​

Adaptive routing techniques, which dynamically adjust paths based on real-time network conditions, are more effective in managing AI traffic patterns and mitigating congestion risks.​

In InfiniBand networks, Partitioning using Partition Keys (PKeys) is the standard method for implementing multi-tenancy and traffic isolation. PKeys allow administrators to define logical partitions within the fabric, ensuring that traffic is confined to designated groups of nodes. This mechanism is essential for creating secure and isolated environments in multi-tenant architectures.​

The Unified Fabric Manager (UFM) leverages PKeys to manage these partitions effectively, enabling administrators to assign and control access rights across different tenants. This approach ensures that each tenant's traffic remains isolated, maintaining both security and performance integrity within the shared fabric.​

In multi-subnet InfiniBand environments , AI training clusters are segmented across network zones (or subnets). Direct GPU-to-GPU communication (especially for collective ops like AllReduce, Broadcast, etc.) requires inter-subnet reachability. NCCL supports this via the InfiniBand Router (IB Router) feature.

From the NCCL User Guide – Environment Variables Section :

"NCCL_IB_USE_IB_ROUTER: Enables NCCL support for IB routers which are used in multi-subnet InfiniBand fabrics. When enabled, NCCL can traverse IB subnets using a properly configured IB router."

This is critical because without IB Router support:

NCCL would be restricted to intra-subnet GPU collectives.

Multi-node training across subnets would fail or fall back to slower TCP fallback mechanisms.

Technical Explanation:

IB Routers use subnet managers (like OpenSM with routing tables) to bridge communication across different InfiniBand partitions.

NCCL queries the subnet topology, discovers routing paths, and uses RDMA CM (Connection Manager) to establish GPU transport over routers.

This capability is especially important in data center-scale AI clusters spanning multiple racks or zones, connected via IB routers like Mellanox SB7800 or QM8700 series .

When NCCL_IB_USE_IB_ROUTER=1 is set:

NCCL includes router-aware route resolution in its path selection logic.

Enables efficient zero-copy communication across GPUs in different IB domains, maintaining low latency.

Other Options Explained:

A. Lazy connection establishment – controls when peer connections are made but does not enable cross-subnet reach.

B. GPU Direct RDMA – enables intra-node direct memory access, not applicable for routing across subnets.

C. Static plugin linking – affects how NCCL links plugins, not related to IB topology.

Exact Extract Reference:

Source: NVIDIA NCCL User Guide – Environment Variables Section

Extract: "NCCL_IB_USE_IB_ROUTER: Enables NCCL support for IB routers, required for multi-subnet InfiniBand configurations. Ensures proper routing of collectives over fabric-wide topologies."

The NVIDIA Spectrum-X Reference Architecture (RA) 1.0.1 is designed for Ethernet AI cloud deployments and includes the SN5600 Spectrum-4 switches and BlueField-3 SuperNICs. This architecture supports adaptive routing and DOCA programmable congestion control (PCC) for lossless RoCE traffic, optimizing performance for AI workloads.

The SN5600 switch offers 64 ports of 800GbE in a dense 2U form factor, providing high throughput and low latency essential for AI applications.

The correct answer is PXN (Peer eXchange Network) .

From the NVIDIA NCCL Documentation :

"PXN enables communication between GPUs connected via NVLink and NICs by treating the GPUs as a distributed switch. This architecture improves bandwidth utilization by enabling any GPU to communicate with the NIC via the shortest path available, even if it's not directly connected to the NIC."

This enhances GPU-to-NIC and NIC-to-GPU transfers, leveraging the NVLink topology. It significantly boosts performance in multi-GPU setups where not every GPU is directly connected to the NIC.

Other options:

Adaptive Routing is a fabric-level feature for dynamic path rerouting.

Graph Search Optimization is used internally for topology modeling in NCCL.

SHARP v2 is a switch-based collective acceleration method, unrelated to PXN.

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.

NVIDIA's What Just Happened (WJH) is a feature that provides real-time visibility into network problems by analyzing all packets passing through the switch and alerting on performance issues caused by packet drops, congestion, high latency, or misconfigurations.

WJH retains the last packets that were dropped from the switch with complete packet headers and the actual drop reason. This enhances the ability to debug network problems, identify affected flows, and decrease time-to-repair.