220-1102 Operating Systems Practice Question
A technician needs to run a legacy Windows 7 application on a Windows 10 Pro workstation. The application requires direct access to hardware and does not work with compatibility mode. Which Windows feature should the technician enable to support this requirement?
⚠ Common exam trap
A common mix-up: candidates confuse Compatibility Mode as a catch-all solution for legacy applications, but the question explicitly states the application requires direct hardware access, which Compatibility Mode cannot provide, making Hyper-V the only viable option.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Hyper-V
Hyper-V is the correct choice because it allows the technician to create a virtual machine running Windows 7 with direct access to hardware resources, such as through Hyper-V's discrete device assignment (DDA) or legacy virtual switches. This bypasses the limitations of compatibility mode, which only modifies the application's environment without granting direct hardware access. By running the legacy application in a Windows 7 VM, the technician can satisfy the hardware access requirement while maintaining the Windows 10 Pro host.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Windows Sandbox
Why it's wrong here
Windows Sandbox creates an isolated, ephemeral desktop environment to safely run untrusted executables, but it boots the same Windows 10/11 OS image as the host and cannot install a separate legacy operating system such as Windows 7. It also intentionally strips direct hardware access — no GPU passthrough, no direct I/O — so a legacy application requiring its own drivers or hardware resources will fail. Thus, it is not a replacement for a proper VM when you need a 32-bit Windows 7 environment with legacy hardware support.
- ✓
Hyper-V
Why this is correct
Hyper-V on Windows 10 Pro is a Type-1 hypervisor (though exposed as a Windows feature) that lets you create a complete Windows 7 virtual machine with its own virtualized CPU, disk, RAM, and hardware devices such as a legacy network adapter. Inside that VM, the legacy application sees a true Windows 7 kernel and HAL, so any HAL-level or driver-level hardware access is handled by the VM's emulated hardware without compatibility conflicts. Hyper-V also supports snapshots and separate virtual switches, allowing you to isolate the old app while giving it the exact hardware characteristics it expects. This is the only option that provides a fully compatible legacy OS with controlled hardware access.
- ✗
Compatibility Mode
Why it's wrong here
Compatibility Mode, set through the executable's Properties → Compatibility tab, installs an application shim that makes the OS lie about its version, adds small UX tweaks like 640x480 resolution or DPI scaling, and can run the app as administrator. However, it does not change the underlying Windows 10 kernel, the Win32 API set, or the Windows Driver Model (WDM) stack; if the app loads a Windows 7-specific driver, calls undocumented I/O ports, or expects Windows 7-specific services behavior, the shim merely passes the call to the modern OS and fails. Compatibility Mode is a lightweight fix for API version mismatches, not a solution for deep hardware or kernel access.
- ✗
Windows Subsystem for Linux (WSL)
Why it's wrong here
WSL (Windows Subsystem for Linux) in both WSL1 and WSL2 is specifically designed to execute Linux ELF binaries, not native Windows PE executables. WSL1 translates Linux syscalls directly to the Windows kernel, while WSL2 uses a real Linux kernel inside a lightweight utility VM, but in neither case does it provide a Windows 7 environment or the Win32 API layer. A legacy Windows 7 application is a .exe requiring the PE loader, so it cannot run under WSL at all — you would need Wine or a full Windows VM. Furthermore, WSL2's VM is managed by Windows and offers only limited hardware virtualization, with no support for arbitrary legacy device drivers or direct I/O access.
Go deeper
Related to this question
Learn chapter
Windows Device Manager
Key term
Compatibility mode
Compatibility mode is a software setting that allows a program or operating system designed for an older version of Windows to run on a newer version by mimicking the older environment.
Key term
Virtual machine
A virtual machine (VM) is a software-based emulation of a physical computer that runs an operating system and applications just like a real machine, but is isolated and managed by a hypervisor on a host system.
About these practice questions
This 220-1102 question is part of Courseiva's 925-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1102 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1102 exam.