Everyday Guidebooks
Cover of CompTIA A+ Core 1

Cybersecurity & IT

CompTIA A+ Core 1: Virtualization and Cloud Concepts

An Unofficial 220-1201 Topic Guide to Virtual Machines, Cloud Service Models, and Shared Resources

by Todd Michael

Available now

Virtual machine or container? SaaS or PaaS? Public cloud or private cloud? Small distinctions can make a big difference when you are studying for Core 1.

This focused, unofficial guide helps comptia a+ candidates understand the virtualization and cloud concepts relevant to the 220-1201 exam. Starting with physical hosts and virtual machines, it builds toward cloud service models, deployment models, resource pooling, and the practical trade-offs behind common scenarios.

Inside, you will find plain-English explanations, side-by-side comparisons, original review questions, and answer rationales that explain why similar choices differ. Short scenarios connect terminology to the kinds of decisions an entry-level technician may encounter.

Use this book to strengthen a challenging topic area alongside a complete Core 1 study plan. It is not a full-exam guide and is not affiliated with or endorsed by CompTIA.

Contents
  1. 1. The Virtualization and Cloud Landscape
  2. 2. Physical Hosts and Virtual Machines
  3. 3. Hypervisors and Virtualization Requirements
  4. 4. Building and Running a Virtual Machine
  5. 5. Virtual Machine Uses and Lifecycle
  6. 6. Virtual Networks and Shared Resources
  7. 7. Containers and Virtual Machines
  8. 8. Cloud Computing Fundamentals
  9. 9. Cloud Service Models
  10. From Infrastructure to Finished Software
  11. Infrastructure as a Service
  12. Platform as a Service
  13. Software as a Service
  14. Comparing the Responsibility Boundary
  15. One Business Need, Three Approaches
  16. Service Models Are Not Deployment Models
  17. Practice Questions
  18. Answers and Explanations
  19. Chapter Takeaways
  20. 10. Cloud Deployment Models
  21. 11. Elasticity, Scalability, and Availability
  22. 12. Cloud Storage and Shared Responsibility
  23. 13. Scenario-Based Topic Review
  24. Scenario 1: A Safe Place to Test
  25. Scenario 2: A Crowded Host
  26. Scenario 3: Choosing a Virtual Network
  27. Scenario 4: Reversing a Risky Change
  28. Scenario 5: Packaging an Application
  29. Scenario 6: Selecting a Cloud Service
  30. Scenario 7: Service Model or Deployment Model?
  31. Scenario 8: Responding to Variable Demand
  32. Scenario 9: More Copies, Fewer Assumptions
  33. Scenario 10: Responsibility at the Right Layer
  34. Turning Clues Into Answers
  35. 14. Final Review and Study Plan
  36. Other Books by Todd Michael

Read a sample: 1. The Virtualization and Cloud Landscape

A technician receives a request for a computer that a training team can use to test a new application. The team needs its own operating system, but the organization does not want to purchase another physical computer for a short project.

One option is to create a virtual machine: a software-based computer that uses a share of an existing physical machine’s resources. The training team can install an operating system and application inside it. If the physical machine has enough capacity, other virtual machines can run alongside it.

Now suppose the organization obtains a similar virtual machine from a cloud provider instead. The team may be able to request it through a web portal and pay according to the provider’s pricing model. The virtual machine still depends on physical hardware somewhere, but the organization does not necessarily own or maintain that hardware.

These two situations are related, but they are not identical. Virtualization is a technology for creating virtual versions of computing resources. Cloud computing is a way of providing access to computing services, often using virtualization as part of the underlying infrastructure. Understanding that distinction will help you avoid one of the most common mistakes in this topic: assuming that anything virtual must be in the cloud.

This chapter gives you a map of the landscape before you work through its individual parts. It also includes a diagnostic review. You do not need to know every answer yet; the purpose is to discover where your understanding is already strong and where further study will be useful.

This book focuses on virtualization and cloud concepts relevant to the CompTIA A+ Core 1 220-1201 exam. It is an independent topic guide, not an official CompTIA publication and not a replacement for a complete Core 1 study guide. Use it to strengthen your understanding of this area while continuing to study the other exam domains.

You will begin with the components of a virtual machine environment: physical hosts, virtual machines, guest operating systems, hypervisors, and shared resources. You will then examine common uses for virtual machines, their lifecycle, virtual networking, and the distinction between virtual machines and containers.

The cloud chapters build on that foundation. They cover cloud characteristics, service models, deployment models, elasticity, availability, storage, and shared responsibility. Later scenario-based reviews bring those ideas together so you can practice identifying the important clues in a question.

Exam objectives and details can change. Verify the current official objectives for the exam version you plan to take, and use them to check your overall preparation. The goal here is not merely to memorize labels, but to understand them well enough to recognize them in unfamiliar wording.

Every virtual machine and cloud service ultimately depends on physical equipment. That equipment includes processors, memory, storage devices, network interfaces, and the facilities that supply power and cooling. Software can divide, manage, and present those resources in flexible ways, but it cannot make the physical requirements disappear.

Consider a physical computer with a processor, installed memory, a storage drive, and a network connection. Its operating system and applications use those components. If the same computer runs virtual machines, the virtual machines also depend on those components, although each one sees a configured set of virtual hardware rather than directly functioning as a separate physical computer.

A physical computer that provides resources for virtual machines is commonly called a host. A virtual machine running on that host is often called a guest. The operating system installed inside the virtual machine is its guest operating system.

For example, a host might run two virtual machines for a training lab. One guest could use a Windows operating system, while another uses a Linux operating system. Each guest has its own operating-system environment and can run compatible applications. Both, however, rely on the host’s physical resources.

This arrangement can make better use of hardware and simplify certain kinds of testing. It also introduces a practical limit: multiple guests compete for resources supplied by the same host. Creating more virtual machines does not create more physical memory or processing capacity. If the host is overloaded, performance can suffer.

Virtualization uses software to create an abstracted version of a computing resource. In this book, the initial emphasis is on virtualizing computers: presenting virtual CPU, memory, storage, and network interfaces to a virtual machine.

The software that creates and manages virtual machines is a hypervisor. It helps allocate the host’s resources to guests and provides the environment in which those guests run. A virtual machine behaves in many ways like a separate computer, even though it shares physical infrastructure with other workloads.

Imagine a technician who needs to test an operating-system configuration without changing the operating system on a daily-use laptop. A virtual machine can provide a separate environment for that test. The technician can install the guest operating system, make the desired configuration changes, and observe the results without treating the laptop’s primary operating system as the test system.

That separation is useful, but it should not be mistaken for unlimited protection. Virtual machines still require sound configuration and security practices. They also depend on the host: a host failure can affect the guests running on it.

Virtualization is not restricted to a particular location. A virtual machine might run on a technician’s laptop, on a server in an organization’s own facility, or on infrastructure operated by a provider. Its location and management…

More Cybersecurity & IT

Cover of The White Hat Bible, Volume 1The White Hat Bible, Volume 1Available nowCover of The White Hat Bible, Volume 2The White Hat Bible, Volume 2Available nowCover of The White Hat Bible, Volume 3The White Hat Bible, Volume 3Available nowCover of The White Hat Bible, Volume 4The White Hat Bible, Volume 4Available nowThe White Hat Bible, Volume 5Available nowCover of The White Hat Pocket GuideThe White Hat Pocket GuideAvailable now

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.