Objective. Students will accurately define the five essential characteristics, three service models, and four deployment models of cloud computing as described in NIST SP 800-145, and match each to a workplace scenario.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Cloud computing means delivering computing resources—servers, storage, databases, networking, software, and more—over the internet ("the cloud") on demand. Instead of buying and maintaining physical hardware in a back room, organizations rent what they need and pay only for what they use. To avoid confusion caused by marketing hype, the National Institute of Standards and Technology (NIST) published a concise, authoritative definition in NIST Special Publication 800-145. This two-page document is the accepted industry baseline, and both CompTIA A+, Network+, and the Cisco CCST/CCNA exams expect you to know it.
---
NIST SP 800-145 states that a true cloud service must exhibit all five of the following characteristics.
1. On-Demand Self-Service
A user can provision computing capabilities—such as server time or storage—automatically, without requiring human interaction from the service provider. Example: a technician spins up a virtual machine in a web portal at 2 a.m. without calling anyone.
2. Broad Network Access
Capabilities are available over the network and accessed through standard mechanisms (web browsers, mobile apps, command-line tools) that work across a wide variety of client devices. This is why a salesperson can reach company files from a laptop in a hotel or a smartphone on the road.
3. Resource Pooling
The provider pools computing resources to serve multiple customers using a multi-tenant model. Physical and virtual resources are dynamically assigned and reassigned based on demand. Individual customers generally do not know or control exactly which physical machine they are using at any moment.
4. Rapid Elasticity
Capabilities can be scaled out or in quickly—sometimes automatically—to match demand. From the user's perspective, the resources often appear unlimited and can be purchased in any quantity at any time. A retail website that scales up on Black Friday and scales back down in January is a classic example.
5. Measured Service
Cloud systems automatically monitor and report resource use, providing transparency for both the provider and the customer. Storage, processing, bandwidth, and active user accounts can all be metered. This is the basis for pay-as-you-go billing.
---
NIST defines three layers of cloud service, often shown as a stack.
Infrastructure as a Service (IaaS)
The provider delivers fundamental computing resources: virtual machines, storage, and networking. The customer installs and manages the operating system, middleware, and applications. Example: Amazon EC2 or a raw storage bucket in AWS S3.
Platform as a Service (PaaS)
The provider delivers a ready-made environment where developers deploy applications without managing the underlying infrastructure or operating system. The customer controls the application and its configuration but not the servers below it. Example: Google App Engine or Microsoft Azure App Service.
Software as a Service (SaaS)
The provider delivers a complete, ready-to-use application over the internet. The customer uses the software but manages nothing below the application layer. Example: Microsoft 365 (Word, Teams, Exchange Online) or Google Workspace.
A helpful memory device: IaaS = I manage the OS; PaaS = Platform handles the OS; SaaS = Software only, hands off.
---
Deployment models describe who owns, operates, and has access to the cloud infrastructure.
Public Cloud
Infrastructure is owned and operated by a third-party provider and shared among many customers over the internet. Cost is typically lowest; physical control is lowest. Examples: AWS, Microsoft Azure, Google Cloud Platform.
Private Cloud
Infrastructure is provisioned for the exclusive use of a single organization. It may be owned, managed, and operated by the organization itself, a third party, or both, and it may exist on or off the organization's premises. A corporate VMware farm hosted in the company's own data center is a common example.
Community Cloud
Infrastructure is shared by several organizations that have common concerns—such as regulatory requirements, security needs, or a shared mission. Example: a cloud environment shared among several hospitals that must all comply with HIPAA.
Hybrid Cloud
A combination of two or more distinct cloud infrastructures (private, community, or public) that remain unique but are bound together by technology that enables data and application portability. Example: a company keeps sensitive payroll data on a private cloud but hosts its public website on a public cloud provider.
---
As an IT support technician or network specialist, you will encounter cloud services every day: configuring email through Microsoft 365 (SaaS), provisioning virtual servers on a public IaaS platform, or supporting users who access a company application hosted in a private VMware environment. Knowing the NIST vocabulary lets you:
---
Cloud environments do not involve the same physical electrical hazards as hardware work, but professional responsibilities still apply. Accessing cloud consoles with administrative credentials requires the same discipline as physical access to a server room: use strong, unique passwords and multi-factor authentication (MFA), follow your organization's acceptable-use policy, and never provision resources or access data beyond your authorization level. Misconfigurations in cloud platforms—such as leaving a storage bucket publicly accessible—can expose sensitive data to the entire internet. Treat every cloud console action with the same care you would give to working inside a live server.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.