hardMultiple Choice
220-1202 Practice Question: A technician is tasked with migrating a physical…
A technician is tasked with migrating a physical server running a legacy OS that does not support virtualization drivers. The technician needs to ensure the OS can boot and run in a virtual machine. Which of the following steps is most critical before performing the physical-to-virtual (P2V) conversion?
⚠ Common exam trap
220-1202 often tests the misconception that a backup or OS patch is the 'most critical' pre-conversion step, when the exam is really probing whether you understand that legacy OSes need HAL and storage driver injection to boot on virtual hardware.
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
✓
Use a P2V tool that can inject the correct HAL and storage drivers for the hypervisor
Legacy operating systems that predate virtualization support lack the HAL (Hardware Abstraction Layer) and mass-storage drivers needed to boot on a hypervisor's virtual hardware. A P2V tool with driver-injection capability (such as VMware vCenter Converter or Microsoft Disk2vhd paired with offline driver injection) rewrites the HAL and installs the correct virtual SCSI/IDE/NIC drivers so the OS can start inside the VM. Without this step the converted image typically blue-screens with a STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE error.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the physical server's RAM before conversion
Why it's wrong here
Increasing the physical server's RAM before a P2V conversion is unnecessary and does not impact the success of the migration process itself. The P2V tool captures the disk image, not the live RAM configuration. After conversion, the virtual machine's RAM, CPU, and other hardware resources are independently configured within the hypervisor, allowing for flexible allocation regardless of the original physical server's specifications. This action would not address any potential boot issues related to driver compatibility.
- ✗
Ensure the legacy OS has the latest service pack installed
Why it's wrong here
While maintaining an updated operating system with the latest service packs is generally good practice for security and stability, it does not directly resolve the common boot failures encountered during a P2V migration. Legacy operating systems, even fully patched, lack the specific virtualization drivers (e.g., for virtualized storage controllers or network adapters) required to recognize the hypervisor's synthetic hardware. Therefore, installing service packs does not address the fundamental driver incompatibility that prevents the converted VM from booting successfully.
- ✓
Use a P2V tool that can inject the correct HAL and storage drivers for the hypervisor
Why this is correct
This is the critical step for a successful P2V migration, especially for legacy operating systems. A specialized P2V tool can inject the appropriate Hardware Abstraction Layer (HAL) and virtualized storage drivers directly into the captured disk image before the first boot on the hypervisor. This ensures the operating system can correctly identify and interact with the virtualized hardware components, such as the virtual disk controller, enabling it to boot successfully without encountering blue screens or boot device errors. Without these injected drivers, the OS would attempt to load drivers for the original physical hardware, leading to a boot failure.
- ✗
Create a full backup of the physical server
Why it's wrong here
Creating a full backup of the physical server before initiating a P2V conversion is an essential best practice for disaster recovery and data integrity. It provides a crucial safety net, allowing for restoration if the conversion process fails or data corruption occurs. However, performing a backup does not inherently solve the technical challenges associated with driver compatibility or the operating system's ability to boot on virtualized hardware, which is a distinct problem addressed by driver injection during the conversion process itself.
Go deeper
Related to this question
About these practice questions
This 220-1202 question is part of Courseiva's 687-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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This 220-1202 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-1202 exam.