220-1102 Question 668
Single answerRollback planA technician is scheduled to deploy a new accounting application to 25 Windows 11 workstations after business hours. Management is concerned that if the deployment causes login issues or application conflicts, employees must be able to return to their previous working state before the next morning. Which action is the BEST example of creating an appropriate rollback plan before the deployment begins?
- A
Document the steps to uninstall the new application, verify recent backups or restore capability, and define how affected systems will be returned to the prior configuration if problems occur
- B
Send an email to users explaining that the installation is low risk and ask them to report any issues the next day
- C
Install the application on all 25 workstations at once so any problems can be identified quickly and fixed in a single maintenance window
- D
Disable antivirus during the deployment to reduce the chance that the installation will fail
Show answer and explanation
Correct answer: A
Explanation
A rollback plan is a key part of implementing organizational change in CompTIA A+ Core 2 objectives. It means defining in advance how to undo a change and restore the system or environment to its last known-good state if the implementation fails or causes unacceptable impact. In practice, this can include confirming backups, restore points, system images, application uninstall steps, configuration baselines, and clear criteria for when to stop the rollout and revert. Best practices in IT change management emphasize documenting the change, communicating with stakeholders, testing where feasible, performing scheduled implementation, and having a documented rollback procedure before making production changes. Option 1 is the only choice that directly addresses those rollback requirements.
- A. Correct.
This is correct because a rollback plan is a documented method for returning systems to a known-good state if a change causes problems. In a real deployment, that includes identifying how to remove the change, confirming backups, restore points, images, snapshots, or other recovery methods are available as appropriate, and specifying the steps to restore previous functionality. This aligns with standard change-management best practices: plan the change, assess risk, test if possible, and prepare a rollback procedure before implementation.
- B. Incorrect.
This is incorrect because notifying users is part of communication and change management, but it is not a rollback plan. A rollback plan specifically addresses how the technician will reverse the change and restore operations if the deployment fails.
- C. Incorrect.
This is incorrect because deploying to every workstation at once increases risk rather than providing rollback capability. A better practice is to pilot the change on a limited set of systems first, but even a pilot does not replace a rollback plan. The misconception is confusing broad deployment speed with preparedness.
- D. Incorrect.
This is incorrect because disabling antivirus is not a rollback strategy and may reduce security. In some environments, temporary exceptions may be used if properly authorized and documented, but that still would not satisfy the requirement to plan how to restore systems to their previous state if the change causes issues.