Virtualization and Cloud Computing Fundamentals for CompTIA Tech+ (FC0-U71): Hypervisors, IaaS, PaaS, and SaaS Explained

Virtualization and cloud computing are no longer "advanced" topics reserved for data center specialists. CompTIA's Tech+ (FC0-U71) exam treats them as foundational IT literacy, because almost every modern business — from a five-person startup to a global enterprise — runs at least part of its workload on a virtual machine or a cloud service. Objective 2.6 specifically asks candidates to "compare and contrast virtualization and cloud technologies," and it falls inside Domain 2.0 (Infrastructure), which carries the single largest weight on the exam at 24%.

This guide breaks down exactly what Tech+ wants you to know: what a hypervisor is, how a guest operating system relates to its host, the three major cloud service models (IaaS, PaaS, and SaaS), and the deployment models that decide where that cloud infrastructure actually lives.

What Is Virtualization? Hypervisors and Guest Operating Systems

Virtualization is the process of creating a software-based, or "virtual," version of something that would normally exist as physical hardware — most commonly a computer. Instead of buying, racking, and cabling a separate physical server for every workload, a single physical machine can host several independent virtual machines (VMs), each behaving as if it had its own dedicated hardware.

Two terms are essential here, and the exam expects you to know the difference:

• Hypervisor — the software layer that creates and manages virtual machines. It sits between the physical hardware and the virtual machines, allocating CPU time, memory, storage, and network access to each VM as needed.
• Guest OS — the operating system installed inside a virtual machine. A single physical host running one hypervisor might simultaneously run a Windows Server guest OS, a Linux guest OS, and a macOS guest OS, each completely isolated from the others.

Type 1 vs. Type 2 Hypervisors

While FC0-U71 does not require deep hypervisor architecture knowledge the way a server-focused certification would, understanding the basic distinction helps the concept stick:

• Type 1 (bare-metal) hypervisors install directly on physical hardware with no underlying operating system in between. They are typically used in data centers and enterprise environments because they are more efficient and offer better performance.
• Type 2 (hosted) hypervisors run as an application on top of an existing operating system, such as running virtualization software on a Windows or macOS desktop. These are common for developers, testers, and anyone who needs to run a second operating system on their everyday computer.

Virtualization is also what makes cloud computing possible in the first place — a cloud provider's entire business model depends on being able to carve one massive physical server farm into thousands of individually billable virtual machines.

Cloud Computing Service Models: IaaS, PaaS, and SaaS

Once virtualization makes it possible to deliver computing resources remotely, cloud providers package those resources into three main service models. Tech+ wants you to be able to compare and contrast all three:

• Infrastructure as a Service (IaaS) — the provider supplies the raw computing infrastructure: virtual machines, storage, and networking. The customer is still responsible for installing and managing the operating system, applications, and data. Think of renting an empty apartment — you get the walls and utilities, but you bring your own furniture. For a full breakdown, see our guide to Infrastructure as a Service (IaaS).
• Platform as a Service (PaaS) — the provider manages the underlying infrastructure and the operating system, giving developers a ready-to-use platform for building and deploying applications without worrying about server maintenance. Our Platform as a Service (PaaS) guide covers this in depth.
• Software as a Service (SaaS) — the provider manages everything, and the customer simply uses a finished application, usually through a web browser. Email services, webmail, and online office suites are classic SaaS examples. See our Software as a Service (SaaS) guide for more detail.

A useful way to remember the difference is how much the customer has to manage versus how much the provider manages. As you move from IaaS to PaaS to SaaS, the provider takes on more responsibility and the customer has less to configure, but also less control. This is closely related to the idea of a shared responsibility model, which our Cloud Responsibility Matrix article explains in detail — it is worth reading alongside this one since Tech+ candidates are expected to understand that security and management duties are always split between the provider and the customer, never held entirely by one side.

Cloud Deployment Models: Public, Private, Hybrid, and Community

Service models describe what you get from the cloud; deployment models describe where that infrastructure physically lives and who else shares it. FC0-U71 expects you to know all four:

• Public cloud — infrastructure owned and operated by a third-party provider (such as a major cloud vendor) and shared among many different customers over the internet. This is the most common and usually the most cost-effective option.
• Private cloud — infrastructure dedicated to a single organization, either hosted on-premises or by a third party exclusively for that one customer. This offers more control and can help meet stricter compliance or security requirements.
• Hybrid cloud — a combination of public and private cloud resources that work together, allowing an organization to keep sensitive workloads private while taking advantage of public cloud scalability for everything else.
• Community cloud — infrastructure shared by a specific group of organizations with common concerns, such as regulatory compliance or industry-specific requirements (several hospitals sharing a cloud environment built around healthcare privacy rules, for example).

Our dedicated article on Public, Private, Hybrid and Community Cloud deployment models walks through real-world scenarios for each, and pairs well with this overview. Readers who want to go one level deeper into how a private cloud carves out its own isolated network segment inside a public provider should also look at our guide to the Virtual Private Cloud (VPC), a concept that becomes directly relevant once you move on to Network+.

Why Organizations Choose Virtualization and Cloud Together

Virtualization and cloud computing solve related but distinct problems, and the exam likes to test whether you understand that relationship rather than treating the two terms as synonyms. Virtualization is the underlying technology that makes efficient hardware use possible — one physical server can run dozens of VMs instead of sitting mostly idle. Cloud computing is the delivery model that lets an organization consume that virtualized capacity on demand, usually billed by actual usage rather than a large upfront hardware purchase. Together they unlock benefits Tech+ wants you to recognize:

• Cost efficiency — no need to buy, power, cool, and maintain physical servers for every workload.
• Scalability — capacity can grow or shrink to match actual demand rather than being fixed at purchase time.
• Disaster recovery — virtual machines can be backed up, cloned, and restored on different hardware far more easily than physical servers.
• Faster deployment — spinning up a new virtual server takes minutes; ordering, racking, and configuring physical hardware can take weeks. (Left unmanaged, this same ease of creation is also what leads to the governance problem known as VM sprawl, covered in our article on VM Sprawl.)

Exam Tips for FC0-U71 Objective 2.6

• Know the one-sentence definition of a hypervisor and a guest OS cold — questions often describe a scenario and ask you to identify which term applies.
• Memorize the "who manages what" progression across IaaS, PaaS, and SaaS. A common exam pattern gives you a scenario (e.g., "a developer wants to deploy code without managing servers") and asks which service model fits — that description points to PaaS.
• Don't confuse deployment models (public/private/hybrid/community — the "where") with service models (IaaS/PaaS/SaaS — the "what"). These are two separate axes that can combine in any way, such as a private cloud delivering IaaS.
• Watch for scenario questions describing a hospital, bank, or government agency sharing infrastructure with similar organizations — that description signals a community cloud, a model test-takers often forget exists.
• Remember that virtualization is a technology, while cloud computing is a delivery/consumption model built on top of that technology — they are related but not interchangeable terms.

Key Takeaways

• A hypervisor creates and manages virtual machines; a guest OS is the operating system running inside one of those VMs.
• Type 1 hypervisors run directly on hardware (bare-metal); Type 2 hypervisors run as an application on top of an existing OS.
• IaaS, PaaS, and SaaS describe how much infrastructure the provider manages versus how much the customer manages — responsibility increases for the provider as you move from IaaS toward SaaS.
• Public, private, hybrid, and community cloud describe where cloud infrastructure lives and who shares it, independent of which service model is used.
• Virtualization and cloud computing work together: virtualization makes efficient resource sharing possible, and cloud computing is the on-demand delivery model built on top of it.