During a scheduled vulnerability patch deployment window, soon after installing the update you observe CPU spikes and slow response times on a mission-critical application server that supports production transactions. Which immediate action should you take to restore stable operations while minimizing business disruption?
Apply additional patches to address the performance issues.
Isolate the server from the network to prevent potential propagation of issues.
Rollback the patch to restore the application to its previous state.
Continue monitoring the server for a longer period to gather more data before taking any action.
Rolling back the patch is the best immediate action when significant performance issues appear right after deployment. A rollback returns the system to its last known-good state, restoring service stability so operations can continue while the patch is investigated and retested in a non-production environment. Continued monitoring or additional patches do not halt the degradation quickly, and isolating the server causes unnecessary downtime without guaranteeing performance recovery.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is rolling back a patch the best immediate action when encountering performance issues?
Open an interactive chat with Bash
What is the purpose of testing patches in a controlled environment before deploying them to production?
Open an interactive chat with Bash
What steps can be taken to safely reapply a patch after a rollback due to performance issues?