A city architecture slide labels the plane that computes runtime state from desired configuration and pushes forwarding config. Which SDN plane is that?
Select an answer to reveal the explanation.
Short Explanation
If management is city hall's filing cabinet, the control plane is the dispatcher that turns the filed plan into live street instructions. It computes runtime state and pushes forwarding config down to the data plane. The Manager API and Horizon brokers do not play that dispatcher role.
Full Explanation
The control plane computes runtime state from desired configuration and pushes forwarding configuration to the data plane. A city architecture slide labeling that function should identify control, not management-as-forwarding or data-as-API-author. The management plane does not forward packets on the host. The data plane does not author the NSX Manager API. The Horizon connection-broker plane does not program NSX segments. Exam caveat: NSX-T splits central and local control components, but the conceptual job—runtime from desired state—is control plane. Operational check: after publishing a config change, verify control-plane realization status to transport nodes before expecting data-plane hits. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems. Record realization state and underlay health in the runbook used by on-call city operators. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems.