CLF-C02 — AWS Certified Cloud Practitioner Quick Review

Quick Review for AWS Certified Cloud Practitioner (CLF-C02): high-yield AWS concepts, service selection, shared responsibility, pricing, security, and practice guidance.

Quick Review purpose

This Quick Review is for candidates preparing for the AWS Certified Cloud Practitioner (CLF-C02) exam from AWS. It is designed to help you refresh the most testable ideas before moving into IT Mastery practice, topic drills, mock exams, and detailed explanations.

The CLF-C02 exam is broad. It usually rewards recognition, comparison, and decision-making more than deep configuration skill. Focus on:

  • What a service is mainly used for.
  • Which service is managed by AWS versus managed by the customer.
  • Security and compliance responsibility boundaries.
  • Basic architectural tradeoffs: cost, availability, scalability, performance, and operations.
  • Pricing, billing, account management, and support concepts.
  • Common AWS terminology that appears in scenario-based questions.

This page is IT Mastery exam-prep support and is not affiliated with AWS.

High-yield exam mindset

What CLF-C02 tends to test

AreaWhat to know quicklyCommon candidate mistake
Cloud conceptsElasticity, scalability, high availability, pay-as-you-go, global reachTreating elasticity and scalability as identical
SecurityShared Responsibility Model, IAM, encryption, logging, monitoringAssuming AWS handles all security tasks
Core AWS servicesCompute, storage, databases, networking, analytics, migration, AI/ML at a recognition levelOver-studying console steps while missing service purpose
Pricing and billingPricing models, cost tools, account structures, support optionsConfusing Budgets, Cost Explorer, Pricing Calculator, and Trusted Advisor
ArchitectureWell-Architected thinking, managed services, fault tolerance, decouplingChoosing a complex service when a managed service is the exam-friendly answer

Practical review rule

If a question asks “Which AWS service should…”, first identify the workload category:

If the scenario says…Think first of…
Run virtual serversAmazon EC2
Run code without managing serversAWS Lambda
Store objects, backups, static assetsAmazon S3
Managed relational databaseAmazon RDS or Amazon Aurora
NoSQL key-value / document databaseAmazon DynamoDB
Content delivery / caching at edgeAmazon CloudFront
DNS / domain routingAmazon Route 53
Monitor metrics and alarmsAmazon CloudWatch
Audit API activityAWS CloudTrail
Evaluate resource configuration over timeAWS Config
Identity and access permissionsAWS IAM
Central multi-account governanceAWS Organizations
Encrypt and manage keysAWS Key Management Service, AWS KMS
Estimate future AWS costsAWS Pricing Calculator
Analyze past/current cost and usageAWS Cost Explorer
Set cost alerts and thresholdsAWS Budgets

Cloud concepts and AWS value proposition

Core cloud advantages

ConceptExam-ready meaning
Pay-as-you-goPay for resources consumed instead of large upfront capital purchases
Variable expenseCosts scale with usage rather than fixed data center commitments
Economies of scaleAWS operates at large scale, which can reduce unit costs
ElasticityAutomatically add or remove capacity as demand changes
ScalabilityIncrease or decrease capacity to meet workload needs
High availabilityDesign to remain accessible despite component failures
AgilityProvision resources quickly and experiment faster
Global reachDeploy closer to users using AWS global infrastructure

Elasticity vs scalability

TermQuick distinctionExample
ScalabilityAbility to handle increased or decreased loadIncrease database read capacity
ElasticityAutomatic scaling up and down with demandAuto Scaling adds instances during peak traffic and removes them later

A common trap is selecting scalability when the scenario emphasizes automatic response to changing demand. That is usually elasticity.

AWS global infrastructure

Key infrastructure terms

TermMeaningTypical exam angle
RegionA separate geographic area containing multiple Availability ZonesChoose for latency, compliance, data residency, service availability
Availability ZoneOne or more discrete data centers within a RegionDesign across multiple AZs for high availability
Edge locationSite used by services such as CloudFront to cache content near usersLower latency for global content delivery
Local ZonePlaces selected AWS services closer to large population or industry centersLow-latency local workloads
AWS OutpostsAWS infrastructure installed on premisesHybrid workloads that need local processing
AWS WavelengthAWS services at 5G network edge locationsUltra-low latency mobile/5G use cases

Region selection decision points

Choose a Region based on:

  1. Compliance or data residency requirements.
  2. Latency to users or systems.
  3. Service availability in that Region.
  4. Cost differences.
  5. Resilience strategy, such as multi-Region disaster recovery.

Do not assume every AWS service is available in every Region.

Shared Responsibility Model

The Shared Responsibility Model is one of the most important CLF-C02 concepts.

Responsibility split

AreaAWS responsibilityCustomer responsibility
Physical facilitiesData centers, power, cooling, physical securityNot responsible
Hardware and global infrastructureServers, storage hardware, networking hardwareNot responsible
Managed service infrastructureOperating and securing the underlying service platformConfigure and use the service securely
DataProvides secure services and controlsOwns data classification, protection choices, and access
IAMProvides IAM serviceCreate users, roles, policies, MFA, least privilege
Network configurationProvides networking capabilitiesConfigure VPCs, security groups, NACLs, routing
Guest operating system on EC2Provides infrastructurePatch and secure the OS unless using a managed service
ApplicationsProvides hosting servicesSecure application code and dependencies

Service model changes the customer responsibility

Service typeCustomer manages moreCustomer manages less
Amazon EC2Operating system, patches, application runtime, installed softwarePhysical infrastructure
Containers on customer-managed EC2Container host, cluster configuration, OS, runtimePhysical infrastructure
AWS FargateContainer image and app configurationServers and container host management
AWS LambdaFunction code, permissions, event sourcesServers, OS, runtime operations
Amazon S3Bucket policies, object permissions, data lifecycle choicesStorage infrastructure
Amazon RDSDatabase settings, access, schema, dataHardware, database engine patching options, backups features

Common shared responsibility traps

  • “AWS secures the cloud; the customer secures what they put in the cloud.”
  • AWS does not automatically classify your data for business sensitivity.
  • AWS does not automatically grant least-privilege IAM permissions.
  • AWS does not patch your EC2 guest operating system by default.
  • For managed services, AWS manages more infrastructure, but the customer still controls access, data, and configuration choices.

IAM and access control

IAM essentials

ConceptWhat it doesExam tip
IAM userLong-term identity for a person or applicationPrefer roles and federation where possible
IAM groupCollection of IAM usersPolicies can be attached to groups
IAM roleIdentity with temporary credentials that can be assumedCommon answer for AWS service access
IAM policyJSON permission documentGrants or denies actions on resources
Root userAccount owner identity with full accessSecure with MFA and avoid routine use
MFAAdditional authentication factorStrongly recommended for privileged identities
Least privilegeGrant only required permissionsFrequent best-practice answer

IAM role vs IAM user

ScenarioBetter answer
EC2 instance needs to access S3IAM role attached to the instance
Lambda function needs to write logsIAM execution role
External user needs temporary AWS accessIAM role / federation
Human administrator needs centralized sign-in across accountsAWS IAM Identity Center
Application uses long-term access keys in codeUsually a bad practice; prefer roles

Policy evaluation basics

For CLF-C02, remember:

  • Permissions are denied by default.
  • An explicit allow can grant access.
  • An explicit deny overrides an allow.
  • Use least privilege.
  • Avoid embedding long-term credentials in applications.

AWS Organizations and account governance

FeaturePurpose
AWS OrganizationsCentrally manage multiple AWS accounts
Organizational unit, OUGroup accounts for administration
Service control policy, SCPSet maximum available permissions for accounts or OUs
Consolidated billingCombine billing across accounts
AWS Control TowerHelps set up and govern a multi-account AWS environment

Important distinction: SCPs do not grant permissions by themselves. They define permission boundaries at the account or OU level. IAM policies are still needed to allow actions.

Security, compliance, and governance services

Security service recognition table

ServicePrimary purposeDo not confuse with…
AWS IAMIdentity and access managementIAM Identity Center for workforce federation
AWS IAM Identity CenterCentralized workforce access to multiple AWS accounts and appsIAM users
AWS KMSCreate and control encryption keysAWS Secrets Manager
AWS Secrets ManagerStore, retrieve, and rotate secretsParameter Store for simpler configuration values
AWS Certificate Manager, ACMProvision and manage SSL/TLS certificatesKMS keys
AWS CloudTrailRecord AWS API calls and account activityCloudWatch metrics/logs
Amazon CloudWatchMetrics, logs, alarms, dashboardsCloudTrail audit history
AWS ConfigTrack resource configuration and compliance over timeCloudTrail API event history
Amazon GuardDutyThreat detection using logs and intelligenceInspector vulnerability scanning
Amazon InspectorAutomated vulnerability management for workloadsGuardDuty threat detection
Amazon MacieDiscover and protect sensitive data in S3KMS encryption
AWS Security HubAggregates security findingsGuardDuty alone
AWS ShieldDDoS protectionAWS WAF web request filtering
AWS WAFWeb application firewall for HTTP/S requestsSecurity groups
AWS ArtifactAccess AWS compliance reports and agreementsAudit logging
Amazon DetectiveInvestigate security findingsGuardDuty detection
AWS Audit ManagerContinuously audit AWS usage against frameworksArtifact reports

CloudTrail vs CloudWatch vs Config

NeedBest match
“Who made this API call?”AWS CloudTrail
“What is CPU utilization?”Amazon CloudWatch
“Alert me when a metric crosses a threshold.”Amazon CloudWatch alarm
“Has this resource configuration changed?”AWS Config
“Is this resource compliant with a rule?”AWS Config
“Collect application logs.”Amazon CloudWatch Logs

This is one of the most common question-bank trap areas. Use topic drills until you can choose among these quickly.

Encryption basics

NeedService or feature
Manage encryption keysAWS KMS
Hardware security module controlAWS CloudHSM
Encrypt S3 objectsServer-side encryption options for S3, often using S3-managed or KMS-managed keys
Encrypt EBS volumesEBS encryption
Encrypt RDS databasesRDS encryption options
Manage TLS certificatesAWS Certificate Manager

Know the difference:

  • Encryption at rest protects stored data.
  • Encryption in transit protects data moving across networks, usually with TLS.
  • KMS manages cryptographic keys; it is not a general secret storage service.
  • Secrets Manager stores secrets such as database credentials and can support rotation.

Compute services

Compute comparison

ServiceUse when…Key exam clue
Amazon EC2You need virtual servers and control over OS/runtime“Virtual machine,” “install software,” “full control”
EC2 Auto ScalingAdd/remove EC2 instances based on demand“Adjust capacity automatically”
Elastic Load BalancingDistribute traffic across targets“Balance traffic,” “fault tolerance”
AWS LambdaRun code in response to events without managing servers“Serverless,” “event-driven,” “short-running function”
Amazon ECSRun containers using AWS container orchestration“Docker containers,” “managed orchestration”
Amazon EKSRun Kubernetes on AWS“Kubernetes”
AWS FargateRun containers without managing servers“Serverless containers”
AWS Elastic BeanstalkDeploy applications without manually managing infrastructure“Developer uploads code; AWS handles capacity/provisioning”
Amazon LightsailSimple VPS-style cloud hosting“Simple website or small app with predictable bundle”
AWS BatchBatch computing jobs“Batch processing”

EC2 purchasing options

OptionBest forCommon clue
On-Demand InstancesFlexible, short-term, unpredictable workloadsNo long-term commitment
Reserved InstancesSteady-state usage with commitmentPredictable EC2 needs
Savings PlansFlexible commitment-based savingsCommit to usage amount
Spot InstancesFault-tolerant workloads that can be interruptedLowest-cost spare capacity use cases
Dedicated HostsPhysical server dedicated to youLicensing or compliance tied to physical host
Dedicated InstancesInstances on hardware dedicated to one customerIsolation at hardware level, less license control than hosts

