Outline the general steps in patch management.

• A. Ignore patches until systems fail.
• B. Discover vulnerabilities, prioritize, test patches, deploy, and verify patch effectiveness.
• C. Replace hardware every year.
• D. Only patch servers, not endpoints.

Answer: (D)

Patch management is a structured process to keep systems secure by applying updates that fix known vulnerabilities. The general steps start with identifying what needs patches through asset inventory and vulnerabilityScanning, so you know which systems are missing important updates. Next, you prioritize patches based on risk, impact, and how critical each system is to operations. Before wider deployment, you test patches in a controlled environment to catch compatibility or stability issues that could disrupt work. After successful testing, you deploy the patches across affected devices and systems, and then verify that the patches were installed and that they’re providing the expected security benefits. Ongoing monitoring and regular scheduling keep everything up to date and help you respond to new vulnerabilities as they appear.

That approach aligns with best practices because it covers discovery, risk-based prioritization, testing to avoid unintended consequences, proper deployment, and verification of effectiveness. Ignoring patches until systems fail, replacing hardware annually, or patching only servers while neglecting endpoints all miss essential parts of maintaining a secure, up-to-date environment.