A government agency gets complaints from one region and needs a visit that behaves like a person simply opening the service there. Which agent style fits?
Select an answer to reveal the explanation.
Short Explanation
You send someone who browses like a local, from the town that actually complained. You want a synthetic user agent in that region so the visit matches a person opening the service. A fixed script, a LAN collector, or a packet capture does not perform that user-like visit for you.
Full Explanation
The agency needs a visit that behaves like a person simply opening the service in the region where complaints start, so the fitting style is a synthetic user agent placed in that region. That agent performs the user-like open from the same region the users are in, which is the comparison the complaints require. A scripting agent that replays a fixed multi-step transaction is the style for a scripted workflow with several steps. The request here is not a scripted click path; it is a person opening the service, so the transaction script tests a different action than the one users described. A local collection agent that only watches traffic already on a regional LAN observes existing packets and does not itself open the service the way a user does. A packet capture in that region never walks the application, so it cannot show what a person experiences when the service opens, no matter how close the capture sits to the complaint. On the exam, match a simple user-like visit to the synthetic user style, and keep the scripting style for a multi-step transaction. In production, run the synthetic user visit from the complaint region and compare it with a visit from a region that is not complaining, so the regional experience is what you are measuring.