A bank's cloud probe reaches the public gateway but cannot show the hops between the teller VLAN and the core, and the team wants that inside path from an Enterprise Agent. Which placement provides it?
Select an answer to reveal the explanation.
Short Explanation
A spotter standing outside the building cannot name the rooms a hallway passes through. You place an Enterprise Agent inside the bank network so the hops a cloud probe cannot see show up on the path. One teller laptop, another outside cloud agent, or a span that is not an Enterprise Agent still leaves that inside view missing.
Full Explanation
A cloud probe that reaches the public gateway and cannot see the hops between the teller VLAN and the core is outside the network those hops live in. An Enterprise Agent placed inside the bank's own network sources tests from within that network, so those internal hops can appear on the path. An Endpoint Agent installed on a single teller laptop sees the network from one desk. It can sleep, it represents one user device, and it is not the inside probing point this gap calls for. Another cloud agent that still starts outside the bank keeps the same external vantage point. A different cloud location does not put the probe on the teller-to-core path. A span session that copies internal packets and is not an Enterprise Agent can duplicate frames. It does not run the Enterprise Agent test from inside the network, so it does not close the gap the cloud probe left. Exam caveat: when the missing data is an internal hop, the Enterprise Agent has to sit where that hop is visible, and another outside probe does not create that view. Operational check: source a path test from the internal Enterprise Agent and confirm the hops between the teller VLAN and the core appear, which the cloud probe could not show.