Each civic transport node has a local control plane that must receive forwarding updates. How does that plane interact with the central control plane?
Select an answer to reveal the explanation.
Short Explanation
Central control is the city dispatcher; local control is the officer on each host. Manager's CCP tells each transport node's LCP what to program. vCenter and Horizon are not that control channel.
Full Explanation
The central control plane on the NSX Manager cluster disseminates runtime updates to the local control plane on each transport node, and that local control plane programs the node's forwarding engines for overlay and security state. Central control is the city dispatcher; local control is the officer on each host or Edge who installs the instructions locally. The local control plane does not push desired state up to vCenter only as its NSX control channel, because vCenter is not the CCP for Geneve forwarding. Edge nodes do not replace the central control plane while Manager is healthy; Edges are data-plane appliances for centralized services. The local control plane does not learn Geneve forwarding state only from Horizon, which is an EUC stack. Exam caveat: management-plane agents on transport nodes are related plumbing, but the label pair this item wants is CCP on Manager disseminating to LCP on transport nodes. Operational check: after a policy or segment change, verify transport nodes remain connected with healthy local control-plane agents in NSX Manager, confirm host forwarding state updates for the civic workloads, and ensure operators do not look to Horizon or vCenter HA as the Geneve control channel.