Forwarding engines on prepared city hosts receive stateless forwarding tables from NSX. Which SDN path is that dissemination?
Select an answer to reveal the explanation.
Short Explanation
The control plane talks downhill to the engines that actually move packets. That downhill path is southbound to the data plane—not vMotion of Manager, not Horizon REST, and not a sensor check-in.
Full Explanation
Forwarding engines on prepared city hosts receive stateless forwarding tables through southbound dissemination from the control plane to the data plane on transport nodes. That downhill control-to-data path is how ESXi and Edge nodes learn how to switch and route overlay traffic for the civic fabric. Northbound REST from vCenter toward Horizon that supposedly installs BLAST routes confuses EUC brokering with NSX fabric programming and uses the wrong plane direction. East-west vMotion of the NSX Manager virtual machine relocates a management VM; it does not disseminate forwarding tables to hosts. A Carbon Black sensor check-in reports endpoint health and does not program Geneve VTEPs or host forwarding engines. Exam caveat: remember plane directions—northbound is typically API/consumers into management, southbound is control into data. Associate questions test identification of that path, not packet formats of every southbound channel. Operational check: after publishing a network or routing change, verify transport-node realization succeeds and data-plane tables update on hosts; do not interpret a Manager vMotion event or a sensor check-in as proof that southbound fabric programming completed.