Trap: Spot Instances are attractive for cost, but not for workloads that cannot tolerate interruption.

Load balancers

Load balancerBest fit
Application Load Balancer, ALBHTTP/HTTPS, path-based or host-based routing
Network Load Balancer, NLBVery high performance TCP/UDP/TLS traffic
Gateway Load Balancer, GWLBDeploy and scale third-party virtual appliances

At CLF-C02 level, the most common distinction is ALB for web application routing and NLB for high-performance network traffic.

Storage services

Storage service selection

ServiceStorage typeBest for
Amazon S3Object storageObjects, backups, static websites, data lakes
Amazon EBSBlock storagePersistent volumes for EC2
EC2 instance storeTemporary block storageEphemeral data tied to instance lifecycle
Amazon EFSManaged file storageShared Linux file system across instances
Amazon FSxManaged file systemsWindows File Server, Lustre, NetApp ONTAP, OpenZFS use cases
AWS BackupCentralized backup managementBackup policies across AWS services
AWS Storage GatewayHybrid cloud storageConnect on-premises environments to AWS storage
AWS Snow FamilyPhysical devices for edge or data transferLarge-scale offline transfer or rugged edge processing

S3 essentials

ConceptMeaning
BucketContainer for S3 objects
ObjectFile plus metadata stored in S3
KeyObject name/path
VersioningKeep multiple versions of objects
Lifecycle policyMove or expire objects over time
ReplicationCopy objects to another bucket or Region based on rules
S3 Object LockHelps prevent object deletion or overwrite for retention use cases
Static website hostingHost static HTML/CSS/JS content from S3

S3 storage classes

Storage classBest for
S3 StandardFrequently accessed data
S3 Intelligent-TieringData with unknown or changing access patterns
S3 Standard-IAInfrequently accessed data that still needs rapid access
S3 One Zone-IAInfrequently accessed data stored in one AZ
S3 Glacier Instant RetrievalArchive data requiring immediate retrieval
S3 Glacier Flexible RetrievalArchive data with flexible retrieval needs
S3 Glacier Deep ArchiveLong-term archive data with lowest-cost archive use cases

Trap: S3 One Zone-IA stores data in one Availability Zone. It is not the default choice for critical multi-AZ resilience.

EBS vs EFS vs S3

NeedChoose
Boot volume or attached disk for EC2Amazon EBS
Shared file system for multiple Linux instancesAmazon EFS
Object storage accessible via API/HTTPAmazon S3
Temporary high-speed storage tied to EC2 hostInstance store
Windows shared file systemAmazon FSx for Windows File Server

Database services

Database selection table

ServiceTypeBest for
Amazon RDSManaged relational databaseTraditional SQL applications
Amazon AuroraAWS-optimized relational databaseHigh-performance MySQL/PostgreSQL-compatible workloads
Amazon DynamoDBManaged NoSQL key-value/document databaseServerless, low-latency, scalable apps
Amazon ElastiCacheIn-memory cacheRedis or Memcached caching
Amazon RedshiftData warehouseAnalytics on large structured datasets
Amazon NeptuneGraph databaseHighly connected data relationships
Amazon DocumentDBDocument databaseMongoDB-compatible document workloads
Amazon TimestreamTime-series databaseIoT, telemetry, time-based data
Amazon QLDBLedger databaseImmutable, verifiable transaction log use cases
Amazon KeyspacesWide-column databaseApache Cassandra-compatible workloads

RDS vs DynamoDB

Question clueLikely answer
SQL, joins, relational schema, existing commercial/open-source DB engineAmazon RDS
MySQL/PostgreSQL compatibility with AWS-optimized performanceAmazon Aurora
Key-value access, massive scale, serverless NoSQLAmazon DynamoDB
Microservice with unpredictable scale and simple access patternsDynamoDB often fits
Complex relational transactions and SQL reportingRDS or Aurora usually fits

