A library workload VLAN must become an NSX object so security groups and tags can consume it. What should the administrator create?
Select an answer to reveal the explanation.
Short Explanation
DFW groups eat NSX segments, not leftover vSphere port groups from the old closet. Build the library VLAN as an NSX segment on the right transport zone so tags and security groups can actually see it.
Full Explanation
NSX security groups and policy objects consume NSX segments—overlay or VLAN-backed—that sit on the intended transport zone. A vSphere standard-switch port group with no NSX backing is not that object. Carbon Black sensor groups and Workspace ONE UEM smart groups organize endpoints and devices; they are not NSX network inventory for DFW grouping.