Wastewater VM packets are forwarded by tables that sit on the prepared host. Which SDN plane performs that forwarding?
Select an answer to reveal the explanation.
Short Explanation
The data plane is the actual pipes: packets hit tables on the host and get forwarded without calling city hall for each frame. Management UI, DRS, and Carbon Black are not those pipes. Stats flow back up; the packet path stays on the transport node.
Full Explanation
The data plane performs stateless forwarding from control-plane tables and reports statistics for wastewater VM packets on the prepared host. That is where tables sit and frames are switched/routed/filtered in the forwarding path. The management plane UI does not inspect every packet before it leaves the VM. vCenter DRS is not the NSX-T packet path. Carbon Black is not the overlay forwarding engine. Exam caveat: troubleshooting "config looks right but traffic fails" often means checking data-plane realization and host modules after confirming management config. Operational check: generate test traffic between wastewater VMs and confirm forwarding/DFW counters increment on the host data plane. 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.