220-1102 Practice Question: That a legacy 16-bit application is not running…

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

Answer analysis

Why the other options are wrong

Understanding why incorrect options are tempting is as important as knowing the correct answer.

• ✗

  Install the application in Windows XP compatibility mode

  Compatibility mode does not resolve the architectural limitation of 64-bit Windows, which lacks support for 16-bit executables.

• ✗

  Enable the Windows Subsystem for Linux

  WSL is for running Linux binaries, not legacy Windows 16-bit applications.

• ✗

  Run the application as administrator

  Running as administrator does not overcome the 16-bit architecture limitation.

Technical deep dive

How to think about this question

The core issue preventing a 16-bit application from running on a 64-bit Windows 10 system is an architectural incompatibility. 64-bit Windows operating systems lack the built-in NTVDM (NT Virtual DOS Machine) subsystem that was present in 32-bit versions of Windows. NTVDM was responsible for providing the necessary environment, including a virtual 8086 mode, to execute 16-bit applications. Without NTVDM, 64-bit Windows cannot directly interpret or run 16-bit executables, regardless of compatibility settings or administrative privileges. Therefore, the solution requires an environment that *does* possess this capability. A virtual machine running a 32-bit version of Windows 10 (or even an older 32-bit Windows OS like XP or 7) effectively recreates the necessary execution environment. Inside the 32-bit guest OS, the WoW64 (Windows-on-Windows 64-bit) layer, which is part of 32-bit Windows, can handle the execution of 16-bit applications. While WoW64's primary role is to allow 32-bit applications to run on 64-bit Windows, the 32-bit Windows OS itself inherently supports 16-bit applications through NTVDM. This approach isolates the legacy application in a compatible environment without compromising the host system. Compatibility mode (Option A) is ineffective because it only adjusts how a 32-bit or 64-bit application behaves within its native environment; it cannot magically add NTVDM support to a 64-bit OS. WSL (Option B) is for Linux binaries, and running as administrator (Option D) addresses permission issues, not architectural ones.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

Keep practising

More 220-1102 practice questions

• →A change advisory board (CAB) approved a standard change to update antivirus definitions on all servers. The technician…
• →A company's change management policy requires all server changes to be approved by the Change Advisory Board (CAB). A te…
• →A company is implementing a bring-your-own-device (BYOD) policy and needs to ensure that corporate data on employee mobi…
• →A company requires employees to present both a smart card and a PIN to log into their workstations. Which authentication…
• →A company requires all Windows 10 workstations to be able to join an Active Directory domain. Which edition of Windows 1…
• →A company wants to allow employees to securely access internal resources from home via the internet. Which method provid…