A city network team wants path analytics and visibility across both the civic overlay hops and the physical underlay. Which product supports that use case?
Select an answer to reveal the explanation.
Short Explanation
Think of vRealize Network Insight as a city street map that shows both the overlay tunnels and the physical roads underneath. ESXi logs and Horizon sessions do not draw that path. Use vRNI when the ask is visibility plus path analytics across virtual and physical.
Full Explanation
vRealize Network Insight is the VCTA-NV product that delivers path analytics and visibility across both the civic overlay hops and the physical underlay beneath them. Harborview operators use it when the ask is a single map of virtual tunnels plus the roads those tunnels ride, not a stack of unrelated logs. ESXi host logs can help a city network team troubleshoot one hypervisor, but they are not a data-center path-analytics product and do not stitch overlay-to-underlay hop views. vSphere HA is a compute availability feature that restarts virtual machines after host failure; it never becomes virtual-plus-physical network visibility. Horizon Client session logs describe end-user computing sessions for remote clerks and do not draw the civic underlay path map. Exam caveat: associate-level questions expect you to name vRNI for path analytics spanning virtual and physical fabrics, not to configure every collector or flow export detail. Do not confuse host syslog with product-grade path analytics. Operational check: in a civic proof, confirm Network Insight can resolve a path between two agency VMs that includes both Geneve overlay hops and underlay switch hops, and verify that ESXi logs or Horizon sessions alone cannot substitute for that end-to-end view.