Study Hub / AWS Certified Cloud Practitioner (CLF-C02) / Domain 1.0
AWS Certified Cloud Practitioner (CLF-C02) Domain 1.0: Cloud Concepts — Explained
Domain 1.0 answers "what is the cloud, really?" — the definition, the business benefits that drive adoption, the deployment models, and the shared responsibility line that every later domain assumes you understand.
What "cloud computing" actually means
The standard definition: on-demand delivery of IT resources over the internet with pay-as-you-go pricing. Instead of buying servers, you rent capacity by the second.
- On-demand self-service — provision resources yourself, no ticket to IT, no purchase order.
- Broad network access — available over the network from anywhere, on standard devices.
- Resource pooling — the provider's hardware serves many customers (multi-tenancy), with logical isolation between them.
- Rapid elasticity — scale out and in automatically with demand. The cloud's signature trait.
- Measured service — usage is metered and billed. You pay for what you consume — and only what you consume.
The six business benefits (the exam's list)
- Trade capital expense for variable expense — no data-center build-out; costs scale with usage (CapEx → OpEx).
- Benefit from massive economies of scale — AWS buys at a scale you can't, and some of that flows to your bill.
- Stop guessing capacity — no more buying for the peak and idling the rest; scale to actual demand.
- Increase speed and agility — environments in minutes, not procurement cycles. Experimentation gets cheap.
- Stop spending money running data centers — undifferentiated heavy lifting (racking, power, cooling) becomes AWS's problem.
- Go global in minutes — deploy to regions worldwide from one console, putting apps near customers.
Deployment models and shared responsibility
- Cloud (all-in) — everything on AWS. Maximum elasticity, minimum data-center.
- Hybrid — cloud plus on-premises, connected. For regulated data, legacy systems, or gradual migration.
- On-premises (private cloud) — cloud-style tooling in your own data center. Control first, elasticity second.
- Shared responsibility — AWS secures of the cloud (facilities, hardware, virtualization); you secure in the cloud (your data, your configs, your access management). The line moves with the service: IaaS leaves you the OS; managed services take more.
The must-memorize table: who secures what
The shared-responsibility line, by service type.
| Service type | AWS ("of" the cloud) | Customer ("in" the cloud) |
|---|---|---|
| IaaS (EC2) | Hardware, facilities, virtualization | Guest OS, apps, data, firewall rules, IAM |
| Managed service (RDS) | Hardware, OS, database engine patching | Data, access, parameter config |
| SaaS-like (e.g., WorkDocs) | Everything below the app | Your data and who can see it |
| Always customer | — | Data classification, IAM users/roles, encryption choices |
Try it: 4 sample questions
Sample questions to check your understanding of this domain. Answers and full reasoning are tucked under each one.
1. A startup wants to avoid buying servers and instead pay only for the compute it uses each month. Which cloud benefit is this?
- A. A. Go global in minutes
- B. B. Trade capital expense for variable expense
- C. C. Benefit from economies of scale
- D. D. Increase speed and agility
Show answer & reasoning
B. Buying servers is capital expense (CapEx) — big upfront, wasted when idle. Pay-per-use is variable expense (OpEx): costs track usage. That CapEx→OpEx shift is the benefit being described. Economies of scale (C) is about AWS's bulk purchasing lowering unit costs — related, but not what's asked.
2. A company leaves an S3 bucket publicly readable and customer data leaks. Under the shared responsibility model, who is responsible?
- A. A. AWS — S3 is their service
- B. B. The customer — data and access configuration are the customer's responsibility
- C. C. Both equally — shared means shared
- D. D. Nobody — S3 defaults are AWS's choice
Show answer & reasoning
B. "Shared" doesn't mean "blurred": AWS secures the S3 service (of the cloud); the customer configures buckets, policies, and data classification (in the cloud). A public bucket is a customer configuration error, full stop. This is the single most-tested shared-responsibility scenario.
3. An application gets 10x traffic every evening and nearly none overnight. Which cloud characteristic handles this most cost-effectively?
- A. A. Resource pooling
- B. B. Rapid elasticity with pay-as-you-go pricing
- C. C. Broad network access
- D. D. Measured service alone
Show answer & reasoning
B. Elasticity scales capacity with the evening spike and releases it overnight; pay-as-you-go means you only pay for the spike hours. Either trait alone is weaker — elasticity without metering wouldn't save money, and metering without elasticity wouldn't handle the spike.
4. A hospital must keep patient records in its own data center but wants to burst analytics workloads to AWS. Which deployment model is this?
- A. A. All-in cloud
- B. B. Hybrid — on-premises plus cloud, connected
- C. C. Private cloud only
- D. D. Multi-cloud
Show answer & reasoning
B. Sensitive data stays on-premises while elastic workloads burst to the cloud — the textbook hybrid pattern, typically for regulation, latency, or legacy reasons. All-in (A) would move the records too; private-only (C) gets no cloud bursting.
This was one domain. The simulator drills all 4.
This free preview covered Cloud Concepts (Domain 1.0, 24%). Not covered here: Cloud Technology and Services (Domain 3.0, 34%). The entire largest domain — every core AWS service deep-dive — plus advanced shared-responsibility scenarios and compliance-program detail stay in the paid guide and practice bank. The ByteBar Practice Exam Simulator drills every domain with 1,000 exam-style questions — $9.99 one-time unlocks all 28 exams. Prefer to read? The full AWS Cloud Practitioner Study Guide is in the ByteBar shop on Etsy.
Practice Exam Simulator — $9.99 one-time, all 28 exams Full Study Guides on Etsy