Transit placed fare-collection on a known set of NSX-T segments and wants DFW policy to follow those segments as VMs are added. What should the administrator use?
Select an answer to reveal the explanation.
Short Explanation
If the fare app lives on those segments, put the segments in the group. New VMs that land there inherit the fence without someone typing two hundred IPs.
Full Explanation
NSX-T groups can be defined from segments and can nest other groups. Segment membership scales as workloads attach. Static IP lists rot, UEM smart groups are not NSX DFW members, and load-balancer VIP pools are not the segment-based group model.