Cache vs database

If the question asks for faster repeated reads or reduced database load, think Amazon ElastiCache. If it asks for durable primary data storage, choose a database or storage service instead.

Networking and content delivery

VPC basics

ComponentPurpose
Amazon VPCIsolated virtual network in AWS
SubnetSegment of a VPC within an Availability Zone
Public subnetHas route to internet gateway for internet-facing resources
Private subnetNo direct inbound internet route
Route tableControls where network traffic is directed
Internet gatewayAllows internet access for public resources
NAT gatewayAllows outbound internet access from private subnets
Security groupStateful virtual firewall for instances/resources
Network ACLStateless subnet-level traffic filter
VPC endpointPrivate access to supported AWS services without using public internet
VPC peeringPrivate connection between two VPCs
AWS Transit GatewayHub for connecting many VPCs and networks

Security group vs network ACL

FeatureSecurity groupNetwork ACL
LevelResource/instance levelSubnet level
StateStatefulStateless
RulesAllow rules onlyAllow and deny rules
Return trafficAutomatically allowed if request allowedMust be explicitly allowed
Common useInstance-level access controlBroad subnet traffic control

This is a high-frequency CLF-C02 trap. If the scenario says stateless or subnet-level, think network ACL.

Connectivity services

NeedService
Encrypted connection over the internet from on-premises to AWSAWS Site-to-Site VPN
Dedicated private network connection to AWSAWS Direct Connect
Connect many VPCs and on-premises networks centrallyAWS Transit Gateway
DNS and domain registration/routingAmazon Route 53
Global content cachingAmazon CloudFront
Improve global application availability/performance with static anycast IPsAWS Global Accelerator

Route 53 routing policy recognition

Routing needRoute 53 concept
Basic single destinationSimple routing
Route based on health checks / failoverFailover routing
Route based on user locationGeolocation routing
Route to lowest-latency RegionLatency-based routing
Split traffic by percentageWeighted routing

Architecture and the AWS Well-Architected Framework

Six Well-Architected pillars

PillarExam meaning
Operational excellenceRun and improve systems, automate operations, learn from events
SecurityProtect data, systems, and assets
ReliabilityRecover from failures and meet demand
Performance efficiencyUse resources efficiently as requirements change
Cost optimizationAvoid unnecessary cost and improve value
SustainabilityMinimize environmental impact of workloads

Architecture decision rules

Scenario asks for…Prefer…
Loosely coupled communicationAmazon SQS, Amazon SNS, Amazon EventBridge
Queue between application tiersAmazon SQS
Publish messages to multiple subscribersAmazon SNS
Event routing between services/appsAmazon EventBridge
Orchestrate multi-step workflowsAWS Step Functions
Scale web tier automaticallyEC2 Auto Scaling with Elastic Load Balancing
Reduce latency for static contentAmazon CloudFront
Avoid managing serversLambda, Fargate, managed services
Improve fault toleranceMulti-AZ design, load balancing, backups
Disaster recovery across geographic areasMulti-Region strategy

High availability vs fault tolerance vs disaster recovery

TermMeaning
High availabilitySystem remains accessible with minimal interruption
Fault toleranceSystem continues operating even when components fail
Disaster recoveryRestore service after a major outage or disaster
BackupCopy of data used for restore
Multi-AZResilience within a Region
Multi-RegionResilience across Regions; often more complex and costly

A question asking for resilience against an Availability Zone failure usually points to multi-AZ. A question asking for resilience against a Regional outage points to multi-Region.

Serverless and application integration

Serverless pattern recognition

RequirementCommon AWS service
Run event-driven codeAWS Lambda
Expose API endpointsAmazon API Gateway
Store objectsAmazon S3
NoSQL databaseAmazon DynamoDB
Queue messagesAmazon SQS
Fan-out notificationsAmazon SNS
Event bus / event routingAmazon EventBridge
Workflow orchestrationAWS Step Functions
User sign-up and authenticationAmazon Cognito

SQS vs SNS vs EventBridge

