Courseiva
Operational Procedures →mediumMultiple Choice

220-1102 Operational Procedures Practice Question

A technician has completed an approved change to deploy a new printer driver to all workstations in a department. The deployment was successful, and all users can print. According to change management best practices, which of the following should the technician do NEXT?

⚠ Common exam trap

Many candidates confuse 'successful deployment' with 'completed change' and skip the validation step, choosing to close the ticket or document immediately, but CompTIA emphasizes that monitoring is a mandatory phase in the change management lifecycle to ensure no regression occurs.

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

✓

Monitor the workstations for 24 hours for any issues.

Change management best practices require a monitoring period after a change is implemented to verify stability and catch any latent issues, such as driver conflicts or print spooler errors, before closing the ticket. The deployment was successful and users can print, but problems like memory leaks or compatibility issues with specific applications may only surface after extended use. Monitoring for 24 hours ensures the change is fully validated before proceeding to closure.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Document the change and update the asset management database.

    Why it's wrong here

    Documenting the change and updating the asset management database is an important administrative step, but it does not validate that the printer driver is functioning correctly on any workstation. Documentation should occur after the monitoring period has confirmed stability, so any discovered issues and their resolutions can be accurately recorded. Updating the asset inventory before verification risks reflecting an incomplete or inaccurate deployment state, which could mislead future troubleshooting and audits.

  • ✗

    Close the change ticket immediately.

    Why it's wrong here

    Closing the change ticket immediately removes the change from active oversight before any runtime evidence has been collected, leaving compatibility problems with the print spooler or driver conflicts undiscovered. Standard change management policy requires a defined post-implementation review period, such as 24 hours, to allow unforeseen issues to surface and to provide a clear window for rollback if needed. Immediate closure would also produce an incomplete audit trail, since the verification step would be skipped entirely.

  • ✓

    Monitor the workstations for 24 hours for any issues.

    Why this is correct

    Monitoring the workstations for 24 hours is the correct post-implementation step because it provides a practical observation window for the new driver to be exercised under real user workloads, allowing detection of issues like spooler crashes, print queue stalls, or driver conflicts with common applications. This monitoring is the verification stage required by change management, and it yields objective evidence that the deployment is stable before the change is formally closed. If problems are found, the 24-hour window still allows a controlled rollback to the previous driver.

  • ✗

    Notify the users that the change is complete and ask for feedback.

    Why it's wrong here

    Notifying users and asking for feedback is part of the communication plan, but it is not a substitute for systematic monitoring because users may not immediately test all printing features, such as duplexing, color matching, or specific tray selections. Subjective feedback is useful after the monitoring period, when it can be correlated with any issues already observed. Acting on feedback too early could result in unnecessary changes or confusion if a transient driver issue later resolves during the monitoring window.

About these practice questions

Courseiva writes every 220-1102 question from scratch — 925 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This 220-1102 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 220-1102 exam.