Study guide · Core 1 · Domain 4 · 11% of the Core 1 exam
Virtualization and Cloud Computing: the CompTIA A+ objectives in plain English
Domain 4 is a short domain with a wide reach in CompTIA A+ Core 1 (220-1201). It covers cloud computing concepts, including the three main service models, shared responsibility, cloud file storage and synchronization, virtual desktop infrastructure, and cloud based services such as hosted email. It also covers client-side virtualization, where one physical computer runs one or more virtual machines under a hypervisor. At 11 percent of the Core 1 exam, this is one of the smaller domains, but its vocabulary appears in many other scenarios, because help desk work now moves constantly between local machines, browser based services, and virtual environments. If you can explain who manages what in the cloud, and how a virtual machine differs from the host it runs on, you have the core of this domain. Most questions here reward clear definitions applied to a short workplace story, so learn each term by the job it does and by who is responsible for it.
What the objectives cover
4.1 Summarize cloud computing concepts
Cloud computing means using computing services over a network, usually the internet, from systems run by a provider instead of from hardware you own and maintain in your own building. The three service models differ in who manages what. With Infrastructure as a Service, or IaaS, the provider supplies virtual servers, storage, and networking, and manages the physical hardware and the virtualization layer underneath. The customer still installs the operating system, patches it, and installs and manages the applications and the data. With Platform as a Service, or PaaS, the provider also manages the operating system and the runtime or development platform, so the customer focuses on building, deploying, and running applications and the data those applications use, without patching the platform servers. With Software as a Service, or SaaS, the provider manages almost the whole stack, including the application itself, its updates, and the systems it runs on. The customer simply signs in, usually through a browser, and manages users, settings, and data. A useful way to remember the order is that control decreases as you move from IaaS to PaaS to SaaS, while convenience increases.
The shared responsibility model is the rule that ties the three models together. Responsibility is never all on one side. The provider is responsible for the physical data centers, servers, storage hardware, and core network, and for keeping the services it promises running and patched at the levels it controls. The customer remains responsible for its own data, user accounts, passwords, access choices, and the devices used to connect. Everything between those poles moves as the service model changes, which is why the same task, such as patching an operating system, belongs to the customer with IaaS and to the provider with SaaS. Cloud file storage keeps files on provider systems so they can be reached from many devices, and synchronization keeps copies in step, so a change made on a laptop appears on a desktop or a phone, and a conflict can appear when two copies change at once. Virtual desktop infrastructure, or VDI, hosts complete desktop environments on central servers, and users connect to a full desktop rather than to a single application. Cloud based services extend the same idea to everyday tools, such as hosted email, where the provider runs the mail servers, storage, and spam filtering, while the customer manages mailboxes, addresses, and who can sign in.
4.2 Summarize aspects of client-side virtualization
Client-side virtualization means running virtual machines on a local computer, such as a desktop or a laptop, instead of only on servers in a data center. A virtual machine, or VM, is a software based computer that behaves like a separate physical machine, with its own virtual processor, memory, storage, and network adapter. The operating system installed inside the VM is the guest operating system, and the physical computer it runs on is the host. One host can run several guests at the same time, each isolated from the others, so a problem inside one guest does not normally change the host or the other guests. A program called a hypervisor creates the VMs, divides the host resources among them, and controls their access to the real hardware. Hypervisors come in two types. A Type 1, or bare metal, hypervisor installs directly on the hardware, with no general purpose operating system underneath it. Examples include VMware ESXi and Microsoft Hyper-V in its server role. A Type 2, or hosted, hypervisor installs as an application on top of a normal operating system. Examples include Oracle VirtualBox and VMware Workstation. Type 1 hypervisors are common on servers because they use resources efficiently and present a smaller surface to secure. Type 2 hypervisors are common on client machines because they install easily alongside everyday applications, which is why this objective focuses on them.
Running virtual machines takes real resources from the host, so resource requirements decide whether a setup works well or barely works at all. The processor must support hardware virtualization, and that support usually has to be turned on in the firmware before the hypervisor can use it. The host needs enough RAM for its own operating system plus the memory assigned to each running guest, enough storage for the virtual disk files, which grow as guests are used and as snapshots accumulate, and a network connection that guests can share or bridge to reach other devices and the internet. Assigning more resources than the host can spare slows everything, including the host itself, so sizing a guest is a balance, not a race to the highest numbers. Security needs the same attention as a physical fleet. Patch each guest operating system and its applications, patch the hypervisor and the host as well, and remove or power off forgotten VMs so they do not sit unpatched and unnoticed. A snapshot saves the state of a VM at a point in time, so you can return to that state after a failed change, which makes snapshots useful before updates and experiments. Isolation is the other major benefit. Technicians can test software, practice an install, or examine a risky file inside a VM, while the host and the production network stay separate from the test environment.
Worked example
A help desk technician supports a small office where staff open a web browser to use email, calendars, and a shared word processor. Staff never install, patch, or update the applications. Which cloud service model is in use?
Software as a Service delivers finished applications over the internet. The provider runs, patches, and updates the software, and users simply sign in and use it.
Why the other options are wrong
- BInfrastructure as a Service: Infrastructure as a Service provides virtual servers, storage, and networking. Customers still install and manage their own operating systems and applications.
- CPlatform as a Service: Platform as a Service provides a development and runtime environment for building applications. End users doing office work are not using a development platform.
- DVirtual desktop infrastructure: Virtual desktop infrastructure hosts complete desktop environments on central servers. The scenario describes individual web applications, not a hosted desktop.
Acronyms and terms in this domain
| Term | What it means |
|---|---|
| VM | Virtual Machine, a software based computer that runs its own guest operating system on a host |
| VDI | Virtual Desktop Infrastructure, complete desktop environments hosted on central servers and reached over a network |
| IaaS | Infrastructure as a Service, rented virtual servers, storage, and networking, with the customer managing operating systems and applications |
| PaaS | Platform as a Service, a managed platform for building and running applications, with the provider managing the underlying servers and runtime |
| SaaS | Software as a Service, finished applications delivered over the internet and managed by the provider |
| Hypervisor | The software that creates virtual machines and divides host resources among them |
| Snapshot | A saved state of a virtual machine at a point in time, used to return the machine to that state later |
| Host | The physical computer that provides the processor, memory, storage, and network resources a virtual machine uses |
| Guest | The virtual machine itself, or the operating system running inside a virtual machine on a host |
| Thin client | A lightweight endpoint device with minimal local resources, used mainly to connect to hosted desktops or services |
Where the help desk meets this domain
You meet the cloud half of this domain in ordinary account and file tickets. A user cannot sign in to hosted email, so you check the password, the account status, and multifactor settings in an admin portal instead of visiting a mail server. A shared document will not update on one laptop, so you check whether synchronization is paused, whether the user is signed in to the right account, whether storage is full, and whether two people edited the same file and created a conflict copy. A new staff member needs a mailbox, a calendar, and access to shared files on the first morning, and all of that is provisioned in the cloud services, not installed from discs at the desk. In each case the provider runs the servers and the application updates, while your team owns the accounts, the permissions, and the data, which is the shared responsibility model in daily form. Knowing which side owns a problem tells you whether to fix a setting, coach the user, or escalate to the provider status page.
You meet the virtualization half when you build test setups, support training machines, or troubleshoot a workstation that runs a second operating system for one legacy task. A VM that will not start often points to virtualization support turned off in the firmware, too little free RAM once the host and other guests are counted, or a virtual disk that has filled the host drive. A slow guest often needs its memory or processor allocation adjusted, or a forgotten snapshot removed under your change process. You also use isolation on purpose. You can install an update inside a VM first, snapshot it before a risky change, and roll back in minutes when the change breaks something, instead of rebuilding a physical machine. Remote and hybrid staff add the VDI version of the same work. A user connects from a thin client or a home laptop to a hosted desktop, and your checks cover the connection, the sign in, and the session, rather than the health of a full local install.
Traps to watch for
The Type 1 and Type 2 trap turns on one question: what sits directly under the hypervisor. A Type 1 hypervisor sits on bare metal, meaning it installs directly on the hardware and is itself the first software layer, even if management tools make it look like a normal system. A Type 2 hypervisor sits on top of a host operating system, so if a scenario says a technician installed a program on Windows or macOS and then created a Linux VM inside that program, the answer is Type 2, no matter how powerful the machine is. The reverse trap describes a server where the hypervisor was installed on empty hardware before any guests were created, and then offers a hosted product name as a distractor. Ignore brand familiarity and read the layering in the stem. Hardware first means Type 1. Operating system first, hypervisor as an application second, means Type 2. That single check settles most hypervisor questions in this domain.
The SaaS and VDI trap is close behind, because both deliver software to a user over a network and both can open inside a window on a local screen. The difference is the size of what is delivered. SaaS delivers one finished application, such as email or a word processor in a browser tab, and the user signs in to that application only. VDI delivers a complete desktop environment, with its own start menu, desktop, and set of applications, hosted on a central server and viewed remotely. If the stem mentions a full desktop session, a thin client connecting to a hosted desktop, or the same standard desktop image given to many staff, it points to VDI. If it mentions staff opening a browser to use one or two named applications that the provider patches, it points to SaaS. A related trap mixes IaaS into the same story. Renting a virtual server and installing your own operating system and applications on it is IaaS, even when you reach that server through a browser based console.
Now try it. The 3 free sample questions for this domain are in practice mode, with full explanations.
Practice Domain 4 questions