An operations department is struggling with software vulnerabilities across a large set of servers. Management wants a systematic setup that tests updates before production with minimal manual steps. Which option is BEST?
Publish a policy that requires administrators to manually approve patches for each device
Design a release pipeline that stages updates in a test environment and moves them to production using scheduled tasks
Reject newly released patches to reduce overhead and re-enable them in quarterly cycles
Activate daily scans on all systems and run reboots after each detected update
Implementing a process that tests updates before moving them to production is reliable and efficient. Applying patches without a controlled release increases risk of unexpected failures. Manually approving patches for every device can introduce delays and errors. Ignoring updates leaves systems exposed to threats.
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.
What is a release pipeline?
Open an interactive chat with Bash
Why is it risky to apply updates without a controlled process?
Open an interactive chat with Bash
What are the advantages of automating patch management?