Match each change-management practice to the best description for reducing patching risk in production.
Drag a concept onto its matching description — or click a concept then click the description.
Use a phased rollout to catch compatibility issues early
Provide a rollback or backout plan if the patch fails
Place the work inside a maintenance window
Create a baseline that supports recovery and comparison
Apply change control and obtain approval
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Change Advisory Board: A group that reviews and approves changes to reduce unauthorized modifications.
These change-management practices reduce patching risk by ensuring proper review, scheduling, rollback capability, pre-testing, documentation, and automation to minimize errors.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Change Advisory Board: A group that reviews and approves changes to reduce unauthorized modifications.
Why this is correct
The Change Advisory Board (CAB) is a formal governance committee typically comprising stakeholders from IT, security, and business units. Its core responsibility is to review proposed changes, assess their risk and impact, and either approve or reject them before implementation. This oversight reduces unauthorized modifications and helps ensure changes align with organizational security policies and operational requirements. The CAB does not perform technical testing or scheduling; it focuses on change approval and risk governance.
Rollback plan: A documented procedure to revert to a previous state if a patch causes issues.
Why this is correct
A rollback plan is a documented, step-by-step procedure to restore a system or application to its previous known-good state if a patch or update fails, introduces critical bugs, or causes data corruption. It includes specific actions such as restoring from backups, reversing configuration updates, and rolling back code versions, along with defined triggers for activation. This plan is essential for minimizing downtime and data loss after a problematic deployment, and it is typically tested to ensure feasibility. It is a recovery mechanism, not a scheduling or approval practice.
Pre-testing in staging: Testing patches in an environment that mirrors production before deployment.
Why this is correct
Pre-testing in staging involves deploying a patch or software update in an environment that closely mirrors production, including the same hardware, operating systems, middleware, and data characteristics. This allows technical teams to identify compatibility issues, performance anomalies, and functional regressions in a controlled setting before production deployment. The staging environment isolates risks and enables validation of the change and the rollback procedure without affecting live systems. This practice is distinct from the CAB's approval role and from scheduled maintenance windows that determine when deployment occurs.
Scheduled maintenance windows: Performing patching during a time window that minimizes impact on operations.
Why this is correct
Scheduled maintenance windows are predefined time periods, usually during off-peak hours, when systems are intentionally taken offline or limited to apply patches, upgrades, or other changes. By selecting low-activity periods, organizations minimize disruption to users and business operations, and they can plan for potential downtime in advance. This practice is part of change scheduling and execution, not a recovery or approval process. Effective maintenance windows are communicated to stakeholders and aligned with service-level agreements to ensure predictable service delivery.
Change Advisory Board: Testing patches in a staging environment before deployment.
Why it's wrong here
This option is incorrect because it describes pre-testing in a staging environment, which is a separate technical validation practice, not the responsibility of the Change Advisory Board (CAB). The CAB's role is governance-based: it reviews, risk-assesses, and approves change proposals, relying on technical experts to actually perform testing. While the CAB may review the results of staging tests as part of its decision-making, it does not itself execute tests or manage the staging environment. The confusion arises because CAB approval and pre-testing are both elements of a change management process, but they are functionally distinct.
Rollback plan: Performing patching during a time window that minimizes impact on operations.
Why it's wrong here
This option is incorrect because it describes a scheduled maintenance window, which is a planning/scheduling practice, not a rollback plan. A rollback plan is a reactive recovery procedure triggered when a change fails or causes issues, providing a pathway to revert to a previous state; it does not concern when the change is performed. Scheduled maintenance windows are proactive and focus on minimizing operational impact by choosing a low-activity time for deployment. These two practices serve entirely different purposes in change management: one is timing, the other is restoration.
Go deeper
About these practice questions
One of 1,013 original SY0-701 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.