A logistics hub needs ongoing visibility of traffic that is already crossing the branch LAN, rather than a new synthetic visit to an application. Which agent style fits that job?
Select an answer to reveal the explanation.
Short Explanation
You do not hire a mystery shopper when you need a camera on the crowd already in the aisle. You want a local collection agent on the branch LAN so you see the traffic that is already there. A synthetic visit, a click-through script, or a one-time capture is a different job than the ongoing view you asked for.
Full Explanation
The hub wants ongoing visibility of traffic that is already on the branch LAN, so the fitting agent style is a local collection agent sitting on that LAN. It observes the existing flow from the place the flow already lives, instead of inventing a new visit. A synthetic user agent opens the application the way a visitor would, which creates a fresh transaction and does not describe the traffic already crossing the LAN. A scripting agent clicks through a multi-step warehouse transaction, which is the right style when a scripted workflow is the thing under test, not when the job is to watch current LAN traffic. A one-time packet capture can copy frames for a short look, but it never walks the application and it is not left in place as an agent, so it is not the ongoing collection style the hub asked for. On the exam, separate a vantage that observes existing traffic from the two styles that generate their own application activity, and do not treat a capture file as an agent. In production, confirm the collection agent is on the branch LAN that carries the warehouse traffic and that its view keeps updating after the capture window you might have used for a spot check would have ended.