Change Management Questions
Standard, normal, and emergency changes with CAB approval workflows, conflict detection, and risk assessment.
Newest question added: AI-assisted drafts, not yet individually reviewedHow questions are made
About Change Management
Change Management ensures consistent approach to risk assessment, business continuity, and change approval. It covers the complete lifecycle from creation through implementation and closure.
Why This Matters for Your Exam
Change Management is 25% of the CIS-ITSM exam, per the official blueprint. Expect questions about change types, CAB/ECAB approval, conflict detection, change states, and multimodal change.
Key Concepts to Master
Understand the three change types (Normal, Standard, Emergency), the difference between CAB and ECAB, scheduling and conflict detection, risk assessment methods, and change task types.
Exam Tips
Know that Normal changes require full CAB approval, Standard changes are pre-approved, and Emergency changes need ECAB approval and should be linked to incidents. Remember the four change task types: Planning, Implementation, Testing, Review.
Practice Questions
28 questions availableA team plans next month's upgrade of a production database server. It is not in the standard change catalog, nothing is failing, and the work needs a peer review. How should the change be handled?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: C. Normal change needing peer approval and CAB
A normal change is any service change that is not a standard or emergency change. It requires assessment, peer or technical approval, and Change Advisory Board (CAB) authorization before implementation. ServiceNow's own example is a scheduled upgrade of a production database server that needs peer review and CAB authorization.
- Why A is wrong: Emergency changes are high-priority changes to resolve a major incident or apply an urgent security patch. A planned upgrade with nothing failing does not qualify.
- Why B is wrong: Standard changes do not require group or peer approval at all, and this work is not a pre-approved standard change.
- Why D is wrong: Standard changes are pre-approved changes from a catalog of templates. This upgrade is not in the standard change catalog, so it cannot skip approvals.
A change manager is asked to add a monthly certificate renewal to the standard change catalog. Which characteristic makes a change a good fit for the standard change type?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: D. Repeatable steps with a proven history of success
A standard change is a pre-authorized, low-risk, relatively common change that follows a specified procedure. It is frequently implemented, has repeatable implementation steps, and has a proven history of success. Because it is pre-approved, it skips group or peer approval and CAB authorization.
- Why A is wrong: Scheduling outside change blackout windows is described for normal changes. It does not make a change standard.
- Why B is wrong: Standard changes are low risk and do not require CAB authorization. A change that needs a full assessment is a normal change.
- Why C is wrong: Changes made immediately to resolve a major incident are emergency changes, which go directly to CAB authorization.