220-1102 Practice Question: A technician has received approval from the…

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

Answer analysis

Why the other options are wrong

Understanding why incorrect options are tempting is as important as knowing the correct answer.

• ✗

  Close the change request ticket immediately.

  Closing the ticket should only be done after full documentation and verification that the change is complete and successful. Immediate closure may skip important steps.

• ✗

  Inform all affected users that the maintenance is complete.

  While informing users is good practice, it is not the formal next step in change management. Documentation is prioritized to ensure the change is properly recorded.

• ✗

  Perform a full system backup of the server.

  A backup should be performed before the change, not after. Post-change backups are optional but not the immediate next step according to standard change management procedures.

Technical deep dive

How to think about this question

Following the successful implementation of a change, such as applying a critical security patch, the immediate next step in a robust change management process is to thoroughly document the outcome. This involves updating the change record with details of the implementation, including the exact time of completion, any issues encountered, whether the expected outcome was achieved (e.g., the server is functioning normally), and confirmation that the server is indeed back online. This documentation serves several critical purposes: it provides an audit trail for compliance, supports problem management by recording potential issues or unexpected behaviors, and contributes to a knowledge base for future changes. It ensures that the organization has a complete and accurate history of all modifications made to its IT infrastructure, which is vital for maintaining system stability and security. The scenario explicitly states the server "appears to be functioning normally," which implies initial verification but doesn't negate the need for formal record-keeping. While informing affected users (Option C) is a good communication practice, and closing the ticket (Option B) is the ultimate goal, neither precedes the formal documentation of the implementation details. Closing the ticket prematurely without a complete record risks losing valuable information about the change's execution. Similarly, performing a full system backup (Option D) is typically a pre-implementation step to ensure a rollback capability, not a post-implementation action in the change management workflow. The focus immediately after implementation shifts to recording what happened to ensure accountability and facilitate future operational activities.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

Keep practising

More 220-1102 practice questions

• →A change advisory board (CAB) approved a standard change to update antivirus definitions on all servers. The technician…
• →A company's change management policy requires all server changes to be approved by the Change Advisory Board (CAB). A te…
• →A company is implementing a bring-your-own-device (BYOD) policy and needs to ensure that corporate data on employee mobi…
• →A company requires employees to present both a smart card and a PIN to log into their workstations. Which authentication…
• →A company requires all Windows 10 workstations to be able to join an Active Directory domain. Which edition of Windows 1…
• →A company wants to allow employees to securely access internal resources from home via the internet. Which method provid…