220-1102 Practice Question: A technician is tasked with upgrading the…

Answer analysis

Option-by-option breakdown

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

• ✗

  Continue upgrading the remaining workstations since the change was approved.

  Why it's wrong here

  Continuing with upgrades after a known failure on a pilot system is a direct violation of sound change management principles, particularly risk assessment. This action would multiply the impact of the issue across the entire environment, leading to widespread service disruption and significantly increased recovery efforts and costs. It demonstrates a disregard for system stability and user productivity.

• ✗

  Restore the first workstation to the previous OS and complete the rest without changes.

  Why it's wrong here

  Restoring the workstation to its previous state without thoroughly documenting the encountered issue or performing a root cause analysis is an incomplete and irresponsible response. This approach ignores the critical need to understand why the upgrade failed, preventing the organization from learning from the incident and addressing the underlying problem. Such an action bypasses proper change control and leaves the system vulnerable to recurring issues.

• ✓

  Report the failure to the change advisory board and pause further upgrades.

  Why this is correct

  Reporting the failure to the Change Advisory Board (CAB) and immediately pausing further upgrades is the correct and most responsible course of action. This allows the CAB, as the governing body for changes, to evaluate the identified risk, assess the impact, and collectively decide on the appropriate next steps. They can then modify the rollout plan, investigate a workaround, or halt the change entirely, preventing wider system instability.

• ✗

  Research a hotfix for the application and apply it to all workstations.

  Why it's wrong here

  Independently researching and applying a hotfix to all workstations without proper testing, documentation, or CAB approval constitutes a significant bypass of established change management protocols. This unilateral action risks introducing new, unforeseen compatibility issues or system instabilities, potentially creating an unsupported configuration. Such a deviation complicates future troubleshooting and undermines the integrity of the IT environment.

Go deeper

Related to this question