City automation staff want a programmatic northbound interface so 311 environments can request virtual networks the same way they already request VMs. Which SDN building block is that interface?
Select an answer to reveal the explanation.
Short Explanation
Northbound is the front door where scripts knock. That door is the NSX Manager API on the management plane—not the yellow ESXi console, not Horizon Client, and not a live-response shell.
Full Explanation
City automation staff who want scripts to request virtual networks the same way they already request VMs need the NSX Manager API on the management plane—the SDN northbound interface for the civic fabric. That programmatic front door lets pipelines create and query segments, gateways, groups, and security objects without logging into each physical device or host console, which is exactly how a municipal platform team keeps 311 environments repeatable. The ESXi Direct Console User Interface is a local host console for break-glass troubleshooting; it cannot serve as a fabric-wide declarative API for overlay networks. Horizon Client is an end-user desktop client used by people, not a REST fabric controller that provisions segments. Carbon Black Live Response is an investigative shell on endpoints and has no authority to create NSX virtual networks or security policies. Exam caveat: identify the Manager API as the northbound building block; this associate exam does not require writing REST payloads or memorizing every URI. Policy mode and Manager mode both expose APIs—what matters is knowing northbound lives on the management plane. Operational check: authenticate to NSX Manager’s API with an automation principal, create or list a test segment, and confirm the object appears in the UI inventory with matching identifiers; attempt the same outcome via DCUI, Horizon Client, or Live Response and confirm those tools cannot create the segment.