Housing authority runs mixed GPU and BlueField hosts and must keep platform software aligned. What versioning practice is required?
Select an answer to reveal the explanation.
Short Explanation
Keep GPU drivers and DOCA versions on speaking terms using NVIDIA’s guidance—like matching firmware sets on related housing systems. Silent drift is how weird failures start.
Full Explanation
Housing-authority hosts that mix GPUs and BlueField must coordinate DOCA-host and GPU driver versions per NVIDIA guidance. Supported combinations are published for a reason: mismatched DOCA and GPU stacks produce networking/DPU anomalies and unsupported support cases even when each side “mostly works” alone. Version coherence is a platform practice for analytics nodes, not optional bookkeeping, and it should appear in the same change ticket when either side moves.
Allowing GPU and DOCA versions to drift without NVIDIA guidance institutionalizes unsupported skew across the housing estate. Pinning only DOCA and never installing GPU drivers leaves accelerators unusable for analytics. Tracking GPU versions in a paper binder and DOCA versions nowhere creates incomplete inventory and cannot enforce coordination when BlueField and GPU hosts share operational staff.
Exam caveat: mixed BlueField/GPU estates require coordinated versioning to NVIDIA’s matrix—not one-sided pins or informal partial tracking.
Operational check: maintain a single inventory of GPU driver and DOCA versions against NVIDIA’s supported pairs, gate changes on that matrix, and verify both stacks after any upgrade on housing analytics nodes.