A city must accept DPU-equipped municipal GPU nodes. What BlueField-3 confirmation belongs in Domain 4 verification?
Select an answer to reveal the explanation.
Short Explanation
City DPU nodes aren't done at OS boot—confirm BlueField-3 firmware and software on every equipped box before you stamp acceptance.
Full Explanation
City acceptance of DPU-equipped municipal GPU nodes must include BlueField-3 platform currency, not only host OS or GPU driver checks. Confirming BlueField-3 firmware and software levels on all DPU-equipped municipal nodes is Domain 4 skill 4.7 and ensures DPUs match the fabric’s approved offload and manageability baseline. Ignoring BlueField-3 versions if the host OS boots leaves the DPU plane unverified while the node looks healthy in-band to casual inspection. Confirming only the host GPU driver and skipping DPU firmware validates accelerators but not the SmartNIC/DPU stack that DOCA offloads and advanced networking may depend on. Treating factory BlueField-3 levels as permanently approved assumes shipping defaults equal the city’s golden image, which they often do not after manufacturing lag. Exam writers separate host health from DPU platform confirmation; both belong in municipal node acceptance. Caveat: BF3 confirmation belongs alongside other node acceptance gates even when immediate workloads are GPU-only, because DPU mismatch later blocks offloads, supportability, and consistent fleet behavior. Operational check: query BF3 firmware and software on every DPU-equipped city node, compare to the approved matrix, remediate outliers, and withhold acceptance for nodes that still diverge.