A company has an ESXi host installed with FC HBAs that is connected to a Dell Unity XT storage array. A 500 GB LUN is provisioned to this host from the Unity array and is in production. The VMware…

Question

Options

• ATwo iSCSI target interfaces must be configured with IP addresses from separate subnets.
• BA connection must be established between the host iSCSI initiators and Unity iSCSI targets
• CAny single host should connect to any single array using one protocol only.

• A
  11% (5)
• B
  61% (27)
• C
  27% (12)

Explanation

Option B is correct because software iSCSI requires an active discovery and login session between the host's iSCSI initiator and the Unity array's iSCSI target interfaces - without this connection, the 1 TB LUN cannot be presented to the host even if the vSwitch and NICs are already configured. The VMware admin handled the network layer (vSwitch), but the storage admin must still configure the Unity iSCSI targets and ensure the initiator discovers and connects to them via SendTargets or static discovery.

Option A is wrong because iSCSI target interfaces on separate subnets is a multipathing best practice, not a hard requirement - iSCSI can function with both ports on the same subnet, making this a preference, not a blocking consideration.

Option C is wrong because ESXi and Dell Unity XT fully support simultaneous multi-protocol access; a single host connecting to the same array over both FC and iSCSI is a legitimate and common configuration, especially when adding new LUNs without disrupting existing production ones.

Memory tip: Think of iSCSI setup as two distinct layers - the network layer (vSwitch/NICs, handled by VMware) and the storage layer (initiator-to-target connection, handled by the storage admin). Option B is always required because without that initiator-target handshake, the LUN is invisible to the host regardless of how well the network is configured.

No community discussion yet for this question.