Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Cloud computing is foundational to understanding how modern technology systems operate, and exams test more than just definitions. You need to recognize how cloud services solve real problems: scalability, resource efficiency, abstraction of complexity, and distributed systems design. When you encounter questions about cloud computing, connect specific services to the underlying principles they demonstrate.
Think of cloud computing as a spectrum of abstraction levels, from managing raw hardware yourself to simply using software through a browser. Each service model trades control for convenience, and understanding this tradeoff is key to answering both multiple-choice and free-response questions effectively. Don't just memorize what IaaS, PaaS, and SaaS stand for. Know why each exists and what problems it solves.
Cloud services are organized by how much of the technology stack the provider manages for you. The more abstraction, the less control you have, but also the less responsibility.
IaaS gives you virtualized computing resources (servers, storage, networking) delivered over the internet. Think of it as renting raw building blocks instead of buying physical hardware.
PaaS abstracts away infrastructure management so developers can focus on building and deploying applications without configuring servers or networks.
SaaS delivers complete applications via subscription. Users access software through a browser without installation, updates, or maintenance responsibilities.
Compare: IaaS vs. SaaS: both eliminate on-premises hardware needs, but IaaS gives you control over the entire software stack while SaaS gives you none. If an FRQ asks about tradeoffs between control and convenience, this comparison is your go-to example.
These technologies maximize hardware efficiency by sharing physical resources across multiple users and workloads while maintaining isolation and performance.
A hypervisor sits on top of physical hardware and creates virtual instances of entire machines. Multiple operating systems run simultaneously on a single physical server, each believing it has its own dedicated hardware.
Containers package an application along with all its dependencies into a lightweight, portable unit that runs consistently across any environment. Unlike VMs, containers share the host operating system's kernel, which makes them much smaller and faster to start.
With serverless, you write functions that execute in response to events (like an HTTP request or a database change) without ever provisioning or managing a server. The cloud provider handles all infrastructure behind the scenes.
Compare: Virtualization vs. Containerization: both enable resource sharing, but VMs virtualize entire machines (including the OS) while containers virtualize only the application layer. Containers are lighter and faster to start, making them ideal for microservices. VMs provide stronger isolation, making them better when you need to run different operating systems or require strict security boundaries.
These concepts address how cloud systems automatically adjust to varying workloads while maintaining performance and availability.
Scalability is the capability to add resources to handle growth. Elasticity is the automatic, real-time adjustment of resources based on current demand. The distinction matters.
A load balancer distributes incoming traffic across multiple servers so no single server becomes overwhelmed.
Compare: Scalability vs. Elasticity: scalability is the capability to grow, while elasticity is automatic adjustment. A scalable-but-not-elastic system can handle more load, but someone has to manually provision the extra resources.
Cloud storage solutions address how data is stored, protected, and made accessible across distributed systems.
Cloud storage lets users store and retrieve data over the internet without managing physical drives. Services like Amazon S3, Google Cloud Storage, and Azure Blob Storage are common examples.
Data centers are the physical infrastructure hubs that house the servers, storage, and networking equipment powering cloud services. Their placement around the globe is strategic.
Compare: Cloud Storage vs. Local Storage: cloud storage offers accessibility and redundancy but depends on internet connectivity; local storage offers speed and offline access but requires manual backup and lacks remote accessibility.
These patterns represent how applications are structured to leverage cloud capabilities effectively.
Instead of building one large application (a monolith), microservices decompose it into independent services. Each service handles a specific function and communicates with others via APIs.
Compare: Microservices vs. Monolithic Architecture: monoliths are simpler to develop initially but become difficult to scale and update as they grow; microservices add upfront complexity but enable independent scaling and faster iteration on individual features.
These practices ensure cloud systems remain secure, compliant, and performing optimally over time.
The shared responsibility model is the most important concept here. The cloud provider secures the underlying infrastructure (physical servers, network hardware, hypervisors), while the customer secures their own data, access configurations, and application code.
Cloud networking connects cloud resources using virtual networks, enabling secure communication between services and users.
Monitoring tools track resource performance and health metrics to ensure systems operate within expected parameters.
Compare: Cloud Security vs. Traditional Security: cloud security must address shared infrastructure and remote access but benefits from provider expertise and scale; traditional security offers more direct control but requires in-house expertise for all layers.
| Concept | Best Examples |
|---|---|
| Abstraction levels | IaaS, PaaS, SaaS |
| Resource efficiency | Virtualization, Containerization, Serverless |
| Handling demand | Scalability/Elasticity, Load Balancing |
| Data persistence | Cloud Storage, Data Centers |
| Application architecture | Microservices, Containerization |
| Deployment strategies | Multi-cloud, Hybrid Cloud |
| Security practices | Encryption, Compliance, Shared Responsibility |
| Operational management | Monitoring, Networking, Load Balancing |
Which two service models (IaaS, PaaS, or SaaS) would you compare to illustrate the tradeoff between developer control and operational simplicity?
A company needs to handle traffic spikes during product launches but wants to minimize costs during slow periods. Which two concepts best address this need, and how do they differ?
Compare and contrast virtualization and containerization: What does each virtualize, and when would you choose one over the other?
An FRQ describes a healthcare company that must keep patient data within national borders while using cloud services for non-sensitive workloads. Which deployment strategy addresses this, and why?
Explain how the shared responsibility model in cloud security divides obligations between the provider and the customer. Give one specific example of each party's responsibility.