Cloud Deployment Models and Characteristics Explained
Whether you are studying for a certification exam or just trying to understand cloud computing properly, the deployment models and core characteristics defined by NIST (the U.S. National Institute of Standards and Technology) come up constantly. Getting comfortable with the underlying cloud computing terminology first makes this material easier to follow. This guide breaks down the three main deployment models, the five defining characteristics, and how to tell them apart with confidence.
The NIST Definition of Cloud Computing
Most cloud computing terminology used today traces back to a single NIST publication, which defines cloud computing as a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned with minimal management effort. This definition is the basis for almost every certification exam question on the topic.
The Three (or Four) Cloud Deployment Models
NIST originally defined four deployment models, though many courses simplify this to three by treating community cloud as a niche variant. Understanding each one clearly is the fastest way to answer “match the model to the description” style questions correctly.
Public Cloud
Public cloud infrastructure is provisioned for open use by the general public and is owned, managed, and operated by a business, academic, or government organisation, or some combination of them. It exists on the premises of the cloud provider. AWS, Microsoft Azure, and Google Cloud are the three dominant public cloud providers.
Private Cloud
Private cloud infrastructure is provisioned for exclusive use by a single organisation comprising multiple internal users. It may be owned, managed, and operated by the organisation itself, a third party, or a combination, and may exist on or off premises. This is generally considered the most versatile model when data control and compliance are the priority, since it gives an organisation full control over configuration.
Community Cloud
Community cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organisations that share common concerns, such as compliance requirements or a shared mission. Government agencies with shared regulatory needs are a common real-world example.
Hybrid Cloud
Hybrid cloud is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities but are bound together by standardised technology that enables data and application portability. This is often considered the most versatile model overall, since it allows an organisation to keep sensitive workloads private while using public cloud resources for less sensitive, more elastic needs.
Which Cloud Model Is Most Versatile?
This is a common exam-style question with a nuanced answer. If the question is about balancing control and scalability, hybrid cloud is generally the correct answer, since it combines the benefits of private control with public cloud flexibility. If the question is specifically about compliance and data control alone, private cloud is usually the intended answer.
The Five Essential Characteristics of Cloud Computing
Beyond deployment models, NIST defines five essential characteristics that distinguish true cloud computing from simply running a server remotely. All five typically appear together in some form on certification exams.
On-Demand Self-Service
A consumer can provision computing capabilities, such as server time and network storage, automatically without requiring human interaction with the service provider. This is what allows a developer to spin up a new server in minutes through a web console rather than filing a request and waiting for IT to act.
Broad Network Access
Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous client platforms, such as laptops, tablets, and smartphones. This is the characteristic behind the common exam statement that “all cloud technologies must be accessed over the internet,” though the more precise wording is that they must be accessible over a network using standard protocols, not necessarily the public internet in every private cloud case.
Resource Pooling
The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned according to demand. The consumer generally has no control or knowledge over the exact physical location of the resources provided.
Rapid Elasticity
Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward with demand. To the consumer, the capabilities available for provisioning often appear unlimited and can be appropriated in any quantity at any time.
Measured Service
Cloud systems automatically control and optimise resource use by leveraging a metering capability appropriate to the type of service, such as storage, processing, bandwidth, or active user accounts. Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and the consumer, and forming the basis of pay-as-you-go billing.
Quick Reference Table
| Model/Characteristic | Key Identifier |
| Public Cloud | Open to general public, provider-owned infrastructure |
| Private Cloud | Exclusive to one organisation |
| Community Cloud | Shared by organisations with common concerns |
| Hybrid Cloud | Combination of two or more distinct clouds |
| On-Demand Self-Service | No human interaction needed to provision |
| Broad Network Access | Accessible via standard network protocols on any device |
| Resource Pooling | Multi-tenant, shared physical resources |
| Rapid Elasticity | Scales up or down automatically |
| Measured Service | Usage is metered and billed accordingly |
Common Exam Mistakes to Avoid
- Confusing “broad network access” with “requires the public internet”, private clouds can satisfy this characteristic over a private network
- Assuming hybrid cloud always means “public plus private”, it can technically combine any two or more of the four models
- Mixing up deployment models (who can use the cloud) with service models like IaaS, PaaS, and SaaS (what is being delivered)
Frequently Asked Questions
What are the three types of cloud deployment models?
Many courses simplify NIST’s four models down to three commonly taught types: public, private, and hybrid, treating community cloud as a specialised variant rather than a fourth core category.
Which cloud characteristic is most often tested on exams?
On-demand self-service and broad network access tend to appear most frequently, since they are the two characteristics most often confused with general web hosting or virtualisation.
Conclusion
The NIST deployment models and five characteristics form the vocabulary underpinning almost all cloud computing terminology. Once the distinction between “who can use it” (deployment models) and “what defines it as cloud” (the five characteristics) is clear, most related exam questions and real-world architecture decisions become far more straightforward.
About the Author
