A stadium lab must run path tests on event-week builds without placing the agent on production servers. Which placement fits?
Select an answer to reveal the explanation.
Short Explanation
A practice scale belongs on its own bench, not bolted to the machine you are about to rebuild. You put a dedicated Enterprise Agent in the stadium lab so event-week tests run without using production servers. A staff laptop, a cloud probe, or a SPAN session is not that lab agent.
Full Explanation
The lab has to probe event-week builds without placing the agent on production servers, so a dedicated Enterprise Agent in the lab is the placement that keeps the test origin off those servers and still inside the environment under test. The agent stays with the lab build instead of riding on a server the event cannot spare. An Endpoint Agent on one event-staff laptop follows that person and leaves when the shift ends, so it is not a stable probing point for the lab and it is not an Enterprise Agent parked there. A cloud agent cannot see the internal hop the lab build is meant to test, which means the very segment the lab cares about is missing from its path. A SPAN session in the lab rack mirrors packets and is not an Enterprise Agent at all, so it does not originate the path tests the build needs. On the exam, a dedicated Enterprise Agent is how you probe a lab without borrowing production servers, and a mirror session does not become that agent. In production, confirm the lab agent is the origin of the event-week tests and that no production server is hosting it, then confirm the path still includes the internal hop the lab build is supposed to exercise.