Which sequence lists typical phases of patch management cycle?

Which sequence lists typical phases of patch management cycle?

• A. Discovery/assessment, testing, deployment, verification, remediation.
• B. Planning, development, deployment, sunset.
• C. Scanning, patching, rebooting, auditing.
• D. Design, coding, testing, deployment.

Answer: (A)

The sequence tests the full lifecycle of patch management, from identifying what needs patches to making sure they’re actually applied and any gaps are addressed. Starting with discovery/assessment ensures you know which assets need updates and what risks they pose. Then testing makes sure patches won’t break critical systems before you roll them out widely. Deployment actually applies the patches across the environment. Verification confirms that patches are successfully installed and that systems function as expected after patching. Remediation covers any remaining issues, such as patches that failed or systems that still show vulnerabilities, ensuring the environment is secure and up to date. The other options describe different workflows. One mirrors a project development path (planning, development, deployment, sunset) rather than actively managing patches. Another focuses on generic IT operations steps (scanning, patching, rebooting, auditing) but lacks the formal testing and verification phases and a structured remediation step. The last resembles software development life cycle (design, coding, testing, deployment) and isn’t the patch management process. So, the sequence with discovery/assessment, testing, deployment, verification, and remediation best represents the patch management cycle.

The sequence tests the full lifecycle of patch management, from identifying what needs patches to making sure they’re actually applied and any gaps are addressed. Starting with discovery/assessment ensures you know which assets need updates and what risks they pose. Then testing makes sure patches won’t break critical systems before you roll them out widely. Deployment actually applies the patches across the environment. Verification confirms that patches are successfully installed and that systems function as expected after patching. Remediation covers any remaining issues, such as patches that failed or systems that still show vulnerabilities, ensuring the environment is secure and up to date.

The other options describe different workflows. One mirrors a project development path (planning, development, deployment, sunset) rather than actively managing patches. Another focuses on generic IT operations steps (scanning, patching, rebooting, auditing) but lacks the formal testing and verification phases and a structured remediation step. The last resembles software development life cycle (design, coding, testing, deployment) and isn’t the patch management process.

So, the sequence with discovery/assessment, testing, deployment, verification, and remediation best represents the patch management cycle.