220-1102 Question 686
Single answerChange board approvalsA technician needs to deploy a registry change to 120 Windows workstations to fix a line-of-business application before the start of business tomorrow. Company policy requires all production changes to be reviewed by a change advisory board (CAB). The technician has tested the fix successfully on two non-production systems and documented the expected impact. What should the technician do NEXT to follow proper change-management procedures?
- A
Submit a formal change request with the implementation plan, testing results, risk assessment, rollback steps, and proposed schedule for CAB approval
- B
Deploy the change after business hours because the issue affects many users and the technician already validated the fix on test systems
- C
Ask the application owner for verbal approval and then push the change to production to avoid delaying the business
- D
Send an email to affected users explaining the change and proceed if no one objects before the end of the day
Show answer and explanation
Correct answer: A
Explanation
The best next step is to submit the change for formal CAB review with complete supporting documentation. In standard change-management practice, approval should occur before implementing a production change unless the organization has declared the situation an emergency and invoked a separate emergency change process. A well-prepared request includes testing results, business justification, affected assets, risk assessment, implementation steps, validation method, communication plan, and rollback procedure. This aligns with common IT service management best practices such as those described in ITIL-based change enablement/change management processes, where change advisory board approval is used to reduce risk, improve coordination, and maintain accountability.
- A. Correct.
Correct. In a controlled IT environment, a production change should go through the formal change-management process before implementation. A proper change request typically includes the reason for the change, affected systems, implementation steps, test evidence, risk and impact analysis, communication plan, backout or rollback plan, and the requested maintenance window. CAB review and approval help ensure the change is understood, authorized, and scheduled appropriately.
- B. Incorrect.
Incorrect. Testing the fix is important, but successful testing alone does not replace required CAB approval for production changes. Deploying without authorization bypasses change control and can create compliance, audit, and operational problems even if the change is technically sound.
- C. Incorrect.
Incorrect. An application owner's verbal approval may be useful input, but it is not the same as formal change board approval when organizational policy requires CAB review. This option reflects a common misconception that business stakeholder approval can substitute for documented change authorization.
- D. Incorrect.
Incorrect. User notification is part of many change plans, but notifying users does not authorize the change. Lack of objections from users is not equivalent to approval through the organization's established change-management process.