ServicePatternExample
Amazon SQSQueue; one consumer processes each messageDecouple web app from order processor
Amazon SNSPub/sub notification fan-outSend one event to email, Lambda, and SQS subscribers
Amazon EventBridgeEvent bus and routingRoute SaaS/app/AWS events to targets

Trap: SQS queues work items; SNS broadcasts notifications.

Monitoring, logging, and operations

Operational service recognition

ServiceMain use
Amazon CloudWatchMetrics, logs, alarms, dashboards
AWS CloudTrailGovernance, compliance, operational and risk auditing of API activity
AWS ConfigResource inventory, configuration history, compliance rules
AWS Systems ManagerOperational management for AWS resources and hybrid environments
AWS Health DashboardEvents affecting AWS services and your account
AWS Trusted AdvisorRecommendations for cost optimization, performance, security, fault tolerance, and service limits
AWS Service CatalogApproved portfolios of products for users to launch
AWS CloudFormationInfrastructure as code using templates
AWS Cloud Development Kit, AWS CDKDefine cloud infrastructure using programming languages
AWS OpsWorksConfiguration management using Chef/Puppet-style approaches

CloudFormation vs Elastic Beanstalk

NeedChoose
Provision infrastructure from templatesAWS CloudFormation
Deploy an app while AWS handles infrastructure provisioning detailsAWS Elastic Beanstalk
Define infrastructure using familiar programming languagesAWS CDK

Billing, pricing, and cost management

Pricing fundamentals

AWS pricing commonly varies by:

  • Compute usage and purchase model.
  • Storage amount, class, and retrieval.
  • Data transfer.
  • Requests and API calls.
  • Managed service features.
  • Region.
  • Support plan and optional services.

Do not assume the cheapest option is always correct. The exam often balances cost with availability, performance, or operational effort.

Cost tool selection

NeedBest match
Estimate cost before buildingAWS Pricing Calculator
View and analyze historical cost and usageAWS Cost Explorer
Set alerts for cost or usage thresholdsAWS Budgets
Detailed billing data for analysisAWS Cost and Usage Report
Receive optimization recommendationsAWS Trusted Advisor
Allocate costs by project/teamCost allocation tags
Central billing across accountsAWS Organizations consolidated billing

Common billing traps

  • Pricing Calculator estimates before deployment; it does not analyze your real past usage.
  • Cost Explorer analyzes actual cost and usage trends; it is not primarily an alerting tool.
  • AWS Budgets is for thresholds and notifications.
  • Trusted Advisor gives recommendations across categories, including cost optimization.
  • Consolidated billing helps manage multiple accounts centrally.
  • Tags help organize and allocate costs, but only if used consistently.

Support concepts

Know that AWS offers multiple support options with different levels of technical support, response expectations, and advisory features. For exam purposes, focus on the general idea:

NeedThink about
Basic documentation and whitepapersAWS documentation and self-service resources
Account and billing supportAvailable separately from deep technical support
Technical guidance and production workload supportPaid AWS Support plans
Architectural guidance and best practicesAWS Support resources, Trusted Advisor, Well-Architected guidance
Help from third-party software listingsAWS Marketplace seller or support path, depending on product

Avoid memorizing unofficial support-plan details from outdated sources. Use the current AWS exam guide and AWS support documentation for plan-specific features.

Migration, hybrid, and data transfer

Migration service recognition

ServiceUse
AWS Migration HubTrack migration progress across tools
AWS Application Migration ServiceLift-and-shift application migration
AWS Database Migration Service, AWS DMSMigrate databases to AWS
AWS Schema Conversion ToolHelp convert database schemas
AWS DataSyncOnline data transfer between storage systems and AWS
AWS Transfer FamilyManaged file transfer using protocols such as SFTP
AWS Snow FamilyPhysical devices for large data transfer or edge workloads
AWS Storage GatewayHybrid access to cloud-backed storage
AWS Direct ConnectDedicated network connection to AWS

Snow Family quick distinction

