Operators need to inject a synthetic packet and see the virtual path between a water-quality lab VM and a historian VM. Which NSX-T feature does that?
Select an answer to reveal the explanation.
Short Explanation
Traceflow is a civic dye test: inject a fake packet and watch which NSX hops it hits. Performance charts, Horizon logs, and vSAN health do not inject that overlay packet.
Full Explanation
Traceflow injects a synthetic packet and reports the virtual path and observations between endpoints, which is how operators verify connectivity between a water-quality lab VM and a historian VM at identify depth. Traceflow is a civic dye test: inject a fake packet and watch which NSX hops it hits. GUI navigation of Traceflow belongs in the administrative domain; this item names the feature. vCenter performance charts do not inject overlay packets. Horizon session logs and vSAN health are not Traceflow. Exam caveat: Traceflow shows the virtual path and observations; it is not a replacement for underlay packet captures when the failure is purely physical, but it is the NSX feature for synthetic path injection. Operational check: run Traceflow between the lab and historian VMs, review observations on segments and DFW, and verify performance charts, Horizon logs, and vSAN health were not used as the injector. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish.