A hospital campus hosts its Enterprise Agent only on the application server, and probing stops whenever that server is rebuilt. What should replace that placement?
Select an answer to reveal the explanation.
Short Explanation
A spare generator keeps the lights on while you rebuild the main machine. You move the Enterprise Agent to a dedicated device so probing continues when the application server is rebuilt. A clinician laptop, a cloud probe, or a SPAN session still leaves you without that steady campus vantage.
Full Explanation
The Enterprise Agent today lives only on the application server, and probing stops whenever that server is rebuilt, so the replacement is a dedicated device that hosts the Enterprise Agent and stays up through the rebuild. The application install and the probing point are then separate: rebuilding the server no longer removes the vantage that tests the campus. An Endpoint Agent on one clinician laptop follows a single user device and is not the campus probing host, so it neither replaces the site agent nor survives as the hospital's test origin. A cloud agent cannot see the internal hop inside the hospital campus, which means the segment the current agent was placed to see disappears from the path if you move the test outside. A SPAN session that copies packets is not an Enterprise Agent, so a mirror keeps running or not without ever originating the tests the server-hosted agent was performing. On the exam, when the requirement is that probing survive a server rebuild, choose a dedicated Enterprise Agent host rather than the application install alone. In production, rebuild a test server or schedule the real change and confirm the dedicated agent keeps testing the internal hop while the application server is down.