A hospital needs its network test to start on the clinical application server so the first hop is that server's own interface. Where should the Enterprise Agent run?
Select an answer to reveal the explanation.
Short Explanation
A tape measure starts in your hand, and a test starts on the host that is holding the agent. You put the Enterprise Agent on the application server when the path has to begin on that server's own interface. A laptop, a cloud vantage point, or a copied packet stream starts somewhere else.
Full Explanation
If the test must begin on the clinical application server, the Enterprise Agent has to run on that server so the first hop is the server's own interface and the path includes the gateway that server actually uses. An Enterprise Agent installed on that clinical application server is the placement that makes the server itself the probing point. An Endpoint Agent on one laptop that is not the application server starts on a different machine, often on a different segment, and it goes quiet when that laptop sleeps, so it does not represent the server. A cloud agent outside the hospital that cannot see the internal hop begins off campus. It may reach a public address and still miss the internal hop the server uses to leave its subnet. A span session that copies packets for review and is not an Enterprise Agent can feed a capture. It does not run the Enterprise Agent test from the server, so it is not the probing point this design requires. Exam caveat: placement follows the vantage point you need, and a convenient laptop or an outside probe is not the same as starting the test on the host under study. Operational check: from the agent on the application server, confirm the test's first hop is that server's gateway rather than a laptop path or an external probe.