Public-works needs a new overlay Layer 2 network for water-meter headend VMs on the city's NSX-T fabric. How should the operator create that network in NSX?
Select an answer to reveal the explanation.
Short Explanation
A city overlay is a software street, not a leftover host vSwitch lane. Build it under Networking, then Segments, as a Policy Segment. Gateway Firewall zones and Horizon pools are not how NSX creates that L2.
Full Explanation
In the Policy UI, overlay and VLAN-backed Layer 2 networks are Segment objects created under Networking. Public-works needs a new overlay for water-meter headend VMs, so the operator opens Networking, then Segments, and adds a Policy-mode Segment—a software street, not a leftover host vSwitch lane. A standard vSphere port group on a host vSwitch is a vSphere construct, not the NSX method for an overlay segment. Gateway Firewall is a north-south security object, not an L2 network. Horizon and Unified Access Gateway do not create NSX segments. Exam caveat: choosing the correct transport zone on the Add Segment form decides overlay versus VLAN backing; the object type is still Segment under Networking. Operational check: create the public-works segment under Networking Segments, select the overlay transport zone, attach a headend test VM, and reject port groups, Gateway Firewall zones, and Horizon pools as the create path. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish.