Question 420
At the Quayford environmental data center, a Linux database host cannot discover its ONTAP block storage because the initiator uses an unrelated target IP. Which ongoing control best prevents this failure from recurring?
Explanation
Correct Answer
This control works beyond the initial remediation because it requires the team to recheck target network reachability after SAN LIF changes. This result addresses the stated challenge at the Quayford environmental data center.
Incorrect Answers
That routine supports san nvme namespace support, but the relevant ongoing risk requires the team to recheck target network reachability after SAN LIF changes. For the Quayford environmental data center, the direct corrective action is to configure iSCSI discovery against reachable data LIFs on the intended SAN-enabled SVM.
“Monitor directory resolution and SMB trust health after DNS updates” checks a different ongoing risk rather than the reported failure: at the Quayford environmental data center, a Linux database host cannot discover its ONTAP block storage because the initiator uses an unrelated target IP. The relevant mechanism is it requires the team to recheck target network reachability after SAN LIF changes. The directly matched preventive control is “Recheck target network reachability after SAN LIF changes”.
Audit junction and volume mount status after provisioning changes is not the primary recurring safeguard for this problem. The team should recheck target network reachability after SAN LIF changes. For the Quayford environmental data center, the direct corrective action is to configure iSCSI discovery against reachable data LIFs on the intended SAN-enabled SVM.