Device family conceptTypical use
SnowconeSmall rugged edge/data transfer device
Snowball EdgeLarger data transfer and edge compute
SnowmobileExtremely large-scale data migration concept

For CLF-C02, you usually only need to recognize that Snow Family helps when network transfer is impractical or when edge locations need rugged local processing.

Analytics, AI/ML, and developer services

Analytics services

ServiceMain purpose
Amazon AthenaQuery data in S3 using SQL
AWS GlueData integration, ETL, data catalog
Amazon EMRBig data processing frameworks
Amazon KinesisReal-time streaming data
Amazon OpenSearch ServiceSearch, log analytics, observability use cases
Amazon QuickSightBusiness intelligence dashboards
Amazon RedshiftData warehousing

AI/ML service recognition

ServiceMain purpose
Amazon SageMakerBuild, train, and deploy machine learning models
Amazon BedrockBuild generative AI applications using foundation models
Amazon ComprehendNatural language processing
Amazon RekognitionImage and video analysis
Amazon PollyText to speech
Amazon TranscribeSpeech to text
Amazon TranslateLanguage translation
Amazon LexConversational interfaces / chatbots
Amazon TextractExtract text and data from documents
Amazon KendraIntelligent enterprise search

For CLF-C02, these are usually recognition questions. Do not over-study model training unless your practice results show a weakness.

Developer and deployment services

ServicePurpose
AWS CodeCommitSource control repository service
AWS CodeBuildBuild and test code
AWS CodeDeployAutomate code deployments
AWS CodePipelineContinuous delivery pipeline
AWS Cloud9Cloud-based IDE
Amazon ECRContainer image registry

Fast service-selection workflow

Use this quick mental workflow when a scenario lists several AWS services:

    flowchart TD
	    A[Read the scenario outcome] --> B{What category is needed?}
	    B -->|Compute| C{Server control needed?}
	    C -->|Yes| C1[Amazon EC2]
	    C -->|No, code only| C2[AWS Lambda]
	    C -->|Containers| C3[ECS/EKS or Fargate]
	    B -->|Storage| D{Object, block, or file?}
	    D -->|Object| D1[Amazon S3]
	    D -->|Block for EC2| D2[Amazon EBS]
	    D -->|Shared file| D3[Amazon EFS or FSx]
	    B -->|Database| E{Relational?}
	    E -->|Yes| E1[RDS or Aurora]
	    E -->|NoSQL key-value| E2[DynamoDB]
	    E -->|Warehouse| E3[Redshift]
	    B -->|Security or audit| F{Need logs, config, or identity?}
	    F -->|API activity| F1[CloudTrail]
	    F -->|Metrics and alarms| F2[CloudWatch]
	    F -->|Resource compliance| F3[Config]
	    F -->|Permissions| F4[IAM]

Common CLF-C02 traps to practice

Trap list

  1. CloudTrail vs CloudWatch

    • CloudTrail: API activity and audit.
    • CloudWatch: metrics, logs, alarms.
  2. Security group vs network ACL

    • Security group: stateful, resource level.
    • Network ACL: stateless, subnet level.
  3. IAM role vs access key

    • Roles with temporary credentials are usually preferred for AWS service access.
  4. S3 vs EBS vs EFS

    • S3: object storage.
    • EBS: block volume for EC2.
    • EFS: shared file storage.
  5. RDS vs DynamoDB

    • RDS/Aurora: relational SQL.
    • DynamoDB: managed NoSQL key-value/document.
  6. Pricing Calculator vs Cost Explorer vs Budgets

    • Calculator: estimate.
    • Cost Explorer: analyze actual costs.
    • Budgets: alert on thresholds.
  7. Multi-AZ vs multi-Region

    • Multi-AZ: resilience inside a Region.
    • Multi-Region: geographic disaster recovery or global strategy.
  8. AWS responsibility vs customer responsibility

    • AWS manages infrastructure.
    • Customer manages data, identity, access, and configuration choices.
  9. SNS vs SQS

    • SNS broadcasts.
    • SQS queues.
  10. Managed service does not mean no customer responsibility

  • You still configure access, encryption choices, networking, and data handling.

