A retailer wants a probe that stays beside each store firewall and keeps testing when no associate laptop is open. Which placement matches that design?
Select an answer to reveal the explanation.
Short Explanation
A guard shack beside the door stays staffed after the store closes, and your probe has to do the same. You place an Enterprise Agent on a dedicated device beside the firewall so the test does not depend on an open laptop. A cloud agent, one endpoint, or a span session is a different tool.
Full Explanation
A probe that must stay beside the store firewall and keep testing after the laptops are closed needs its own device at that spot. An Enterprise Agent on a dedicated device beside the firewall is the placement that sources tests from that standing probe instead of from a person's session. An Endpoint Agent on one associate laptop in the store follows that laptop. It stops when the laptop sleeps or leaves the store, so it is not a probe that remains beside the firewall. A cloud agent that cannot see the hop inside the store starts outside the branch. It can test toward a public address and still miss the internal hop next to the firewall. A span session that copies store traffic and is not an Enterprise Agent duplicates frames for analysis. It does not host the Enterprise Agent or run the scheduled test the retailer asked to place beside the firewall. Exam caveat: a dedicated Enterprise Agent, an endpoint install, a cloud vantage point, and a span are different collection methods, and only the dedicated device matches this design. Operational check: confirm the dedicated agent is up beside the firewall and that a test sourced from it still runs while store laptops are powered off.