220-1102 Question 156
Single answerUpdate and SecurityA small office uses Windows 10 Pro laptops that receive updates directly from Microsoft. After a recent feature update, several users report that a line-of-business application crashes on launch. The application vendor has not yet certified the new Windows version, but management still wants the affected systems to continue receiving monthly security patches. What is the BEST action for the technician to take?
- A
Uninstall the recent feature update on the affected laptops and defer feature updates, while continuing to allow quality updates
- B
Disable Windows Update entirely until the vendor releases a compatible version of the application
- C
Run Disk Cleanup and remove temporary files so the application can rebuild its cache after the update
- D
Use System Restore on each laptop and then permanently turn off restore points to prevent future update-related issues
Show answer and explanation
Correct answer: A
Explanation
The best answer is to remove the incompatible feature update and defer future feature updates while continuing to receive quality updates. In Windows 10/11 servicing, feature updates introduce new versions and can create compatibility issues, whereas quality updates are the regular cumulative security and reliability patches that organizations generally should continue installing. For A+ Core 2, candidates should recognize that stopping all updates is not a secure or practical response when only a feature update caused the issue. Microsoft documents separate management of feature updates and quality updates through Windows Update for Business, Local Group Policy, and related update settings in Pro and enterprise-oriented editions. This scenario reflects a common real-world support decision: preserve security posture while mitigating application compatibility problems.
- A. Correct.
This is correct. In Windows 10 Pro, a technician can roll back or uninstall a problematic feature update and use update settings or policy to defer future feature updates while still allowing monthly quality updates. This approach addresses application compatibility without unnecessarily exposing systems by stopping security patches. It aligns with the best practice of separating feature-update management from ongoing security-update maintenance.
- B. Incorrect.
This is incorrect. Disabling Windows Update completely would stop both feature updates and critical quality/security updates, increasing risk to the organization. A common misconception is that all updates must be halted to preserve compatibility, but Windows provides ways to delay feature updates specifically while keeping security fixes in place.
- C. Incorrect.
This is incorrect. Disk Cleanup may help with storage-related update failures or remove obsolete update files, but it does not address a business application crashing because of OS-version compatibility after a feature update. Someone might choose this if they confuse update side effects with corrupted temporary data.
- D. Incorrect.
This is incorrect. System Restore can sometimes reverse recent system changes, but it is not the best long-term method for managing Windows update rings or feature-update compatibility. Turning off restore points is also poor practice because it removes a useful recovery option. The root issue here is controlling feature updates while preserving security patching, not eliminating recovery tools.