Question 510
After fixing this HPE storage issue, which evidence best establishes closure? A broad FC zone exposes production storage ports to unrelated servers.
Explanation
Correct Answer
The evidence matches the reported storage problem: Only approved host and array ports appear within the zone. It confirms the remediation: Apply narrow supported initiator-target zoning and verify membership. Underlying rule: FC zoning limits fabric discovery but does not replace array LUN masking.
Incorrect Answers
This addresses a different storage problem, such as: An iSCSI initiator can ping storage but TCP session negotiation fails. That problem points toward check IP routing TCP transport target discovery and iSCSI authentication. The present incident instead requires apply narrow supported initiator-target zoning and verify membership. and validation that only approved host and array ports appear within the zone.
The proposed proof is relevant when two nominal SAN fabrics share the same failure-prone core uplink. Its governing principle is that SAN resiliency needs separate full failure domains for the host paths. Here the better diagnosis follows FC zoning limits fabric discovery but does not replace array LUN masking.
This choice concerns SAN transport and topology, for example: A SAN migration assumes SCSI ALUA and NVMe ANA have identical requirements. The current storage issue instead hinges on FC zoning limits fabric discovery but does not replace array LUN masking. The appropriate evidence is only approved host and array ports appear within the zone.