Cloud Concepts and the AWS Value Proposition

The Cloud Practitioner (CLF-C02) exam opens with the "why" of cloud before any specific service. Examiners want to confirm you can explain what cloud computing is, tell the deployment and service models apart, and recite the business value AWS delivers. Anchor these definitions cold and a whole block of easy points becomes automatic.

Core Idea

• Cloud computing is the on-demand delivery of IT resources — compute, storage, databases — over the internet with pay-as-you-go pricing, so you provision what you need in minutes instead of buying hardware upfront.
• The cloud shifts spending from CapEx (large upfront purchases of servers and data centers) to OpEx (variable operational spending you only pay for what you use).
• AWS frames its business case as six advantages of cloud — memorize them, because the exam quotes them almost verbatim.

The Six Advantages of Cloud

AWS lists exactly six benefits, and the exam tests them by matching a scenario to the right phrase:

• Trade capital expense for variable expense — stop paying upfront for servers you might use; pay only when you consume.
• Benefit from massive economies of scale — aggregated usage from millions of customers lets AWS pass lower pay-as-you-go prices to you.
• Stop guessing capacity — scale up or down on demand instead of over- or under-provisioning hardware.
• Increase speed and agility — new IT resources are a click away, dropping provisioning time from weeks to minutes.
• Stop spending money running and maintaining data centers — focus on customers and applications, not on racking servers and managing power.
• Go global in minutes — deploy to multiple AWS Regions worldwide with a few clicks for lower latency to users.

Deployment Models

The deployment model describes where your infrastructure lives:

• Cloud (all-in cloud): the application is fully deployed in the cloud, with all parts running on cloud resources — the model for cloud-native, born-in-the-cloud apps.
• Hybrid: cloud resources are connected to on-premises infrastructure, common when regulation, legacy systems, or latency require keeping some assets in your own data center while extending into AWS.
• On-premises (private cloud): resources are deployed in your own data center using virtualization and resource-management tools; this is not AWS cloud but appears as a contrast on the exam.

Service Models: IaaS, PaaS, SaaS

The service model describes how much AWS manages versus you:

• IaaS (Infrastructure as a Service): the basic building blocks — networking, computers, storage. You control the OS and everything above it. Think EC2. Maximum flexibility and control.
• PaaS (Platform as a Service): AWS manages the underlying infrastructure (OS, patching, capacity) so you focus only on deploying and managing your application and data. Think Elastic Beanstalk.
• SaaS (Software as a Service): a completed product run and managed by the provider; you just use it. Think web-based email. You manage almost nothing but your own usage.

Elasticity vs. Scalability

These two terms are constantly confused on the exam, so separate them clearly:

• Scalability is the ability to grow — adding capacity (bigger or more resources) to handle increased load. It is often planned and can be manual.
• Elasticity is automatic, real-time expansion and contraction of resources to match current demand, so you add capacity during spikes and release it when demand falls to control cost.

A rigid on-premises data center can be scalable but is rarely elastic, because releasing hardware you already bought saves nothing.

High-Yield Exam Patterns

• A scenario about "not paying upfront for servers" maps to trade capital expense for variable expense.
• "Deploying to users around the world with a few clicks" maps to go global in minutes.
• If a question stresses automatic scaling up and down with demand, the answer is elasticity, not scalability.
• "Full control of the operating system" signals IaaS; "just use the finished software" signals SaaS.
• A company keeping some systems in its own data center while using AWS is describing a hybrid deployment.
• Cloud moving spending from upfront purchases to usage-based billing is the CapEx to OpEx shift.

Common Traps to Avoid

• Do not confuse elasticity (automatic, bidirectional) with scalability (growth, often manual).
• Do not call a private on-premises data center "cloud" — being virtualized does not make it AWS cloud.
• Do not mix up the six advantages' wording; "economies of scale" is about aggregated demand lowering prices, not about a single customer's usage.
• Remember variable expense = OpEx and capital expense = CapEx; reversing them is a common distractor.
• SaaS does not give you OS control — if the question needs OS-level access, it is IaaS.