A university keeps installing its probing software on a laptop that sleeps, and the tests go dark whenever that laptop sleeps. What should they use instead for a steady Enterprise Agent?
Select an answer to reveal the explanation.
Short Explanation
A lamp that turns itself off cannot watch the building through the night. You want a dedicated Enterprise Agent on a host that stays up when laptops sleep, so the campus tests keep running. Leaving an endpoint on that laptop, moving to a cloud probe, or mirroring a port still fails the steady vantage you need.
Full Explanation
The university keeps putting the probing software on a laptop that sleeps, and the tests go dark with it, so the replacement is a dedicated Enterprise Agent on a host that stays up when laptops sleep. The probing point then has its own host instead of borrowing a user machine that leaves the network for hours. An Endpoint Agent that remains on that same laptop still goes to sleep with the laptop, and an endpoint on one user device is not the dedicated Enterprise Agent the campus tests need. A cloud agent cannot see the internal campus hop the current tests are meant to cover, so moving the vantage off campus drops the segment the laptop was at least sometimes able to see. A SPAN session on a lab switch copies frames and is not an Enterprise Agent for the campus tests, so a mirror does not replace the scheduled probing that disappears when the laptop sleeps. On the exam, a laptop that sleeps is a bad Enterprise Agent host; the steady placement is a dedicated agent that stays up. In production, let a user laptop sleep and confirm the dedicated agent keeps running the campus tests, including the internal hop, while the laptop is dark.