Lesson 8: Virtualization and Cloud
CompTIA A+ Core 1 (220-1201) · Objectives 220-1201 4.1, 220-1201 4.2, 220-1202 1.11 · Download .docx
Objectives
- Explain virtualization concepts: hypervisors, VM networking, containers, sandboxes and resource requirements.
- Summarize cloud computing concepts: IaaS, PaaS, SaaS, deployment models, elasticity, metered use and file sync.
- Use cloud-based productivity tools: email, storage and sync, collaboration and identity synchronization.
Key terms
- VM
- Virtual machine: software-based computer with its own virtual CPU, memory, disk and network that runs a full operating system on shared physical hardware.
- Private cloud
- Cloud infrastructure operated for a single organization, on-premises or hosted, giving the most control and isolation.
- Cloud email system
- Hosted email service, managed by a provider rather than on-premises servers, accessed through web browsers or mail apps.
- Sandbox
- Isolated environment where untrusted software or files can run without being able to affect the real system or network.
- Public cloud
- Cloud infrastructure owned by a provider and offered to the general public over the internet on a pay-as-you-go basis.
- Cloud storage sync
- Service setting that keeps chosen local folders matched with copies in online storage, including options for files kept online-only.
- Test and development environment
- Virtual machines used to build and test software or updates safely, using snapshots to roll back changes.
- Hybrid cloud
- Combination of private and public clouds linked together so data and applications can move between them.
- Collaboration tools
- Cloud apps for spreadsheets, documents, presentations, videoconferencing, and instant messaging that let multiple people work together in real time.
- Application virtualization
- Running an application in an isolated or streamed environment separate from the local OS, so it works without a traditional installation.
- Community cloud
- Cloud infrastructure shared by several organizations with common concerns, such as compliance or mission, and managed by them or a third party.
- Identity synchronization
- Process of copying user accounts and credentials from an on-premises directory to a cloud identity service so users sign in with one identity.
- Legacy software/OS support
- Using virtualization to keep running outdated operating systems or applications that will not work on current hardware or OS versions.
- IaaS
- Infrastructure as a Service: provider supplies virtual servers, storage and networking; the customer installs and manages the OS and everything above it.
- License assignment
- Allocating purchased software or cloud subscriptions to specific users or devices, which enables the apps and services they may use.
The concept
220-1201 4.1 — Explain virtualization concepts: hypervisors, VM networking, containers, sandboxes and resource requirements. VM as sandbox: A sandbox is an isolated environment where untrusted code can run without affecting the host or the network. VMs make good sandboxes because they can be cut off from the network and rolled back to a clean snapshot after each test. VMs for test development: Test development is a core purpose of VMs: one host can run several guest operating systems side by side, and snapshots let the developer roll each guest back to a known-good state in seconds. That is faster and cheaper than maintaining separate physical machines or reimaging after every test run. Legacy software in a VM: Application virtualization for legacy software runs an unsupported OS as a guest so its applications keep working on modern hardware. Because the guest OS is end-of-life, it should be isolated from the internet and backed up, but the business keeps its workflow while the host stays current. Cross-platform virtualization: Cross-platform virtualization runs one OS inside another. A Type 2 (hosted) hypervisor installs as an application on macOS, so the designer keeps her normal desktop and starts a Windows VM only when she needs the accounting software. Type 1 hypervisor definition: A Type 1 (bare-metal) hypervisor is installed directly on the server hardware and controls CPU, memory and I/O itself. With no general-purpose host OS consuming resources or adding attack surface, it is the standard choice for data centers and cloud providers. Choosing a hypervisor for servers: In the Type 1 stack nothing sits between the hardware and the hypervisor, so host resources go to the VMs and there is no general-purpose OS to patch or attack. The Type 2 stack adds a full host OS layer, which suits desktops and labs but adds overhead and another component that can fail or be exploited.
220-1201 4.2 — Summarize cloud computing concepts: IaaS, PaaS, SaaS, deployment models, elasticity, metered use and file sync. IaaS service model: In IaaS the provider supplies and manages the facility, physical servers, storage, networking and virtualization layer, while the customer manages everything from the guest OS up: OS patches, runtimes, applications and data. Renting VMs that the customer patches is the defining IaaS pattern. PaaS service model: PaaS gives developers a managed platform: the provider runs and patches the OS, middleware and language runtime and often scales the app automatically. The customer remains responsible for the application code and its data. SaaS service model: SaaS delivers a complete application over the internet. The provider runs and maintains the application and everything beneath it, while the customer manages its users, settings and the data it puts into the service. IaaS guest OS patching: In IaaS, the customer manages Data, Applications, Runtime, Middleware and the Operating system, while the provider manages Virtualization, Servers, Storage and Networking. A guest OS patch therefore falls to the school. PaaS shared responsibility: In PaaS the customer manages the Data and Applications layers, while the provider manages the runtime, middleware, OS and everything below. A third-party library that the developers selected and packaged with their code belongs to the Applications layer, so they must update the dependency and redeploy. Public cloud: A public cloud is owned and operated by a provider and offered to the general public. Customers share the provider's pooled infrastructure while remaining logically isolated from one another, gaining the most elasticity and pay-as-you-go pricing with the least control over the hardware.
220-1202 1.11 — Use cloud-based productivity tools: email, storage and sync, collaboration and identity synchronization. Cloud storage sync settings: Cloud storage sync clients can show the full folder structure while keeping files online-only, downloading each file only when it is opened (files on demand), or syncing only selected folders. This frees local space while keeping every file accessible. Identity synchronization: Identity synchronization copies user accounts (and, depending on the method, password hashes or authentication) from the on-premises directory to the cloud provider's directory. Users keep one identity across on-premises and cloud services, and account changes flow to the cloud automatically. License assignment: Being able to sign in shows that the identity has synchronized. Cloud productivity services provision a mailbox and grant app access only after a license that includes those services is assigned to the account, either directly or through group-based licensing. Cloud email client setup: Cloud email systems publish configuration through autodiscover (DNS records and a web service), so clients find the correct server, protocol and security settings from the email address. Mail, calendar and contacts then sync with the cloud mailbox on every device. Cloud email shared mailbox: Cloud email systems support shared mailboxes that several users open with their own credentials and permissions (read, send as, send on behalf). Access is granted and removed per user, sign-ins are individually logged, and MFA applies to each person. Cloud storage folder sync: Cloud storage sync clients let users choose which folders sync to each device (selective sync or adding a shortcut to a shared folder) and whether files are kept on the device or online-only. This saves space while keeping chosen folders available offline and synchronized.
Worked examples
Common mistakes
- Type 1 hypervisor definition: choosing “It streams hosted desktops from a data center to thin clients” is a common mistake. This describes VDI, a delivery model that may run on a Type 1 hypervisor but is not one.
- PaaS shared responsibility: choosing “The provider, because it manages the runtime layer in PaaS” is a common mistake. The provider patches the platform's language runtime, but a library bundled inside the customer's code is part of the application, not the runtime.
- Cloud email shared mailbox: choosing “Forward all its mail to each person's personal email” is a common mistake. Forwarding school mail to personal accounts leaks data and loses central control.
- Guest OS security: choosing “That is correct, because virtual machines cannot be infected by malware” is a common mistake. Guest operating systems are just as vulnerable to malware as physical machines.
- Application virtualization: choosing “Containers on each laptop” is a common mistake. Containers package an app with its dependencies to run on the local host's kernel; they would still be installed and run on each laptop.
- High availability design: choosing “File synchronization on staff laptops” is a common mistake. Local file copies on laptops do not keep a cloud-hosted platform online.
Self-check
Try each one before you look. A miss here costs nothing and tells you exactly what to reread.
Canvas is the official record. This companion enhances the PGCC curriculum; it does not replace it. Last name and class year only. Students with a 504 plan or IEP: your accommodations apply.