Virtualization Concepts

CompTIA A+ 220-1201 & 220-1202

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the CompTIA A+ Certification Exam Domains & Study Strategy

2 Core 1 Domain 1: Mobile Devices (13%)

Laptop Hardware & Components Laptop Features & Display Types Mobile Device Connectivity & Accessories Mobile Operating System Features Mobile Device Synchronization & Data Transfer

3 Core 1 Domain 2: Networking (23%)

TCP/IP Fundamentals & the OSI Model Common Ports & Protocols Wireless Networking Standards Network Hardware & Devices Network Configuration & Internet Connections Network Types & Topologies

4 Core 1 Domain 3: Hardware (25%)

Cables & Connectors RAM Types & Storage Devices Motherboards, CPUs & Power Supplies Printers & Multifunction Devices Peripheral Devices & Expansion Cards Network Cable Tools & Testing

5 Core 1 Domain 4: Virtualization & Cloud Computing (11%)

Virtualization Concepts Cloud Computing Models & Services Client-Side Virtualization in Practice

6 Core 1 Domain 5: Hardware & Network Troubleshooting (28%)

CompTIA Troubleshooting Methodology Hardware Troubleshooting Network Troubleshooting Printer Troubleshooting Display & Mobile Device Troubleshooting

7 Core 2 Domain 1: Operating Systems (28%)

Windows Editions & Features Windows Administrative Tools & Utilities Windows Command Line & PowerShell macOS & Linux Basics Windows Networking & File Sharing Windows Installation & Upgrade Methods

8 Core 2 Domain 2: Security (28%)

Physical & Logical Security Measures Malware Types & Threat Mitigation Wireless & Network Security Encryption & Data Protection

9 Core 2 Domain 3: Software Troubleshooting (23%)

Windows OS Troubleshooting Mobile OS & Application Troubleshooting Browser & Application Troubleshooting

10 Core 2 Domain 4: Operational Procedures (21%)

Documentation & Change Management Backup & Recovery Methods Safety & Environmental Procedures Scripting & Remote Access Technologies Privacy, Licensing & Organizational Policies

Virtualization Concepts

Key Takeaways Explain This Topic AI

A hypervisor creates and manages virtual machines: Type 1 (bare-metal) installs directly on hardware for production servers, while Type 2 (hosted) runs on top of a host operating system for labs and testing.

Every virtual machine (VM) is allocated software-based hardware (vCPU, vRAM, virtual disk, virtual network interface card) and behaves like an independent physical computer with its own operating system.

Hardware-assisted virtualization (Intel VT-x or AMD-V) must be enabled in BIOS/UEFI before any hypervisor can run 64-bit guests; it is frequently disabled by default.

Containers (Docker, Podman) share the host kernel and start in seconds with megabyte-sized images, whereas VMs include a full guest OS and boot in minutes using gigabyte-sized disks.

On the 220-1201 Core 1 exam, Domain 4 is worth 11 percent, so expect roughly 8 to 10 of the 90 questions to cover virtualization and cloud concepts.

Last updated: October 2026

What Virtualization Means on the Exam

Virtualization is the creation of software-based versions of physical resources such as servers, storage, networks, and entire operating systems. A single physical host can run several virtual machines (VMs) , each acting as an isolated computer with its own guest OS, applications, and virtual hardware. CompTIA A+ Core 1 (exam 220-1201, the V15 edition launched March 25, 2025) tests virtualization in Domain 4, which is weighted at 11 percent of the 90-question, 90-minute exam.

The core benefit is consolidation: instead of ten under-used physical servers, one powerful host runs ten VMs, cutting hardware, power, cooling, and rack costs. Other tested benefits include sandboxing (running risky software in isolation), legacy-application support, cross-platform development, fast disaster recovery via snapshots, and resource efficiency.

Hypervisors: Type 1 vs Type 2

A hypervisor (also called a virtual machine monitor) is the software layer that creates, schedules, and isolates VMs. Objective 4.1 lists both Type 1 and Type 2 hypervisors, so know the two types cold.

Type 1 (Bare-Metal)

