AWS Certified Cloud Practitioner (CLF-C02) Ultimate Cheat Sheet
Your Quick Reference Study Guide
This cheat sheet covers the core concepts, terms, and definitions you need to know for the AWS Certified Cloud Practitioner (CLF-C02). We've distilled the most important domains, topics, and critical details to help your exam preparation.
💡 Note: While this study guide highlights essential concepts, it's designed to complement—not replace—comprehensiv e learning materials. Use it for quick reviews, last-minute prep, or to identify areas that need deeper study before your exam.
About This Cheat Sheet: This study guide covers core concepts for AWS Certified Cloud Practitioner (CLF-C02). It highlights key terms, definitions, common mistakes, and frequently confused topics to support your exam preparation.
Use this as a quick reference alongside comprehensive study materials.
AWS Certified Cloud Practitioner (CLF-C02)
Cheat Sheet •
About This Cheat Sheet: This study guide covers core concepts for AWS Certified Cloud Practitioner (CLF-C02). It highlights key terms, definitions, common mistakes, and frequently confused topics to support your exam preparation.
Use this as a quick reference alongside comprehensive study materials.
Cloud Concepts
24%AWS Value Proposition
Why orgs pick AWS: pay‑as‑you‑go, economies of scale, global infra, elasticity, and managed services.
Key Insight
AWS can cut costs and speed delivery for variable workloads — but savings require right‑sizing, monitoring, and following the Shared Responsibility or
Often Confused With
Common Mistakes
- Assuming AWS is always cheaper than on‑premises.
- Believing elasticity/auto‑scaling alone guarantees optimal cost or performance.
- Thinking managed services remove customer responsibility for security/compliance/cost tuning.
Cloud Fundamentals: Models, Ops, Provisioning
Core cloud basics: public/private/hybrid models, elasticity/scalability/HA, and provisioning options (on‑demand,Reserved
Key Insight
Elasticity (automatic resize for demand spikes) ≠ scalability (architectural ability to grow); AZs give zone‑level HA, Regions add disaster and legal/
Often Confused With
Common Mistakes
- Treating elasticity and scalability as identical.
- Assuming high availability means no backups or DR planning required.
- Believing a different AZ equals the same protection as a different Region.
AWS Cost & Billing — Rightsize, Tag, Monitor
Pricing models and tools to estimate, allocate, and reduce AWS spend while preserving performance.
Key Insight
Start with visibility: enable Cost Explorer, consolidated billing, budgets, and consistent tags before optimizing.
Often Confused With
Common Mistakes
- Assuming consolidated billing automatically reduces costs for every account.
- Picking the cheapest resource without accounting for performance or availability trade-offs.
- Relying on tags without a standardized strategy and activation in the Billing console.
AWS Security — Least Privilege & Continuous Defense
Layered controls (IAM, encryption, logging, monitoring) applied continuously under the shared‑responsibility model.
Key Insight
Combine IAM least‑privilege + MFA, KMS key management, CloudTrail/Config logging and active monitoring — one control isn't enough.
Often Confused With
Common Mistakes
- Assuming encrypting data at rest protects data in transit.
- Treating security as a one‑time setup instead of continuous monitoring and auditing.
- Believing security groups apply at the subnet level (they attach to ENIs/instances).
AWS CAF (Cloud Adoption Framework)
Prescriptive guidance across people, processes, and technology to plan cloud adoption and assign responsibilities.
Key Insight
CAF is guidance, not a migration tool — use its perspectives to surface gaps in people, process, and tech.
Often Confused With
Common Mistakes
- Treating CAF as an automated migration tool you run.
- Skipping people/process perspectives and focusing only on architecture.
- Assuming CAF alone produces a complete migration plan without tooling/timelines.
AWS DMS (Database Migration Service)
Service to migrate and replicate databases with minimal downtime using full load plus CDC via a replication instance and
Key Insight
DMS moves data live with CDC to minimize downtime but doesn't auto-convert schemas or stored procedures; use AWS SCT for that.
Often Confused With
Common Mistakes
- Expecting automatic schema and stored-procedure conversion during heterogeneous migrations.
- Assuming DMS always causes major downtime—CDC can keep the source online.
- Believing DMS migrates all DB objects (triggers/procs) by default.
TCO — Total Cost of Ownership (True Cost Check)
Compares all direct and indirect on‑prem vs AWS costs to judge migration ROI and payback.
Key Insight
Include CapEx, OpEx, staffing, licensing, facilities, and migration costs — cloud isn't automatically cheaper.
Often Confused With
Common Mistakes
- Counting only obvious bills (compute/storage) and ignoring staff, licenses, facilities
- Assuming cloud always saves money — steady, high‑utilization workloads may cost more
- Omitting one‑time migration or re‑architecture costs from the comparison
Pay‑as‑You‑Go Pricing (Consumption Billing)
Pay only for resources you use — enables elasticity, but costs can spike without governance or discounts.
Key Insight
Great for spiky/variable demand; for steady loads use Reserved/Committed pricing to lower cost.
Often Confused With
Common Mistakes
- Believing pay‑as‑you‑go is always the cheapest option
- Thinking it removes the need for cost monitoring or governance
- Ignoring available long‑term discounts or commitment plans for predictable workloads
AWS Value Proposition
Why orgs pick AWS: pay‑as‑you‑go, economies of scale, global infra, elasticity, and managed services.
Key Insight
AWS can cut costs and speed delivery for variable workloads — but savings require right‑sizing, monitoring, and following the Shared Responsibility or
Often Confused With
Common Mistakes
- Assuming AWS is always cheaper than on‑premises.
- Believing elasticity/auto‑scaling alone guarantees optimal cost or performance.
- Thinking managed services remove customer responsibility for security/compliance/cost tuning.
Cloud Fundamentals: Models, Ops, Provisioning
Core cloud basics: public/private/hybrid models, elasticity/scalability/HA, and provisioning options (on‑demand,Reserved
Key Insight
Elasticity (automatic resize for demand spikes) ≠ scalability (architectural ability to grow); AZs give zone‑level HA, Regions add disaster and legal/
Often Confused With
Common Mistakes
- Treating elasticity and scalability as identical.
- Assuming high availability means no backups or DR planning required.
- Believing a different AZ equals the same protection as a different Region.
AWS Cost & Billing — Rightsize, Tag, Monitor
Pricing models and tools to estimate, allocate, and reduce AWS spend while preserving performance.
Key Insight
Start with visibility: enable Cost Explorer, consolidated billing, budgets, and consistent tags before optimizing.
Often Confused With
Common Mistakes
- Assuming consolidated billing automatically reduces costs for every account.
- Picking the cheapest resource without accounting for performance or availability trade-offs.
- Relying on tags without a standardized strategy and activation in the Billing console.
AWS Security — Least Privilege & Continuous Defense
Layered controls (IAM, encryption, logging, monitoring) applied continuously under the shared‑responsibility model.
Key Insight
Combine IAM least‑privilege + MFA, KMS key management, CloudTrail/Config logging and active monitoring — one control isn't enough.
Often Confused With
Common Mistakes
- Assuming encrypting data at rest protects data in transit.
- Treating security as a one‑time setup instead of continuous monitoring and auditing.
- Believing security groups apply at the subnet level (they attach to ENIs/instances).
AWS CAF (Cloud Adoption Framework)
Prescriptive guidance across people, processes, and technology to plan cloud adoption and assign responsibilities.
Key Insight
CAF is guidance, not a migration tool — use its perspectives to surface gaps in people, process, and tech.
Often Confused With
Common Mistakes
- Treating CAF as an automated migration tool you run.
- Skipping people/process perspectives and focusing only on architecture.
- Assuming CAF alone produces a complete migration plan without tooling/timelines.
AWS DMS (Database Migration Service)
Service to migrate and replicate databases with minimal downtime using full load plus CDC via a replication instance and
Key Insight
DMS moves data live with CDC to minimize downtime but doesn't auto-convert schemas or stored procedures; use AWS SCT for that.
Often Confused With
Common Mistakes
- Expecting automatic schema and stored-procedure conversion during heterogeneous migrations.
- Assuming DMS always causes major downtime—CDC can keep the source online.
- Believing DMS migrates all DB objects (triggers/procs) by default.
TCO — Total Cost of Ownership (True Cost Check)
Compares all direct and indirect on‑prem vs AWS costs to judge migration ROI and payback.
Key Insight
Include CapEx, OpEx, staffing, licensing, facilities, and migration costs — cloud isn't automatically cheaper.
Often Confused With
Common Mistakes
- Counting only obvious bills (compute/storage) and ignoring staff, licenses, facilities
- Assuming cloud always saves money — steady, high‑utilization workloads may cost more
- Omitting one‑time migration or re‑architecture costs from the comparison
Pay‑as‑You‑Go Pricing (Consumption Billing)
Pay only for resources you use — enables elasticity, but costs can spike without governance or discounts.
Key Insight
Great for spiky/variable demand; for steady loads use Reserved/Committed pricing to lower cost.
Often Confused With
Common Mistakes
- Believing pay‑as‑you‑go is always the cheapest option
- Thinking it removes the need for cost monitoring or governance
- Ignoring available long‑term discounts or commitment plans for predictable workloads
Security and Compliance
30%Shared Responsibility Model (Security Of vs In the Cloud)
Split of security tasks: AWS protects the cloud infrastructure; you protect your data, configs, and accounts; varies by
Key Insight
Responsibility shifts by service model — IaaS (EC2) = you secure OS/apps; PaaS/SaaS (RDS/Lambda) = AWS covers more infra.
Often Confused With
Common Mistakes
- Thinking AWS is responsible for all security for every service
- Assuming AWS certifications automatically make your workload compliant
- Believing managed or serverless services remove customer duties for IAM, data, or configs
AWS KMS (Key Management Service)
Managed service to create, store, and use cryptographic keys; integrates with AWS encryption (SSE) and client-side data‑
Key Insight
KMS manages key lifecycle and cryptographic operations — it protects keys (not plaintext) and CMK key material cannot be exported.
Often Confused With
Common Mistakes
- Believing CMKs or key material can be exported from AWS
- Assuming KMS automatically encrypts every resource by default
- Thinking KMS stores or sees your plaintext application data
AWS Compliance & Governance (Artifact + Shared Model)
Find AWS compliance evidence and apply the shared‑responsibility model across regions and industries.
Key Insight
Service certifications don't automatically cover your workload — map customer controls, region choice, and Artifact evidence.
Often Confused With
Common Mistakes
- Assuming a certified AWS service makes your workload compliant.
- Treating certifications and service availability as identical across regions.
- Thinking encryption or managed services alone remove your logging/controls responsibilities.
CloudTrail — API Audit Trail
Records AWS API calls and account activity for auditing and troubleshooting; not an alert/response engine by itself.
Key Insight
CloudTrail captures control‑plane events by default; data events, real‑time alerts, and retention require extra config (S3, CloudWatch/EventBridge).
Often Confused With
Common Mistakes
- Expecting built‑in real‑time alerts or automated responses without integrations.
- Assuming CloudTrail logs all data‑plane events by default.
- Believing logs persist indefinitely without configuring S3/lifecycle or retention settings.
IAM — Identities, Policies & Roles
Global AWS service that manages users, groups, roles, credentials, and JSON policies for access control.
Key Insight
IAM is global; explicit DENY always wins; use roles for temporary creds and keep root locked away.
Often Confused With
Common Mistakes
- Treating IAM as regional (it's global).
- Using the root account for daily admin instead of protected IAM identities.
- Interchanging users and roles as if they’re the same thing.
Least Privilege — Lock Down Access
Grant only the permissions needed — use fine-grained policies, roles, temporary creds, and permission boundaries.
Key Insight
Start restrictive (read-only or none) and add explicit actions; prefer roles/temporary creds over long-lived keys.
Often Confused With
Common Mistakes
- Treating strong authentication (MFA/passwords) as a substitute for restricting permissions.
- Applying least privilege only to human users, not to roles or service principals.
- Granting broad admin or long-lived credentials for convenience.
GuardDuty — Managed Threat Detection
Managed detector that analyzes CloudTrail, VPC Flow Logs, and DNS for prioritized security findings.
Key Insight
Detection-only: it surfaces prioritized findings — it doesn't block or auto-fix incidents.
Often Confused With
Common Mistakes
- Treating GuardDuty like a firewall that blocks traffic (it only detects and alerts).
- Expecting per-EC2 agents — GuardDuty uses AWS-native logs/telemetry, not instance agents.
- Assuming it auto-remediates or replaces a SIEM; it outputs findings for tooling/automation.
AWS WAF — Web Application Firewall
Layer‑7 firewall for HTTP(S) to block injections, bots, and OWASP risks; attach to CloudFront, ALB, API Gateway.
Key Insight
App-layer protection only — WAF filters requests but does not provide network-level DDoS mitigation.
Often Confused With
Common Mistakes
- Relying on WAF alone for DDoS protection instead of using Shield/Shield Advanced.
- Assuming WAF blocks all OWASP attacks by default—rules must be configured.
- Thinking WAF replaces security groups or NACLs; those protect lower network layers.
Cloud Technology and Services
34%IaC — Infrastructure as Code
Define infrastructure in code/config so environments are provisioned repeatably, versioned, and testable.
Key Insight
IaC (declarative or imperative) makes provisioning repeatable and auditable — it automates setup but doesn't remove ops or security responsibility.
Often Confused With
Common Mistakes
- Thinking IaC must be declarative — scripts and SDK-driven flows are still IaC.
- Equating IaC with config management — IaC provisions resources; config tools configure software inside them.
- Assuming IaC guarantees security/compliance — templates need reviews, policies, and guarding controls.
AWS CloudFormation — Declarative IaC
AWS service using YAML/JSON templates to declare, create, update, and manage stacks of AWS resources.
Key Insight
CloudFormation declares desired resource state; use change sets and drift detection to preview differences — it won't auto-repair drift or install OS‑
Often Confused With
Common Mistakes
- Treating CloudFormation as a config-management tool that installs software inside instances.
- Believing templates must be JSON — YAML is fully supported.
- Assuming drift detection auto-corrects resources — it only reports differences; manual action required.
AWS Global Infrastructure — Regions & AZs (Availability Zones)
AWS physical footprint — Regions, AZs, Local Zones, edge sites; choose placement to meet latency, availability, and data
Key Insight
Region = jurisdiction/data residency; AZ = independent fault domain for HA; Local/edge reduce latency but don't replace AZ resilience.
Often Confused With
Common Mistakes
- Assuming Local Zones or edge locations give AZ-level resiliency
- Believing the closest Region eliminates all latency — routing and app design matter
- Thinking AZ labels (e.g., us-east-1a) map to the same physical AZ across accounts
Availability Zones (AZs) — Isolated Fault Domains
Isolated data‑center groupings inside an AWS Region with independent power/networking; use multi‑AZ for high uptime.
Key Insight
AZs are separate data centers inside one Region — distribute resources across AZs to survive single data‑center failures.
Often Confused With
Common Mistakes
- Treating an AZ as a full Region — it's a Region's fault domain, not a Region
- Assuming an AZ is a single server or rack
- Relying on multi‑AZ alone for cross‑Region disaster recovery or data residency needs
Auto Scaling (ASG & Launch Templates)
Automatically adjusts EC2 capacity via Auto Scaling Groups and policies to meet demand and control cost.
Key Insight
Scales both out and in using metric- or schedule-based policies — policy choice trades availability vs. cost.
Often Confused With
Common Mistakes
- Assuming Auto Scaling guarantees zero downtime during scaling or instance replacement.
- Expecting Auto Scaling to automatically scale managed services (like RDS) without extra configuration.
- Believing Auto Scaling removes the need for a load balancer to distribute traffic.
Elastic Load Balancing (ALB, NLB, GWLB, CLB)
Distributes incoming traffic across targets; pick ALB for HTTP/S, NLB for TCP/high throughput, GWLB for appliance chains
Key Insight
Match by OSI layer and feature: ALB = L7 host/path routing, NLB = L4 high-performance + preserves client IP, GWLB = steer to appliances.
Often Confused With
Common Mistakes
- Using ALB for arbitrary TCP services — ALB is for HTTP/S (layer 7) routing.
- Thinking NLB cannot preserve client source IPs — NLB can preserve source IP.
- Treating GWLB as a general L7 web router instead of appliance traffic steering.
RDS — Managed Relational DB
Managed relational DB (MySQL/Postgres/Oracle/etc.): AWS runs infra; you manage data, access, and DB config.
Key Insight
AWS handles infra/patches/backups; you retain control of data, users, network, encryption, and scaling choices.
Often Confused With
Common Mistakes
- Believing RDS removes your data and access responsibilities — you still manage users, network, and schema.
- Expecting full DB superuser/root access — some privileged operations are restricted in managed RDS.
- Assuming compute auto-scales — storage can auto-scale; compute requires instance changes or serverless options.
DynamoDB — Serverless NoSQL
Fully managed key-value/document DB with single-digit ms latency; requires partition-key design and capacity planning.
Key Insight
Partition key + capacity mode (on‑demand vs provisioned) drive performance/cost; default reads are eventual and items max ~400 KB.
Often Confused With
Common Mistakes
- Treating DynamoDB like an RDBMS — no joins or fixed schemas; use keys and secondary indexes.
- Assuming no capacity or key planning — partition keys and capacity mode affect latency and cost.
- Assuming strong reads by default — eventual consistency is the default unless you request strong reads.
VPC (Virtual Private Cloud) & Network Primitives
Regional virtual networks (VPCs) — subnets, route tables, IGW/NAT, security groups, and NACLs for connectivity and sec.
Key Insight
VPC is regional; subnets are AZ-scoped. IGW gives public internet; NAT provides outbound for private subnets. SGs are stateful; NACLs are stateless.
Often Confused With
Common Mistakes
- Assuming a VPC automatically spans all AWS Regions
- Using an Internet Gateway expecting NAT for private subnets
- Treating security groups as stateless like NACLs
AWS Direct Connect — Dedicated Private Link
Dedicated private connection from on‑prem to AWS that reduces internet variability but still needs routing and HA design
Key Insight
Direct Connect bypasses the public Internet but does NOT encrypt traffic by default; you still configure BGP/VLANs, VPC routing, security, and add red
Often Confused With
Common Mistakes
- Assuming Direct Connect encrypts traffic end-to-end by default
- Believing Direct Connect always yields lower latency for every route
- Relying on a single Direct Connect connection for high availability
S3 — Object Storage & Storage Classes
Scalable object storage; choose storage class by access frequency, cost, and retrieval speed.
Key Insight
Objects-only: you must PUT/replace whole objects; storage classes trade lower cost for lower availability/longer retrieval.
Often Confused With
Common Mistakes
- Treating S3 like a mountable block device — you must read/write whole objects.
- Mixing storage classes with encryption/ACLs — classes only affect cost/availability.
- Ignoring lifecycle timing and fees — transitions take time and may incur early-delete charges.
EBS — EC2 Block Storage (AZ-scoped)
Persistent, network-attached block volumes for EC2 — pick by IOPS, throughput, or cost; tied to an AZ.
Key Insight
AZ-scoped block volumes attach to EC2 (single-instance by default); snapshots are incremental and stored outside the AZ (in S3).
Often Confused With
Common Mistakes
- Assuming EBS replicates across AZs — volumes live in one AZ only.
- Believing any volume can attach to many instances — multi-attach is limited to specific types.
- Thinking snapshots are lost with AZ failure — snapshots persist (stored in S3) and can recreate volumes.
AWS Analytics Stack
Managed services to ingest, process, query, and visualize data—pick the right tool per pipeline stage.
Key Insight
Map services to stages: S3=storage, Kinesis=ingest/streaming, Glue=ETL/catalog, Athena/Redshift=query, EMR=clustered processing.
Often Confused With
Common Mistakes
- Treating S3 as an analytics service instead of object storage used by analytics tools.
- Calling Athena a data warehouse — it's a serverless query engine that queries data in place.
- Assuming all analytics services are serverless (EMR uses managed clusters).
SageMaker — Build, Train, Deploy
Managed end-to-end ML: notebooks, scalable training, hyperparameter tuning, and hosted inference.
Key Insight
SageMaker covers data prep, training, tuning, and hosting — each feature consumes compute/storage and incurs cost.
Often Confused With
Common Mistakes
- Thinking SageMaker only deploys models — it also provides training, tuning, and notebooks.
- Believing it only supports deep learning; it also runs traditional ML algorithms.
- Assuming Autopilot or managed features remove need for data prep or cost planning (not free).
Amazon SNS — Pub/Sub Push & Fan‑Out
Managed pub/sub push service that fans out notifications to endpoints (SQS, Lambda, HTTP, SMS, email).
Key Insight
Push-based fan‑out to subscribers; use SQS subscriptions for durability and don't expect ordered or exactly‑once delivery.
Often Confused With
Common Mistakes
- Treating SNS like a durable queue — it doesn't persist messages long‑term.
- Expecting ordered, exactly‑once delivery — SNS is best‑effort and may duplicate.
- Using SNS for bulk email deliverability — use SES for sending email at scale.
Service Selection — Map Requirements to AWS Services
Match the primary constraint (scale, cost, ops, latency) to a service category, then pick the specific managed service.
Key Insight
Choose by dominant constraint: control→EC2, containers→ECS/EKS, serverless→Lambda, relational→RDS, NoSQL→DynamoDB.
Often Confused With
Common Mistakes
- Choosing services by familiarity or brand, not by the actual requirements and tradeoffs.
- Assuming 'managed' removes all operational work or cost responsibility—still check limits/pricing.
- Treating a category (e.g., 'database') as a single interchangeable service.
Billing, Pricing, and Support
12%Compute Purchase Modes (On‑Demand, RI, Spot, Savings)
Compare cost, flexibility, commitment, and interruption risk across EC2 purchasing options to match workload needs.
Key Insight
Lower price = more commitment or interruption risk; choose by workload predictability, fault tolerance, and licensing needs.
Often Confused With
Common Mistakes
- Assuming Reserved Instances always save more than Savings Plans
- Treating Spot as only for short jobs—usable for long workloads if designed for interruptions
- Mixing Capacity Reservations (guarantee capacity) with Reserved Instances (billing/discount commitment)
Savings Plans — Compute vs EC2 Instance
Commit to $/hour for 1–3 years to get discounts across EC2, Lambda, and Fargate; Savings Plans do not reserve capacity.
Key Insight
Savings Plans are billing discounts, not capacity reservations — use Compute for cross‑service flexibility, Instance for family/region savings.
Often Confused With
Common Mistakes
- Believing Savings Plans reserve capacity — they only apply discounted pricing
- Assuming Compute Savings Plans cover only EC2; they also apply to Lambda and Fargate
- Confusing EC2 Instance Savings Plans (narrower scope) with Compute Savings Plans (broader, cross‑service)
AWS Organizations — Consolidated Billing & Policies
Centralized account grouping: aggregated billing, pooled discounts, and organization-level policies.
Key Insight
Billing and discounts are aggregated to the management account — Organizations does NOT grant resource access.
Often Confused With
Common Mistakes
- Thinking the management account can access member accounts' resources
- Believing Organizations adds an extra fee for consolidated billing
- Assuming RIs/Savings Plans are never pooled across accounts
AWS Budgets — Alerts, Forecasts & Actions
Set cost/usage/RI/coverage thresholds to send alerts or trigger actions; pairs with Cost Explorer for analysis.
Key Insight
Budgets alerts and can invoke actions, but data updates daily — it won't auto-shutdown resources or give real‑time costs.
Often Confused With
Common Mistakes
- Expecting Budgets to automatically stop or delete resources
- Assuming Budgets provides real-time cost data
- Treating Budgets as a replacement for Cost Explorer
Trusted Advisor (TA) Checks
Automated best-practice checks for cost, security, fault tolerance, performance, and service limits; returns remediation
Key Insight
TA only recommends fixes (no auto-remediation); full-depth checks and extra checks require paid support and run periodically.
Often Confused With
Common Mistakes
- Expecting Trusted Advisor to automatically fix issues (it only recommends actions).
- Assuming it checks every service/region equally—coverage and depth vary.
- Believing all checks are available on the Basic (free) plan.
AWS Support Plans (Basic, Dev, Business, Enterprise)
Tiered support (Basic free → Developer → Business → Enterprise/On‑Ramp) with different SLAs, features, and TA access.
Key Insight
Higher tiers add faster response SLAs, full Trusted Advisor checks, and a designated TAM only on Enterprise; Basic is billing/docs only.
Often Confused With
Common Mistakes
- Thinking Basic gives 24x7 technical/troubleshooting support (it doesn't).
- Assuming every paid plan has the same SLAs or includes a TAM—only Enterprise has a TAM and fastest targets.
- Treating Developer support as suitable for mission‑critical production systems (it has longer response windows).
Certification Overview
Cheat Sheet Content
Similar Cheat Sheets
- CCNA Exam v1.1 (200-301) Cheat Sheet
- AWS Certified AI Practitioner (AIF-C01) Cheat Sheet
- Exam AI-900: Microsoft Azure AI Fundamentals Cheat Sheet
- Google Cloud Professional Cloud Architect Cheat Sheet
- Google Cloud Security Operations Engineer Exam Cheat Sheet
- Google Cloud Professional Cloud Security Engineer Cheat Sheet