AWS CLF-C02 Glossary: Cloud Basics, Security, and Billing Terms

AWS CLF-C02 glossary of cloud basics, security, billing terms, traps, and decision cues.

Use this glossary when foundational AWS terms start to blur together. Keep it beside the cheat sheet and resources rather than treating it as a substitute for studying.

High-yield terms

Term Short meaning Why it matters on CLF-C02
Availability Zone Isolated location inside an AWS Region used for resilience Core HA and resilience concept
CAPEX Up-front capital spending model common in on-premises environments Part of cloud-economics comparisons
OPEX Ongoing operational spending model common in cloud consumption Cloud cost model contrast with CAPEX
Edge location AWS point of presence used by edge and content-delivery services Helps separate global edge services from Regions and AZs
Elasticity Ability to grow or shrink capacity quickly Core cloud benefit tested repeatedly
High availability Design approach that keeps service available despite failures Often contrasted with elasticity and fault tolerance
IaaS Infrastructure as a Service; customer manages more of the stack Foundational service-model classification
PaaS Platform as a Service; provider manages more of the runtime platform Helps compare managed levels
SaaS Software as a Service; provider manages the finished application High-level cloud model
Region Geographic AWS boundary containing multiple Availability Zones Core global infrastructure concept
Reserved pricing Discounted pricing model based on longer commitment Common pricing distractor
Scalability Ability to handle more work by growing capacity Frequently confused with elasticity
Shared responsibility model Security split between AWS and the customer One of the most tested CLF ideas
Support plan AWS service tier for guidance, response targets, and tooling Common business-fit question lane
Total cost of ownership Broader cost comparison, not just raw resource price Strong cloud economics concept
Fault tolerance Design that can keep operating through failure with less interruption Commonly confused with high availability
On-Demand pricing Pay for compute or services without long commitment Baseline pricing model
Spot pricing Discounted spare capacity with interruption risk Core pricing comparison concept
AWS Artifact AWS source for compliance reports and agreements High-yield compliance answer
AWS Budgets Tool for spend thresholds and alerts Frequently tested cost-control tool

Commonly confused pairs

Pair Keep this distinction clear
elasticity vs scalability fast adjustment versus broader capacity growth
high availability vs fault tolerance reduced downtime versus surviving failure with stronger continuity
Region vs Availability Zone geography boundary versus isolated location inside that boundary
pricing model vs support plan how you pay for resources versus what support service you receive
IaaS vs PaaS vs SaaS more customer management versus less
CAPEX vs OPEX up-front spend versus ongoing usage-based spend
Budgets vs Cost Explorer alerts and thresholds versus cost analysis and exploration
Artifact vs Audit Manager downloaded compliance evidence versus audit-workflow support

If three terms blur together

Cluster Fast separation
Region / Availability Zone / edge location geography boundary, isolated facility group, or edge presence
scalability / elasticity / high availability more capacity, faster capacity adjustment, or resilience through failure
pricing / billing / support how you pay, how you track the bill, or what help tier you have
IaaS / PaaS / SaaS more customer management, less customer management, or finished software
IAM / compliance / logging access control, standards/evidence, or activity visibility

One-sentence memory hooks

  • If the question is about who secures what, think shared responsibility model first.
  • If the question is about fast adjustment to demand, think elasticity before generic scalability.
  • If the question is about cost alerts, think AWS Budgets before broad pricing pages.
  • If the question is about compliance reports, think AWS Artifact.
  • If the question is about the least operational effort, prefer the more managed answer.

Operational clusters worth keeping straight

Cluster What it usually signals on the exam
cloud value / CAPEX / OPEX / TCO business-value and economics questions
Region / AZ / edge location infrastructure and resilience questions
IAM / shared responsibility / compliance evidence foundational security and governance questions
On-Demand / Reserved / Spot pricing model selection
Support plans / Trusted Advisor / Account Manager features support and business-fit questions

If the confusion is really about…

Topic family Best page to revisit
service-family recognition Cheat Sheet
exam-day format or study pacing FAQ or Study Plan
current AWS facts, policies, or official prep links Resources
broad exam framing Guide root
Revised on Sunday, May 10, 2026