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.

The correct answer is ngc config set --org org-name --ace ace-name. NGC CLI uses configuration context to determine which organization, team, or entitlement scope the user is operating in. When users belong to multiple organizations, the CLI must be configured with the intended organization context so that registry access, model downloads, private containers, and enterprise software resources resolve correctly. NVIDIA documentation shows ngc config set as the command used to configure or switch NGC context, including organization and team values, and other NVIDIA installation workflows show NGC configuration prompting for organization, team, and ACE fields. Manually editing JSON configuration files is not the recommended operational method because it increases the risk of syntax errors and inconsistent authentication state. ngc registry login is not the normal command for setting persistent NGC CLI organization context. Exporting an environment variable may influence a session, but it is not the best persistent configuration method. In AI infrastructure operations, correct NGC configuration is important for pulling validated containers, GPU drivers, vGPU software, models, and enterprise assets from the correct account scope.

NVIDIA ' s Cable Validation Tool (CVT) and the Unified Fabric Manager (UFM) use strict Bit Error Rate (BER) thresholds to ensure the stability of NDR (400G) and HDR (200G) InfiniBand fabrics. Because modern high-speed links rely on Forward Error Correction (FEC) to fix minor bit flips, a " Raw BER " (errors before FEC) is expected, but must remain within a specific envelope—typically better than $10^{-12}$. However, the " Effective BER " (errors after FEC) should ideally be zero or incredibly low (less than $1.5 \times 10^{-254}$) over a long observation window. If these thresholds are exceeded within a standard 6-hour monitoring period, it indicates that the signal-to-noise ratio is too low for the FEC to maintain a reliable stream. This leads to packet drops and " Symbol Errors " that trigger InfiniBand " Retransmissions, " which are catastrophic for the performance of AI collectives like all_reduce. While Rx power variance (Option A) and temperature (Option D) are health indicators, they are causes of poor BER, not the BER threshold itself.

NCCL is used to validate GPU communication behavior across the East-West fabric, so the correct answers are measuring latency between GPUs and measuring bandwidth between GPUs. NVIDIA describes NCCL as a topology-aware library of multi-GPU collective communication primitives, and NVIDIA GPU debug guidance specifically identifies NCCL performance tests, such as all_reduce_perf, as useful for establishing network performance between groups of nodes. In an AI Factory, East-West traffic is the server-to-server traffic used during distributed training. When models scale across many GPUs and nodes, operations such as all-reduce, broadcast, all-gather, and reduce-scatter depend on low latency and high bandwidth. NCCL testing helps confirm that GPU-to-GPU paths, GPUDirect RDMA, InfiniBand or Spectrum-X fabric behavior, routing, and collective communication performance are healthy before production workloads start. NCCL is not intended to measure storage performance; that requires storage benchmarks or GPUDirect Storage validation. It also does not measure GPU power consumption; that is handled by tools such as nvidia-smi, DCGM, or platform telemetry.

A floating Virtual IP address is required because users, compute nodes, and management services need a consistent endpoint for the active BCM head node. NVIDIA DGX BasePOD HA documentation states that the external VIP is the IP address that should always be used to access the active head node after HA configuration is complete. The same HA workflow also verifies failover behavior after setup by checking HA status from both directions and confirming which head node is active. Therefore, a controlled failover validation is necessary to prove that the secondary head node can assume service responsibility. Compute nodes do not need to be powered on and running workloads during HA setup; NVIDIA documentation actually shows cluster nodes being powered off before HA configuration. Independent static IP addresses alone do not provide transparent service continuity because clients would need to reconnect manually. Synchronization occurs as part of the HA setup workflow, but the best two answers for automatic failover and verified readiness are the floating VIP and failover validation.

In a Bright Cluster Manager HA setup, the database (MySQL/MariaDB) must remain perfectly synchronized between the active and standby head nodes to allow for a seamless transition. This synchronization typically occurs over a dedicated management or heartbeat network. If cmsh status shows the database service as [FAIL] on the secondary node, it almost always points to a communication breakdown. Without a stable network path, the secondary node cannot receive the binary logs from the primary node to keep its local copy up to date. While licensing (Option A) is important, a license failure usually disables management capabilities entirely rather than just the MySQL sync. Furthermore, head nodes are management servers and do not require GPU drivers (Option C) for their primary function. Ensuring low-latency, reliable connectivity between the two head nodes is the primary troubleshooting step for resolving " MySQL FAIL " states in BCM.

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.

NVIDIA Spectrum-X is the world’s first high-performance Ethernet fabric designed specifically for AI, combining Spectrum-4 switches with BlueField-3 SuperNICs. To achieve the high-throughput, low-latency requirements of East-West (server-to-server) AI traffic, the BlueField-3 hardware must be correctly provisioned. The first requirement is ensuring the physical ports are operating in Ethernet mode; LINK_TYPE_P1=2 (and P2=2 for the second port) toggles the hardware from InfiniBand to Ethernet mode. Secondly, the BlueField-3 can operate in several " modes. " While " DPU mode " (Option D) offloads the entire OS to the ARM cores, " NIC mode " (or SuperNIC mode) allows the host to manage the networking while leveraging the Internal CPU Offload Engine. Setting INTERNAL_CPU_OFFLOAD_ENGINE=1 is a specific configuration step for Spectrum-X that allows the SuperNIC to handle RoCE (RDMA over Converged Ethernet) and Congestion Control (CC) algorithms more efficiently at 400G speeds. This setup is vital for AI workloads like LLM training, where consistent latency and zero-packet-loss are non-negotiable for collective communications.

The correct approach is to create a unique, strong administrative user and avoid default or weak credentials. NVIDIA DGX first-boot guidance states that the setup process creates an administrative user account for the system, BMC, and GRUB boot loader. DGX OS guidance also notes that the default BMC credentials stop working after new credentials are created, and earlier DGX OS guidance specifies that the username must use lower-case letters and a strong password. This matters because the BMC provides powerful out-of-band management functions, including remote console, power operations, firmware updates, and hardware monitoring. GRUB protection is also important because unauthorized boot-loader access can weaken system security or bypass controls. Creating separate usernames is not aligned with the documented first-boot flow where the administrative identity is reused for BMC and GRUB. Retaining defaults is insecure, and using a generic username with a simple password is unacceptable for enterprise production. In DGX infrastructure, secure first-boot credential setup is part of system hardening and operational readiness.

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.