SSCP Security Operations and Administration Practice Question
A change request to update a critical database server has been approved by the Change Advisory Board (CAB). During testing, a major compatibility issue is discovered. What is the best course of action?
⚠ Common exam trap
SSCP often tests the misconception that an approved change can proceed despite new critical findings, when in fact any significant issue requires re-evaluation by the CAB.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Report the issue to the CAB and request a revised change
Reporting the issue to the CAB and requesting a revised change is the best course because the change management process requires that any significant deviation from the approved change, such as a major compatibility issue, be re-evaluated by the CAB. This ensures proper risk assessment and approval before proceeding. It maintains the integrity of the change control process and prevents unintended outages.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Report the issue to the CAB and request a revised change
Why this is correct
The CAB owns change approval, so a discovered compatibility issue invalidates the approved change and must be escalated for reassessment. Proceeding without reapproval bypasses change control; reporting back and requesting a revised change preserves governance and satisfies the stem's testing constraint.
- ✗
Reject the change request and close it permanently
Why it's wrong here
Permanently closing the request discards the approved business need and forces a fresh submission, wasting the CAB's work. Rejecting outright is tempting when testing exposes a blocker, yet the correct path is to return the change for revision or defer it, preserving the request for resubmission once the compatibility issue is resolved.
- ✗
Implement the change but have a rollback plan ready
Why it's wrong here
A rollback plan mitigates failure but does not justify deploying a change whose testing already exposed a major compatibility issue. Rollback is for unforeseen problems during implementation, not known blockers. The change should be returned for revision or deferred until the compatibility issue is resolved and retested.
- ✗
Proceed with the change and resolve the issue after implementation
Why it's wrong here
Proceeding ignores the compatibility failure and pushes a known-defective change onto a critical database server, risking outage and data loss. This is tempting under schedule pressure, but change management requires that testing failures halt implementation. The change should be deferred or revised, not deployed with the fault intact.
Go deeper
Related to this question
About these practice questions
This SSCP question is part of Courseiva's 971-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISC2 exam blueprint
This SSCP practice question is part of Courseiva's free ISC2 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 SSCP exam.