An NVMe host has four volumes that are directly provisioned. When setting up a new NVMe host group, the host is not shown in the available host list. Why can the host not be added to the host group?

Question

Options

• AThe host initiator type is incorrect
• BThe host has mapped volumes
• CThe host is part of another host group
• DThe host is not using the same OS

• A
  4% (2)
• B
  93% (51)
• C
  2% (1)
• D
  2% (1)

Explanation

A host with directly provisioned (mapped) volumes cannot be added to a host group because NVMe host groups require that member hosts have no individual volume mappings - volumes must be assigned at the group level, not the host level, to maintain consistency across all hosts in the group. Options A and D are wrong because initiator type and OS type are not prerequisites for host group membership in this context. Option C is wrong because while a host already in another group could also be excluded, the scenario specifically describes a host with mapped volumes, making B the root cause here. Memory tip: Think "clean slate" - a host joining a group must have no solo volume baggage; volumes belong to the group, not the individual host.

No community discussion yet for this question.