• Attribute Detail
• Installs on Hardware directly, with no host OS underneath
• Performance Near-native; the hypervisor talks straight to the CPU
• Where used Data centers, production servers, enterprise clusters
• Examples VMware ESXi, Microsoft Hyper-V (Server role), Citrix XenServer, KVM, Proxmox
• Type 2 (Hosted)

• Attribute Detail
• Installs on Top of an existing OS (Windows, macOS, Linux)
• Performance Lower; requests pass through the host OS first
• Where used Developer laptops, classrooms, home labs, QA testing
• Examples VMware Workstation/Fusion, Oracle VirtualBox, Parallels Desktop

Trap: CompTIA classifies Microsoft Hyper-V as a Type 1 hypervisor even though you enable it from inside Windows 11 Pro. When Hyper-V starts, Windows itself becomes a privileged management partition and the hypervisor sits beneath it. Do not call Hyper-V "Type 2" just because it appears on a desktop OS.

Virtual Machine Components

Each VM receives software versions of real hardware. Recognize these by name and file extension:

• Virtual Component Description
• vCPU Logical cores carved from the physical CPU
• vRAM Memory reserved from host physical RAM
• Virtual disk A file on the host acting as the VM hard drive ( .vmdk , .vhd / .vhdx , .qcow2 )
• Virtual NIC Software adapter wired to a virtual switch
• Virtual optical drive Mounts an ISO image as a CD/DVD

Virtual networking modes you must distinguish:

Bridged — the VM gets its own IP address directly on the physical LAN and appears as a separate device.

NAT — the VM hides behind the host IP; it reaches the internet but is not directly reachable from the LAN.

Host-only — the VM talks only to the host (no internet, no LAN), ideal for malware analysis.

Internal — VMs talk only to each other.

Hardware Virtualization Requirement

Before any hypervisor can run modern 64-bit guests, the CPU's hardware-assisted virtualization feature must be turned on in firmware: Intel VT-x (sometimes branded VT-d for I/O) or AMD-V . This setting often ships disabled. If a customer reports "my VM won't start" or VirtualBox shows a VT-x error, your first step is to reboot, enter BIOS/UEFI, and enable virtualization. On Windows hosts, Hyper-V, the Windows Hypervisor Platform, and Memory Integrity can also lock VT-x away from VirtualBox/VMware, producing the same symptom.

Containers vs Virtual Machines

• Feature Virtual Machines Containers
• Isolation Full — each has its own guest OS kernel Process-level — share the host kernel
• Image size Gigabytes (full OS) Megabytes (app + libraries)
• Boot time Minutes Seconds
• Best for Different OSes, strong isolation Microservices, CI/CD, rapid scaling
• Examples ESXi, Hyper-V, VirtualBox Docker, Podman, Kubernetes (orchestration)

Because containers reuse the host kernel, you cannot run a Windows container on a Linux host without a hidden VM. That shared-kernel trade-off explains both their speed and their weaker isolation versus VMs.

Use Cases You Will See on the Exam

Domain 4 questions are usually scenario-based, so connect each benefit to a real situation:

Server consolidation — replace many idle physical servers with VMs on one host to cut power, cooling, and rack space.

Development and testing — spin up disposable environments that exactly mirror production, then discard them.

Legacy application support — keep an old line-of-business app alive by running its required Windows XP or 7 guest in a VM long after the hardware is gone.

Sandboxing — open suspicious email attachments or unknown installers inside an isolated VM so any infection never touches the real machine.

Cross-platform testing — a web developer checks a site against Windows, macOS, and several Linux distributions from a single laptop.

Disaster recovery — because a VM is just files, you snapshot it, copy it offsite, and restore it on different hardware in minutes.

Training and labs — students practice destructive tasks (repartitioning, registry edits) with no risk to a shared classroom PC.

How Resource Sharing Actually Works

A host with 8 physical cores can present far more than 8 vCPUs across its VMs because most guests are idle most of the time; the hypervisor schedules real cores only when a guest needs one. This is CPU oversubscription . Memory can be oversubscribed too, but RAM is far less forgiving than CPU: if active VMs demand more than the host physically has, the hypervisor must swap memory to disk and performance collapses. For the exam, remember that adequate physical RAM, fast SSD-backed storage for the virtual disks, and a multi-core CPU with VT-x/AMD-V are the four host requirements that make a usable virtualization platform.