CompTIA A+ Core 1 220-1201 objectives 4.1 and 4.2 cover virtualization and cloud computing. The useful first question is what the user needs: a separate operating system, an isolated application, a remote desktop, or a service someone else operates.
A virtual machine (VM) can run on a local computer or in a cloud provider's infrastructure. Virtualization describes how computing resources are separated. Cloud computing describes a way of delivering and managing services. The two often work together, but one does not require the other.
Fast rule: A VM runs a guest operating system. A container runs an isolated application environment while sharing the host operating-system kernel. Virtual Desktop Infrastructure (VDI) delivers desktop sessions from centralized systems. Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) tell you how much the customer manages.
1. Virtualization and cloud decision map
| Need | Think first | What matters |
|---|---|---|
| Test a different operating system | VM | Guest OS, available memory, processor, storage, and networking |
| Package an application consistently | Container | Application dependencies and host-kernel compatibility |
| Access a centrally hosted work desktop | VDI | Network, sign-in, remote session, and backend service |
| Manage a rented server's OS | IaaS | Customer controls guest OS, software, and configuration |
| Deploy code without managing servers | PaaS | Provider manages underlying platform; customer manages code and data |
| Use a finished hosted application | SaaS | Provider operates the application; customer manages access and use |
2. Separate VMs, containers, and remote desktops
- VM: Virtual hardware presents a computer to a guest operating system. A VM suits isolated operating-system testing, development, legacy software, or a sandbox where changes should stay separate from the host. Isolation still needs appropriate security configuration.
- Container: Packages an application and its dependencies while sharing the host operating-system kernel. It usually starts faster and uses fewer resources than a VM. A container is not automatically a separate full operating system.
- VDI: Virtual Desktop Infrastructure hosts desktop environments centrally and delivers sessions over a network. A working laptop can still fail to reach its virtual desktop because of authentication, network, or server-side problems.
- Application virtualization: Lets an application run or appear to run apart from a conventional local installation. It can assist with legacy software or different operating environments, depending on compatibility and the technology used.
An employee opening a hosted desktop is a VDI use case. A technician starting a guest Windows or Linux installation to test software is a VM use case. A developer running a packaged service with the host kernel is a container use case.
3. Type 1 vs. Type 2 hypervisors
A hypervisor creates and manages VMs.
| Type | Runs where? | Typical clue |
|---|---|---|
| Type 1 | Directly on host hardware | Dedicated virtualization host running several guest systems |
| Type 2 | As software on a host operating system | Technician runs a test VM on an existing workstation |
The distinction concerns the hypervisor's relationship to the host operating system. It does not, by itself, guarantee performance or security.
4. Check virtual-machine requirements before troubleshooting
- Processor: The Central Processing Unit (CPU) must support the required virtualization features. Firmware and host settings may need them enabled.
- Memory: Random Access Memory (RAM) assigned to guests must fit alongside the host's own needs. Oversubscribed or insufficient memory can cause slowness.
- Storage: The host needs sufficient space and acceptable disk performance for virtual disks, snapshots, and the workload.
- Networking: Confirm whether the guest needs network address translation (NAT), bridged access, or an isolated virtual network. A VM without the expected connectivity may be configured on the wrong virtual network.
- Security: Guest updates, access controls, isolation, and host protection still matter. A sandbox limits exposure; it does not make unsafe activity harmless.
When one guest is slow but the host is healthy, start with its assigned resources and workload. When every guest is slow, look at shared host capacity and storage performance.
5. Cloud deployment and service models answer different questions
Deployment models describe who the environment serves and how it is organized:
- Public cloud: Services offered through a provider's shared infrastructure, with logical isolation between customers.
- Private cloud: Infrastructure dedicated to one organization. It can be hosted internally or by a provider.
- Hybrid cloud: Uses connected private and public cloud environments for different workloads.
- Community cloud: Shared by organizations with common requirements or concerns.
Service models describe what the provider operates:
| Model | Customer usually manages | Provider usually manages |
|---|---|---|
| IaaS | Guest operating system, applications, data, and access | Physical hosts, storage hardware, and underlying infrastructure |
| PaaS | Application code, configuration, and data | Runtime platform and underlying infrastructure |
| SaaS | User access, application settings, and uploaded data | Hosted application, platform, and infrastructure |
The exact responsibility split depends on the service and contract. None of these models removes the customer's need to manage accounts and data appropriately.
6. Read cloud characteristics as support and cost clues
- Elasticity: Resources can increase or decrease with demand. A temporary traffic spike calls for capacity that can scale, subject to service limits.
- Availability: A service is reachable when needed. Multiple instances or regions can improve resilience, but deployment choices and provider guarantees still matter.
- Metered utilization: Charges may depend on storage, compute time, or network transfer. Ingress is traffic entering a service; egress is traffic leaving it. Pricing varies by provider and direction.
- Multitenancy: Different customers use shared underlying systems with logical separation. Shared infrastructure is different from giving customers access to each other's data.
- Shared vs. dedicated resources: Shared physical capacity can serve separate customers, while dedicated capacity is reserved for one customer or workload according to the service model.
- File synchronization: Keeps selected files updated across locations or devices. A deletion or corruption may also synchronize, so sync is not a backup strategy by itself.
7. Scenario comparisons
Run another OS for a support lab
A technician needs to test an older application without replacing the workstation's current operating system. Choose a VM and confirm guest compatibility and sufficient host resources.
Deploy a packaged application across development computers
The team needs a consistent application runtime, but no separate guest operating system. A container fits, provided the host kernel and application support it.
One employee cannot open a centrally hosted desktop
Other staff can connect. Check that employee's network path, sign-in, and assigned remote session before assuming the physical laptop has failed. This is a VDI support problem.
The team needs a hosted server it can patch itself
IaaS fits a requirement to administer the guest operating system. PaaS would shift more platform operations to the provider; SaaS would deliver a finished application.
A hosted service grows automatically during demand spikes
Think elasticity. If the complaint is instead that the service becomes unavailable during a component failure, think availability and resilience.
Files vanished from several synchronized devices
Investigate the sync history and recovery/versioning options. Do not assume synchronization provides an independent backup.
8. Common exam traps
- Confusing a container with a VM that runs its own guest operating system.
- Assuming every cloud service is a VM, or every VM must be in the cloud.
- Choosing Type 1 or Type 2 from brand recognition instead of where the hypervisor runs.
- Confusing VDI with a local guest VM simply because both show a desktop.
- Treating a private cloud as necessarily located on the organization's premises.
- Mixing deployment models (public/private/hybrid/community) with service models (IaaS/PaaS/SaaS).
- Mistaking elasticity (scaling resources) for availability (being reachable).
- Ignoring egress charges or assuming file synchronization is the same as backup.
9. Rapid review grid
| Clue | Think first |
|---|---|
| Full guest operating system | VM |
| Isolated application sharing host kernel | Container |
| Central desktop accessed over a network | VDI |
| Hypervisor directly on hardware | Type 1 |
| Hypervisor runs on host OS | Type 2 |
| Customer administers guest OS | IaaS |
| Customer deploys code on managed platform | PaaS |
| Finished hosted application | SaaS |
| Capacity expands or shrinks with demand | Elasticity |
| Same files on multiple devices | File synchronization, not necessarily backup |