The correct answer is C because mdadm --examine and mdadm --detail directly inspect Linux software RAID metadata and array health. During DGX cluster deployment, local RAID storage must be verified before the node is released for AI workloads, logging, container images, datasets, scratch space, or checkpoint staging. A mounted filesystem only proves that the operating system can access the volume; it does not confirm that the RAID array is clean, synchronized, degraded, rebuilding, or free of disk failure events. FIO is useful for performance benchmarking, but speed and latency results alone do not prove RAID integrity. A degraded array can sometimes still deliver acceptable short-term performance while lacking redundancy or carrying latent errors. The mdadm --detail command reports array state, active devices, failed devices, rebuild progress, spare disks, and consistency status. The mdadm --examine command checks member-device metadata and helps confirm whether disks belong correctly to the array. In NVIDIA AI infrastructure bring-up, RAID health validation is part of server readiness because storage faults can cause job failures, lost logs, unstable container operation, or checkpoint corruption during production workloads.