Question 380
A data center implementation team investigates the following fault: A virtualization platform needs a block device for a raw LUN but the proposed integration offers only an NFS file-system export as though it were an iSCSI target. Which root cause best explains this behavior?
Explanation
Correct Answer
The technical cause is The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. The appropriate response is: Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk. Confirm successful repair: The host discovers an iSCSI target LUN and presents the expected block device to the hypervisor.
Incorrect Answers
The NFS export access rules do not authorize the requesting client address or security identity. “Update the scoped NFS export policy to include only the approved new hypervisor client addresses” would address that alternative cause, not the condition in this question: the application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation.
“Update the approved initiator and target CHAP secret settings using the supported secure workflow” responds to this separate finding: the iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. This question instead needs “Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk”, so the alternative does not meet the stated condition.
The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. “Verify target port FLOGI and FCNS registration and restore the authorized target attachment” applies to that separate problem. The observed case is a virtualization platform needs a block device for a raw LUN but the proposed integration offers only an NFS file-system export as though it were an iSCSI target; choosing this alternative would address the wrong failure mode.