220-1102 Software Troubleshooting Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Local Users and Groups

  Why it's wrong here

  Local Users and Groups is a Microsoft Management Console (MMC) snap-in used to administer user accounts, group membership, and local security permissions. While an older application might require elevated rights or a specific account context to run, the immediate problem is that the app depends on legacy operating system behavior, such as older DLLs, registry locations, or API semantics. Modifying users or groups does not emulate a prior Windows version, so it would not satisfy the compatibility constraint and thus is not the right primary tool here.

• ✓

  compatibility mode

  Why this is correct

  Compatibility mode allows the technician to configure legacy Windows settings—such as Windows XP or Windows 7—for the older application, forcing the operating system to emulate an earlier environment without modifying the tablet’s current OS. This satisfies the constraint of running an older application that requires deprecated system behaviours, such as specific DLL versions or registry structures, which modern Windows defaults do not provide.

• ✗

  System Restore

  Why it's wrong here

  System Restore is a rollback mechanism that reverts the system's registered files, registry keys, and selected settings to a previously captured restore point. It could indirectly resolve an application failure if a recent system change (e.g., a buggy driver or an update) broke the app, but it does not enable an older program to run on a modern OS when that program was never natively supported. Moreover, System Restore is a system-wide change rather than a per-application fix, making it an invasive, imprecise approach for a targeted compatibility task.

• ✗

  Event Viewer

  Why it's wrong here

  Event Viewer is a troubleshooting utility that aggregates Windows logs, application logs, and system logs, displaying errors, warnings, and audits. It is useful for examining the specific failure code or crash signature after an application fails to launch, but it does not alter the environment to make the application compatible. Relying on Event Viewer only would be diagnostic, not corrective; the immediate goal of actually running the old application is better served by directly applying a compatibility shim, not by post-event log analysis.

Go deeper

Related to this question