Quick review checklist

Before starting mock exams, make sure you can answer these without notes:

Cloud and architecture

  • Explain elasticity, scalability, high availability, and fault tolerance.
  • Identify why a company might choose cloud over on-premises infrastructure.
  • Choose between Region, Availability Zone, edge location, Local Zone, Wavelength, and Outposts.
  • Recognize the six AWS Well-Architected pillars.
  • Distinguish multi-AZ from multi-Region.

Security

  • Apply the Shared Responsibility Model to EC2, RDS, S3, and Lambda.
  • Choose IAM roles instead of long-term credentials for AWS service access.
  • Explain least privilege, MFA, root user protection, and policy basics.
  • Choose between CloudTrail, CloudWatch, and Config.
  • Recognize GuardDuty, Inspector, Macie, Shield, WAF, KMS, Secrets Manager, ACM, and Artifact.

Technology and services

  • Choose EC2, Lambda, ECS/EKS, Fargate, Elastic Beanstalk, or Lightsail from scenario clues.
  • Choose S3, EBS, EFS, FSx, Storage Gateway, Backup, or Snow Family.
  • Choose RDS, Aurora, DynamoDB, Redshift, ElastiCache, Neptune, or DocumentDB.
  • Identify VPC components and security group vs network ACL differences.
  • Recognize Route 53, CloudFront, Direct Connect, VPN, Transit Gateway, and Global Accelerator.
  • Recognize SQS, SNS, EventBridge, Step Functions, and API Gateway.

Billing and support

  • Choose Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Report, or Trusted Advisor.
  • Explain consolidated billing and AWS Organizations at a high level.
  • Understand cost allocation tags.
  • Recognize common pricing factors: compute, storage, requests, data transfer, Region, and support.
  • Know that support options vary and should be checked against current AWS documentation.

How to use question-bank practice after this review

A good practice sequence for AWS Certified Cloud Practitioner (CLF-C02) is:

  1. Start with topic drills

    • Drill IAM, shared responsibility, S3/EBS/EFS, EC2/Lambda, CloudTrail/CloudWatch/Config, and billing tools separately.
  2. Read detailed explanations

    • Do not only mark right/wrong. For every missed question, identify the service clue that should have led to the answer.
  3. Build a confusion list

    • Keep a short list of pairs you confuse, such as SNS/SQS, RDS/DynamoDB, or Cost Explorer/Budgets.
  4. Move to mixed question-bank sets

    • Mixed original practice questions help you practice recognition under realistic conditions.
  5. Use mock exams last

    • Mock exams are best for timing, endurance, and identifying remaining weak areas.
  6. Review missed questions by decision rule

    • Convert every miss into a rule: “If the question says API audit, choose CloudTrail,” or “If the question says stateless subnet firewall, choose network ACL.”

Final rapid reminders

  • Prefer managed services when the scenario values reduced operational burden.
  • Prefer IAM roles over embedded long-term credentials.
  • Prefer Multi-AZ for Availability Zone resilience.
  • Prefer CloudFront for global content delivery.
  • Prefer S3 for object storage and static assets.
  • Prefer RDS/Aurora for relational databases.
  • Prefer DynamoDB for serverless NoSQL key-value/document workloads.
  • Prefer CloudTrail for audit trails.
  • Prefer CloudWatch for metrics, logs, alarms, and dashboards.
  • Prefer AWS Budgets for alerts and Cost Explorer for cost analysis.
  • Always check whether the question asks for security, cost, availability, performance, or operational simplicity.

Your next practical step: use this Quick Review as a checklist, then work through CLF-C02 topic drills and original practice questions with detailed explanations until the service-selection traps feel automatic.

Continue in IT Mastery

Use this Quick Review as a final concept map, then move into IT Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original IT Mastery practice items; they are not official AWS questions, copied live-exam content, or exam dumps.

Browse Certification Practice Tests by Exam Family