# AWS Certified Cloud Practitioner (CLF-C02) Free Practice Exam - CCP Practice Test

CLF-C02 · FOUNDATIONAL. Page: https://blowstack.com/practice-exams/aws-certified-cloud-practitioner

> Master your AWS Certified Cloud Practitioner exam with our Practice Exam Simulator. Prepare effectively and assess your readiness with realistic practice exams designed to mirror the most popular official AWS exam.

Exam version CLF-C02: current, release Sep 19, 2023. All exam dates: https://blowstack.com/tools/cloud-certifications/aws

## Exam at a glance

- Question bank: 937 practice questions
- Questions updated: 2026-10-30
- Free CLF-C02 practice exam (20 questions weighted by domain, in the exam simulator on this page, no sign-up): https://blowstack.com/practice-exams/aws-certified-cloud-practitioner
- CLF-C02 exam simulator (full-length or custom exams with explanations and a pass probability indicator): https://app.blowstack.com/practice-exams/configurator/aws-certified-cloud-practitioner
- Questions: 65
- Duration: 90 min
- Passing score: 70%
- Domains: 4
- Interactive CLF-C02 course (353 lessons built around exercises, no videos): https://blowstack.com/courses/aws-certified-cloud-practitioner
- Official CLF-C02 exam guide (the AWS document listing every domain, task and service in scope): https://docs.aws.amazon.com/aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02.html

## CLF-C02 example questions

One example question per domain from the CLF-C02 question bank, with the correct answer and its explanation.

### Cloud Concepts

**Question:**

A training company hosts downloadable course videos on an Amazon EC2 instance in one AWS Region. Learners worldwide repeatedly download the same videos. The company wants to improve download performance for distant learners and reduce requests to the instance without managing additional video servers. Which solution best meets these requirements?

**Correct answer:** Configure an Amazon CloudFront distribution with the existing EC2 instance as its origin.

**Explanation:** CloudFront caches eligible content at edge locations worldwide. Serving cached videos closer to learners improves download performance and reduces requests to the origin, without requiring the company to manage additional video servers.

### Security and Compliance

**Question:**

A company is moving several business units to AWS. Each unit needs separate AWS accounts, but a central team must maintain consistent governance. The company wants a standardized multi-account environment with centralized audit logging, preconfigured governance controls, and a repeatable process for provisioning new accounts. Which solution meets these requirements with the LEAST custom implementation effort?

**Correct answer:** Use AWS Control Tower to establish a landing zone and provision accounts through Account Factory.

**Explanation:** AWS Control Tower provides an automated way to establish and govern a multi-account environment. Its landing zone includes centralized logging and governance controls, and Account Factory provides standardized account provisioning.

### Cloud Technology and Services

**Question:**

An appliance manufacturer must proactively telephone customers about a product recall. It needs to run outbound calling campaigns that play an automated message and let customers speak with a representative to arrange a replacement. The manufacturer wants built-in campaign dialing and agent handling without developing a custom calling application. Which AWS service best meets these requirements?

**Correct answer:** Amazon Connect

**Explanation:** Amazon Connect provides a managed contact center with outbound campaigns. It can call customers, use contact flows to play automated messages, and connect customers to representatives without the manufacturer building its own dialing application.

### Billing, Pricing, and Support

**Question:**

A company is planning its first AWS application, which will use Amazon EC2, Amazon RDS, and Amazon S3. The company has estimated its compute hours, storage requirements, and request volumes. Before deploying any resources, a finance manager wants to compare estimated monthly costs for two AWS Regions. Which solution should the company use?

**Correct answer:** Create estimates in the public AWS Pricing Calculator using the planned services and usage for each Region.

**Explanation:** AWS Pricing Calculator estimates costs from selected services, Regions, configurations, and expected usage. The company can compare estimates before deploying resources or generating charges.

## Free CLF-C02 cheat sheets

- [Domain 1: Cloud Concepts](https://blowstack.com/cheat-sheets/aws-certified-cloud-practitioner/clf-c02-domain-1.pdf) (24% of the exam, PDF)
- [Domain 2: Security and Compliance](https://blowstack.com/cheat-sheets/aws-certified-cloud-practitioner/clf-c02-domain-2.pdf) (30% of the exam, PDF)
- [Domain 3: Cloud Technology and Services](https://blowstack.com/cheat-sheets/aws-certified-cloud-practitioner/clf-c02-domain-3.pdf) (34% of the exam, PDF)
- [Domain 4: Billing, Pricing, and Support](https://blowstack.com/cheat-sheets/aws-certified-cloud-practitioner/clf-c02-domain-4.pdf) (12% of the exam, PDF)

## Exam domains

The CLF-C02 questions are grouped into 4 domains divided into 19 tasks.

### Cloud Concepts (24% of the exam)

- Define the benefits of the AWS Cloud
- Identify design principles of the AWS Cloud
- Understand the benefits of and strategies for migration to the AWS Cloud
- Understand concepts of cloud economics

### Security and Compliance (30% of the exam)

- Understand the AWS shared responsibility model
- Understand AWS Cloud security, governance, and compliance concepts
- Identify AWS access management capabilities
- Identify components and resources for security

### Cloud Technology and Services (34% of the exam)

- Define methods of deploying and operating in the AWS Cloud
- Define the AWS global infrastructure
- Identify AWS compute services
- Identify AWS database services
- Identify AWS network services
- Identify AWS storage services
- Identify AWS artificial intelligence and machine learning (AI/ML) services and analytics services
- Identify services from other in-scope AWS service categories

### Billing, Pricing, and Support (12% of the exam)

- Compare AWS pricing models
- Understand resources for billing, budget, and cost management
- Identify AWS technical resources and AWS Support options

## Exam mode and practice mode

| | Exam mode | Practice mode |
|---|---|---|
| Questions count | 65 | 1 - 75 |
| Time limit | 90 minutes | Optional, 10 - 90 minutes |
| Exam scope | 4 domains with the official questions ratio | Selected domains with the official questions ratio |
| Correct answers | After exam submission | After exam submission or after each answer |
| Question types | Single answer and multiple answer | Single answer, multiple answer or all types |
| Question hints | Never | Optional |
| Question domain | Revealed after exam submission | Revealed after submission or during the exam |
| Scoring | 15 of 65 questions do not count towards the result | Official AWS method or mathematical mean |

See all simulator features on the AWS Exam Simulator page: https://blowstack.com/practice-exams

## About the CLF-C02 exam

While the AWS Certification exams are known to be challenging, the easiest one among them is still not easy by any means.

The scope of the CCP exam is quite broad, encompassing various aspects of the AWS ecosystem. Candidates are expected to demonstrate their knowledge in several key areas, including the basics of cloud computing, AWS global infrastructure, core AWS services, security and compliance, pricing and support plans, and the fundamentals of deploying and operating in the AWS cloud. This includes understanding the purpose and basic functions of essential services like Amazon EC2, S3, RDS, and Lambda, as well as more general concepts like billing, pricing models, and cloud architecture principles.

The exam places significant emphasis on AWS cloud concepts such as Elasticity, Availability, Serverless, AWS global infrastructure, and principles outlined in the Well-Architected Framework.

A significant portion of the exam focuses on ensuring that candidates can differentiate between different AWS services and their appropriate use cases. This requires not only memorization but also the ability to apply theoretical knowledge to practical scenarios. For instance, understanding when to use specific storage solutions like S3 versus EBS, or recognizing the best use cases for different database services such as RDS, DynamoDB, or Redshift, is crucial.

Moreover, the exam includes questions on security and compliance, which involves understanding AWS's shared responsibility model, basic security practices, and key AWS security services like IAM, KMS, and CloudTrail. This aspect tests a candidate's ability to ensure secure cloud environments, a critical skill for any AWS practitioner.

You can expect rather straightforward questions with limited text distractors and moderate difficulty.

## Technologies and concepts

- **7 Rs of Migration**: The framework classifies workloads as rehost, relocate, replatform, repurchase, refactor or re-architect, retain, or retire. It helps engineers choose an approach that balances business value, migration effort, operational risk, and long-term architecture goals rather than assuming every application should move unchanged.
- **Acceptable Use Policy**: An Acceptable Use Policy establishes behavioral rules for using cloud infrastructure, including restrictions on unlawful activity, spam, and security abuse. Engineers need to understand these rules to design compliant workloads, prevent misuse, and report suspected abuse through the correct provider channel.
- **Access Control**: Access control turns security requirements into enforceable permissions for people, applications, and cloud services. It limits unauthorized activity while preserving legitimate operations, including the ability to deliver logs, run health checks, and investigate incidents.
- **Amazon EC2 instance types**: An instance type represents a resource profile, allowing engineers to match a virtual machine to an application's performance and compatibility requirements. Understanding these profiles helps avoid bottlenecks, reduce unnecessary spending, and distinguish hardware selection from purchasing options such as On-Demand or Spot.
- **APIs**: An application programming interface defines available operations, accepted inputs, responses, and error behavior. In the cloud, APIs enable applications and automation tools to provision resources, configure services, and process data, making them the foundation of programmatic access.
- **Architecture Reviews**: An architecture review identifies risks, examines design trade-offs, and produces actionable improvements for a cloud workload. Frameworks such as the AWS Well-Architected Framework provide a consistent way to evaluate quality across multiple dimensions rather than focusing only on whether an application works.
- **Authentication**: Cloud systems use authentication to establish which identity is making a request by validating credentials or other evidence. It is distinct from authorization, which determines what that identity may do, and is essential for protecting administrative access, application data, and service-to-service communication.
- **AWS Cloud Adoption Framework (AWS CAF)**: AWS CAF organizes cloud transformation around six perspectives: Business, People, Governance, Platform, Security, and Operations. It helps organizations identify readiness gaps, coordinate stakeholders, and prioritize changes that support outcomes such as reduced business risk, improved ESG performance, increased revenue, and greater operational efficiency.
- **AWS Compliance**: Compliance in AWS combines AWS-provided infrastructure assurances with customer responsibilities for data, applications, configurations, and operating procedures. Engineers must identify applicable requirements, verify service and geographic scope, implement controls, and retain evidence rather than assume that using AWS makes a workload compliant.
- **AWS global infrastructure**: This infrastructure lets engineers choose where applications run, how they tolerate failures, and how closely they serve users. Understanding its geographic and operational boundaries is essential for designing availability, latency, disaster recovery, and data residency controls.
- **AWS Knowledge Center**: It supports self-service troubleshooting by turning frequently encountered AWS problems into focused explanations and resolution steps. Engineers use it alongside service documentation, AWS re:Post discussions, and AWS Support to diagnose issues, including security and access problems, without treating every question as a support case.
- **AWS Partner Network**: The AWS Partner Network (APN) connects customers with independent software vendors, systems integrators, consultants, and other organizations with AWS-related capabilities. It also provides participating organizations with training, technical resources, and business opportunities, helping customers access expertise beyond their own engineering teams.
- **AWS Prescriptive Guidance**: It provides actionable recommendations that connect business and technical goals with practical implementation steps. Engineers use it to evaluate approaches, identify prerequisites, and adapt established patterns to their workloads rather than designing every procedure from scratch.
- **AWS Professional Services**: The underlying concept is project-based professional assistance: specialists work with an organization to address technical, operational, and business challenges rather than simply troubleshoot individual service issues. Engineers should understand when a scoped consulting engagement is appropriate and how it differs from AWS Support, solutions architect guidance, and automated migration tools.
- **AWS re:Post**: AWS re:Post illustrates community-based technical support: engineers search existing answers or ask questions that other users and AWS experts can address. Understanding where this resource fits helps engineers distinguish free, public self-service assistance from curated technical guidance, account and billing assistance, and paid technical support.
- **AWS SDKs**: An SDK turns application code into requests to cloud services, handling common tasks such as request signing, serialization, credential lookup, and response parsing. Engineers choose SDKs when service operations belong inside an application or custom automation, rather than in a graphical console, shell command, or infrastructure template.
- **AWS Security Blog**: The AWS Security Blog helps engineers understand security practices and translate them into practical cloud configurations. Knowing when to use it, rather than documentation, troubleshooting articles, compliance resources, or a support case, helps teams find appropriate guidance efficiently.
- **AWS Security Center**: The concept is knowing where to obtain authoritative cloud security information and choosing the right resource for the question. Engineers use security information portals, troubleshooting articles, technical blogs, and compliance resources to inform decisions, while separate operational services inspect and protect their workloads.
- **AWS shared responsibility model**: AWS and its customers have distinct responsibilities for protecting systems, data, and operations, with the boundary changing according to the services used. Understanding that boundary helps engineers implement appropriate controls and collect the right evidence instead of assuming that AWS compliance certifications automatically make a workload compliant.
- **AWS Solutions Architects**: AWS Solutions Architects help engineers select architectural patterns, understand service capabilities, and assess trade-offs involving security, reliability, performance, cost, operations, and sustainability. For certification questions, the important distinction is between architectural guidance, operational troubleshooting through AWS Support, and scoped implementation assistance through AWS Professional Services.
- **AWS Support Center**: It provides a structured way to request help from AWS and maintain a record of the issue, supporting evidence, and correspondence. Engineers should distinguish account and billing assistance, which is available with Basic Support, from technical support, whose availability and response targets depend on the account's support plan.
- **AWS Support plans**: A support plan defines how an engineering team can obtain help from AWS, including permitted contact channels, case severity levels, and target initial response times. Selecting appropriate coverage helps teams manage operational risk, but it does not replace resilient architecture, monitoring, or incident-response procedures.
- **AWS Well-Architected Framework**: The framework helps engineers evaluate operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability through documented questions and best practices. For security governance, it connects architectural decisions to risk reduction and improvement plans, but it does not replace automated resource checks, compliance evidence, or regulatory audits.
- **Backup and Restore**: Backups preserve earlier states of data so engineers can recover from accidental deletion, application errors, ransomware, or infrastructure failures. Effective protection requires more than creating copies: it also requires suitable retention, protected access, and tested restoration procedures that meet business recovery objectives.
- **Benefits of migrating to the AWS Cloud**: Cloud migration can improve availability, adapt capacity to demand, accelerate delivery, and provide access to infrastructure near users worldwide. These benefits depend on architecture, cost management, automation, and organizational readiness rather than occurring automatically when workloads move.
- **Block Storage**: Block storage provides disk-like capacity for operating systems, databases, and applications that need direct reads and writes to specific locations. In the cloud, it can be delivered through persistent network-attached volumes or temporary disks attached to a compute host, making durability, performance, and lifecycle behavior important selection criteria.
- **Bring Your Own License**: BYOL separates software licensing from the purchase of cloud infrastructure, allowing organizations to reuse eligible license investments under the software vendor’s terms. Unlike license-included offerings, it requires customers to manage license eligibility, capacity, and compliance, so its economic value depends on both infrastructure costs and ongoing licensing obligations.
- **Caching**: A cache serves repeated requests without always accessing the original data source or recomputing a result. In cloud architectures, caching can reduce latency, origin load, and data transfer, but it requires deliberate decisions about freshness, capacity, security, and failure behavior.
- **Capital Expenditure**: Capital expenditure, commonly abbreviated CapEx, commits funds to assets that provide value over multiple accounting periods rather than being consumed immediately. In cloud economics, it matters because renting infrastructure can replace substantial upfront infrastructure investment with ongoing service charges, reducing the financial risk of buying capacity before demand is known.
- **CI/CD**: Continuous integration validates frequently merged code changes through automated builds and tests, while continuous delivery or continuous deployment automates the path toward production. Together, these practices shorten feedback cycles, make releases more repeatable, and reduce the risks associated with large, manually executed changes.
- **Cloud Service Models**: Infrastructure as a Service, Platform as a Service, and Software as a Service provide different levels of abstraction and operational control. Understanding these models helps engineers choose suitable services and identify who must secure, configure, patch, and maintain each part of a workload.
- **Commitment Discounts**: Cloud providers offer lower rates when customers commit to eligible resource usage or spending, commonly for one or three years. These discounts can reduce the cost of predictable workloads, but unused commitments can offset or eliminate the savings.
- **Compute**: In the cloud, compute provides on-demand CPU, memory, and optional accelerators through virtual machines, containers, and managed execution environments. Choosing an appropriate compute model helps engineers balance performance, cost, scaling behavior, and operational responsibility.
- **Configuration Management**: Configuration management makes infrastructure and application settings repeatable, auditable, and easier to recover when changes cause problems. In the cloud, it is a shared responsibility: the provider configures its underlying infrastructure, while customers manage the settings and software within their control.
- **Consolidated billing**: Consolidated billing lets an organization pay for multiple cloud accounts centrally without merging their workloads or security boundaries. It simplifies financial administration and can enable eligible volume discounts and shared commitment benefits, but requires clear cost allocation and purchasing controls.
- **Containers**: Containers provide a repeatable way to build, distribute, and run software across development and cloud environments. They improve deployment consistency and resource utilization, but require explicit controls for image security, runtime isolation, networking, identity, and persistent data.
- **Content Delivery Network**: A CDN reduces delivery latency and origin workload by serving reusable content from geographically distributed edge locations. It helps applications handle large audiences and traffic spikes, but its effectiveness depends on cache configuration, content freshness requirements, and origin resilience.
- **Cost Allocation**: Cost allocation turns a cloud bill into an accountable view of who consumed resources and which business activities incurred costs. Engineers apply account boundaries, resource metadata, and allocation rules to support budgeting, showback, chargeback, and informed architecture decisions.
- **Cost management**: In the cloud, cost management connects resource consumption and pricing choices to business outcomes. It helps engineers compare deployment options, eliminate waste, and balance spending against performance, availability, security, and operational effort.
- **Cost optimization**: Cloud cost optimization aligns resource consumption and pricing choices with actual workload needs. It matters because elastic infrastructure can accumulate waste quickly, and a lower bill is useful only when the workload still meets its operational requirements.
- **Credential Management**: Credentials include passwords, access keys, session tokens, and other material used to prove an identity. Managing their lifecycle reduces credential theft, limits the impact of compromise, and keeps applications working when credentials change or expire.
- **Credential Rotation**: Passwords, access keys, tokens, and application secrets can be exposed through compromised systems, accidental disclosure, or excessive distribution. Rotation limits how long a persistent credential remains usable, but it must coordinate changes across the identity system, secret storage, and consuming applications to avoid outages.
- **Data Archiving**: Archiving moves data out of active workflows while preserving its integrity, context, and accessibility for a defined retention period. In the cloud, object storage and archival storage tiers help reduce storage costs, but engineers must balance those savings against retrieval delays, access charges, and retention obligations.
- **Data Durability**: Durability describes how reliably stored data survives hardware failures, corruption, and other failures covered by the storage system's design. It matters when selecting storage because data can remain safely preserved even when temporarily inaccessible, and different storage options protect against different failure scenarios.
- **Data Egress**: Data egress describes outgoing traffic relative to a specified source; the same transfer is ingress at its destination. Cloud providers often charge for outgoing transfers based on volume, destination, and network path, making data movement an important part of architecture and cost planning.
- **Data Lakes**: Data lakes retain data in its original form and in prepared formats so different teams can reuse it for reporting, exploration, and machine learning. In the cloud, object storage commonly provides the storage foundation, while separate services handle ingestion, cataloging, governance, and computation.
- **Data Locality**: In cloud architectures, locality can mean using the same Region, Availability Zone, or processing environment, depending on the workload. It matters because network boundaries affect performance and billing, while replication and geographic distribution introduce trade-offs involving resilience, consistency, and data residency.
- **Data Residency**: Data residency connects the physical location of data to legal, contractual, and organizational requirements. Cloud architectures must account for primary databases, replicas, backups, logs, and downstream systems because choosing a deployment Region alone does not establish compliance.
- **Data Retention**: Retention policies balance business needs, recovery requirements, legal obligations, privacy, and storage cost. In the cloud, engineers implement them through lifecycle rules, backup schedules, retention periods, deletion controls, and exceptions such as legal holds.
- **Data Sovereignty**: In cloud architecture, data sovereignty influences where data can be stored and processed, who can access it, and whether it can cross jurisdictional boundaries. Engineers translate these obligations into Region selection, access controls, replication policies, and operational procedures rather than assuming that a particular hosting location guarantees compliance.
- **Database**: Databases give applications controlled access to persistent information, such as customer records, orders, and device readings. Choosing the right database model and operating approach affects correctness, performance, availability, security, and cost.
- **Database Replication**: Database replication maintains additional copies of database data by transferring an initial dataset and subsequent changes. In cloud migrations, it lets the source database continue serving applications while a target catches up, reducing the downtime needed to switch environments. Replication also supports resilience and distributed reads, but its consistency, recovery, and cost characteristics depend on the implementation.
- **Determinism**: Determinism concerns repeatability, not whether an answer comes from explicit rules or a learned model, and not whether that answer is correct. When choosing between conventional software and AI/ML, distinguish repeatable execution from guaranteed compliance with a specification: a model can repeatedly produce the same prediction without satisfying a requirement for an exact calculation or mandatory business rule.
- **Disaster recovery**: Disaster recovery combines recoverable data, replacement infrastructure, documented procedures, and testing to restore technology services after failures, attacks, or operational mistakes. In the cloud, it uses capabilities such as backups, replication, automated provisioning, and geographically separate deployments to balance recovery requirements against cost and complexity.
- **Discount sharing**: Cloud providers can apply unused commitment-based discounts across linked accounts and aggregate eligible usage for volume pricing. This can reduce total costs without combining workloads into one account, but eligibility rules, sharing settings, and internal cost allocation determine who benefits.
- **Distributed Tracing**: A distributed trace connects individual operations across services into a single view of a request's execution. It helps engineers troubleshoot cloud applications whose behavior cannot be understood from one server's logs or metrics alone.
- **DNS**: DNS lets applications and users find resources through stable names instead of hard-coded network addresses. In the cloud, it supports public websites, private service discovery, and endpoint selection while allowing the underlying infrastructure to change.
- **Document Data Model**: The document data model groups related information into records that commonly use JSON or a similar representation, rather than distributing every entity across fixed relational tables. It matters when applications need flexible record structures and efficient access to related data, but it requires deliberate decisions about keys, indexes, duplication, and consistency.
- **Elasticity**: Elasticity aligns available capacity with actual demand, adding resources during busy periods and releasing them when demand falls. In the cloud, automated provisioning and usage-based pricing can reduce idle capacity and avoid purchasing infrastructure for occasional peaks, while helping applications maintain performance.
- **Encryption**: Encryption helps prevent unauthorized parties from understanding data stored in cloud systems or transmitted over networks. Its effectiveness depends on protecting cryptographic keys, controlling decryption permissions, and applying encryption wherever sensitive data travels or persists.
- **Encryption at Rest**: Encryption at rest protects data stored in objects, disks, databases, snapshots, and backups from disclosure when the underlying storage is accessed without the required keys. In cloud environments, it combines storage encryption with key management and access controls, but it does not replace authorization, backups, or encryption in transit.
- **Encryption in Transit**: Encryption in transit prevents observers on a network path from reading protected data and, with correctly configured secure protocols, helps detect tampering and authenticate communicating endpoints. In cloud architectures, it applies to internet traffic, internal service communication, and hybrid or multi-cloud connections, independently of encryption at rest.
- **Ephemeral Storage**: Ephemeral storage holds disposable data such as caches, temporary files, and intermediate processing results. Its lifecycle is tied to a resource such as a virtual machine, container, or function execution environment, so applications must keep authoritative data elsewhere or be able to reconstruct it.
- **Event-Driven Architecture**: An event records something that has happened, such as an order being placed, a file being uploaded, or a monitoring threshold being crossed. By separating event producers from consumers, this architecture lets cloud applications process work independently, absorb traffic spikes, and deliver notifications without requiring every component to respond at the same time.
- **Failover**: Failover uses redundant resources, health detection, and a mechanism for transferring work to reduce interruptions when components fail. In cloud architectures, distributing those resources across multiple Availability Zones helps maintain availability when an instance or an entire zone becomes unavailable.
- **Fault Isolation**: Cloud systems use fault isolation to limit the scope of infrastructure failures, software defects, and resource exhaustion. Separating components into independent failure domains reduces correlated outages, but applications also need healthy alternatives and recovery mechanisms to remain available.
- **Fault Tolerance**: Fault-tolerant systems use redundancy, failure isolation, and automated handling of faults to keep component failures from becoming service failures. In the cloud, this capability also determines which workloads can safely use interruptible compute capacity and which need a more predictable capacity strategy.
- **Graph Data Model**: Graph modeling emphasizes how entities connect, rather than organizing information primarily into rows or independent documents. It is useful for relationship-heavy workloads such as fraud investigation, recommendations, dependency analysis, and knowledge graphs, where questions require following connections across multiple entities.
- **Heterogeneous Migration**: Heterogeneous migration changes the database technology as well as moving the data, such as migrating from Oracle Database to PostgreSQL. It can support licensing changes, modernization, and adoption of managed cloud databases, but requires assessment of schema compatibility, application changes, and operational risk.
- **High availability**: High availability reduces service interruptions by combining redundant components, isolated failure domains, health monitoring, and recovery mechanisms. In the cloud, it commonly involves distributing workloads across multiple Availability Zones so that a failure in one location does not stop the entire application.
- **Homogeneous Migration**: A homogeneous migration changes where a database runs without changing its underlying engine family. It generally reduces schema conversion and application rewrite work compared with moving between different engines, but still requires compatibility checks, data validation, and a controlled cutover.
- **Horizontal Scaling**: Instead of making one machine larger, horizontal scaling distributes work across multiple resources. It helps applications handle changing demand and can improve resilience, while requiring suitable workload distribution and state management. When automated to match demand, it provides elasticity.
- **Hybrid Cloud**: Hybrid cloud lets an organization keep some systems in facilities it controls while using public cloud resources for other parts of its environment. It matters when migration constraints, latency requirements, data-handling obligations, or existing investments make an entirely cloud-based deployment unsuitable.
- **Hybrid Cloud Storage**: Hybrid cloud storage combines local access with cloud-based capacity, durability, or data protection. It lets organizations keep applications and frequently accessed data close to users while using cloud storage for larger datasets, backup, or archival needs.
- **Identity Federation**: Federation separates where an identity is authenticated from where that identity accesses resources, using established trust and verifiable identity assertions or tokens. It enables centralized sign-in for employees, customers, and workloads while letting each application or cloud account retain control over authorization.
- **In-Memory Caching**: An in-memory cache keeps reusable copies of data or computation results close to the applications that need them. It reduces response times and backend workload, but engineers must manage data freshness, memory capacity, and behavior when cached entries are unavailable.
- **Infrastructure as code (IaC)**: IaC turns infrastructure definitions into repeatable deployment processes that can be reviewed, tested, and automated. It helps engineers create consistent environments, reduce manual errors, and apply security standards across accounts while maintaining a traceable history of changes.
- **IP Routing**: IP routing determines how traffic moves between subnets, private networks, and the internet. In cloud environments, understanding routes, subnet associations, and gateways is essential for designing connectivity and diagnosing why a workload can or cannot reach a destination.
- **Key Management**: Encryption depends on keeping cryptographic keys protected while making them available to authorized systems. Key management defines who controls those keys, how applications use them, and how access is audited and recovered, supporting both encryption at rest and encryption in transit.
- **Key-Value Data Model**: A key-value model organizes data as associations between identifiers and values rather than primarily as related tables. It is useful for access patterns such as retrieving a session, shopping cart, or user preference by identifier, and it underpins many cloud NoSQL databases and caches.
- **Least privilege**: Least privilege reduces the damage that compromised credentials, software defects, and operational mistakes can cause. In cloud environments, it applies to identity permissions, workload roles, administrative access, network connectivity, and organizational guardrails, and requires ongoing review as requirements change.
- **License Entitlements**: A license entitlement describes what an organization is authorized to use, including limits such as users, processor cores, features, duration, and permitted deployment environments. In the cloud, entitlement management connects software purchases to deployment and consumption so teams can control costs, enforce contractual limits, and demonstrate compliance.
- **License Portability**: Moving software to the cloud does not automatically grant permission to move its license with it. Understanding portability helps engineers compare bring-your-own-license and license-included options, estimate total costs, and design deployments that meet contractual requirements.
- **License-Included Pricing**: The cloud provider supplies the covered software license as part of the selected offering, so the customer does not need to bring a separate license for that software. This simplifies procurement and supports usage-based deployment, but engineers must compare total costs and verify which products, editions, and usage rights are actually included.
- **Load Balancing**: A load balancer provides an entry point that directs traffic to a pool of application instances, containers, or other endpoints according to routing rules and health information. It helps applications handle demand and continue serving users when individual targets fail, but it does not create additional application capacity by itself.
- **Management and governance**: Management handles activities such as provisioning, monitoring, configuration, and remediation, while governance defines who may act, which standards apply, and how compliance is demonstrated. Together, they help organizations give engineers useful autonomy without losing accountability, cost visibility, or control over risk.
- **Message Queuing**: A message queue buffers work between applications so that producers and consumers do not need to run at the same speed or be available simultaneously. This helps absorb traffic spikes and isolate failures, but requires careful handling of retries, duplicate messages, processing delays, and retention limits.
- **Migration and data transfer**: Cloud migration combines workload placement, application changes, and data movement to achieve business and technical goals. Engineers must choose an appropriate migration strategy, maintain data consistency, and account for transfer charges that depend on traffic direction, network path, and location.
- **Migration Phases**: A phased migration turns a large cloud adoption effort into manageable activities with measurable outcomes and decision points. It helps teams identify dependencies, address organizational and technical gaps, and reduce disruption while moving workloads and establishing cloud operations.
- **Multi-Factor Authentication**: Multi-factor authentication (MFA) combines factors such as something a person knows, possesses, or is, reducing the risk that a stolen password alone will allow unauthorized access. In cloud environments, it is especially important for privileged human access, root accounts, and sensitive operations, but it must be paired with appropriate authorization, session controls, and recovery procedures.
- **Network Address Translation**: Network Address Translation allows workloads to communicate using addresses different from those assigned to their network interfaces. Cloud architectures commonly use it to give private workloads outbound IPv4 connectivity, conserve public addresses, or connect networks that require address remapping.
- **Network Segmentation**: Network segmentation separates workloads by trust level, function, environment, or data sensitivity, then permits only the traffic required between them. It reduces exposure and limits lateral movement after a compromise, but effective segmentation requires enforced traffic controls rather than merely separate address ranges.
- **Networking, connectivity, and content delivery**: This concept combines network isolation, addressing, routing, name resolution, hybrid connectivity, traffic distribution, and delivery from geographically distributed edge locations. Engineers use these capabilities to balance reachability, security, latency, availability, and cost across public-facing applications and private systems.
- **Object Storage**: Object storage is designed to hold large collections of data without requiring applications to manage disks or traditional file systems. It is commonly used for images, videos, backups, logs, static website assets, and data lakes, with cost and access characteristics determined by the chosen storage class and configuration.
- **On-Premises Infrastructure**: Organizations use on-premises infrastructure to run applications and store data on systems located in their own facilities or in leased data-center space. Understanding this model helps engineers distinguish on-premises, cloud, and hybrid deployments and evaluate their differences in control, operational responsibility, cost, and scalability.
- **Operating Expenditure**: Operating expenditure, commonly called OpEx, covers day-to-day expenses rather than investment in long-lived assets. Cloud consumption often shifts infrastructure spending from upfront capital purchases to ongoing service charges, but those charges can include both fixed commitments and variable usage costs.
- **Password Policies**: Password policies establish requirements such as minimum length, prohibited passwords, reuse restrictions, and reset procedures to reduce unauthorized access. In cloud environments, their effectiveness depends on applying them to the correct identity source and combining them with multifactor authentication, secure credential storage, and appropriate access permissions.
- **Patch Management**: Patch management keeps operating systems, applications, and dependencies updated through repeatable policies and deployment workflows. In cloud environments, responsibility depends on the service model: providers patch infrastructure they operate, while customers patch the software layers they control. Effective patching combines automation with risk-based prioritization, availability safeguards, and continuous validation.
- **Pay-as-You-Go Pricing**: Cloud providers meter resources such as compute runtime, stored data, and requests, then charge according to the applicable rates. This helps organizations replace large upfront infrastructure investments with variable operating expenses, while making resource management and cost monitoring essential.
- **Privileged Access Management**: Privileged Access Management limits who can exercise powerful permissions, under what conditions, and for how long. In cloud environments, it protects root identities and administrative roles through strong authentication, temporary access, separation of duties, and monitoring, reducing the damage caused by stolen credentials or operator mistakes.
- **Public Cloud**: Organizations provision public cloud resources on demand rather than purchasing and operating all underlying physical infrastructure themselves. Understanding this model helps engineers distinguish cloud-based, hybrid, and on-premises deployments and evaluate their operational responsibilities, costs, and security requirements.
- **Publish-Subscribe Messaging**: Publishers do not need to know which applications or people receive their messages, allowing producers and consumers to evolve independently. This pattern supports event distribution, application integration, and operational alerts, especially when one event must reach multiple independent recipients.
- **Relational Data Model**: The relational data model provides a structured way to represent entities, their attributes, and their relationships while supporting integrity rules and flexible queries. It is commonly implemented by SQL database systems and is useful when applications need consistent records, joins across entities, and reliable transactional updates.
- **Resiliency**: Resiliency combines failure isolation, redundant resources, controlled recovery, and operational testing to limit the impact of failures. In the cloud, it requires deliberate architecture across independent failure domains rather than assuming that provider-managed infrastructure makes an application immune to outages.
- **Resource Efficiency**: Resource efficiency means matching cloud capacity and architecture to useful work rather than provisioning for assumptions or leaving resources idle. It helps engineers improve performance per resource, control costs, and reduce environmental impact while preserving security and reliability requirements.
- **Resource Tagging**: Tags describe business and operational attributes such as ownership, department, cost center, application, and environment without changing a resource’s function. A consistent tagging strategy supports cost allocation and resource management, while policy controls help prevent missing, misleading, or unauthorized tags.
- **Resource Utilization**: Resource utilization shows how workloads consume CPU, memory, storage, network bandwidth, and other capacity. It informs rightsizing: selecting resource types, sizes, and quantities that meet performance and availability requirements without paying for unnecessary capacity.
- **Retrieval Latency**: Retrieval latency determines whether stored data can support interactive requests or must be recovered through a slower, asynchronous process. It is a key storage-selection criterion because lower storage prices can come with longer retrieval delays, additional retrieval charges, or restoration requirements.
- **Right-Sizing**: Right-sizing uses observed demand and application requirements to choose appropriate compute, memory, storage, and throughput capacity. It reduces waste while preserving performance and reliability, and it requires regular review as workloads change.
- **Rightsizing**: Rightsizing uses measured demand to identify resources that are overprovisioned, underprovisioned, or poorly matched to their workloads. It reduces unnecessary spending without sacrificing required service levels and should be repeated as applications and usage patterns change.
- **Security**: Security combines technical controls, operational processes, and clearly assigned responsibilities to preserve confidentiality, integrity, and availability. In the cloud, providers secure the underlying infrastructure while customers configure and operate their workloads securely, using capabilities such as identity controls, encryption, network protection, and threat detection.
- **Serverless**: Serverless shifts infrastructure operations to the cloud provider so engineers can focus on application behavior, data, and configuration. It can reduce operational work and align costs with usage, but scaling behavior, billing, execution limits, and customer responsibilities vary by service.
- **Shared File Systems**: A shared file system lets applications on different servers work with the same files through familiar file operations rather than copying data between machines. In the cloud, managed file services support shared application content, user directories, and processing workloads while reducing the work of operating storage servers.
- **Stateful and Stateless Filtering**: Stateful filters remember permitted traffic flows and use that context to recognize return traffic, while stateless filters evaluate each packet without remembering earlier exchanges. This distinction determines how engineers configure bidirectional access, troubleshoot blocked responses, and combine workload-level controls with subnet boundaries and inspection firewalls.
- **Storage**: Cloud storage provides data capacity through managed services rather than requiring engineers to operate all underlying disks and storage systems. Choosing an appropriate storage model and tier requires balancing access patterns, performance, resilience, retention requirements, and total cost.
- **Storage Tiering**: Storage tiering balances storage cost against access latency, retrieval charges, and retention requirements. Cloud platforms implement it through explicit storage-class selection, lifecycle policies, or automatic movement based on access patterns, helping engineers avoid paying premium storage rates for rarely used data.
- **Subnetting**: Subnetting uses IP prefixes to divide address space into networks sized for particular workloads and operational needs. In cloud environments, it supports scalable network design across accounts, Regions, and virtual networks, while helping engineers avoid address conflicts and establish routing and security boundaries.
- **Temporary Credentials**: Temporary credentials let people and workloads access cloud resources without distributing permanent access keys. They reduce the lifetime of exposed credentials, support federation and role-based access, and shift credential renewal to identity services and supported client libraries.
- **Total Cost of Ownership**: Total Cost of Ownership (TCO) includes direct expenses, such as hardware or cloud usage, and indirect expenses, such as administration, facilities, and migration effort. It helps engineers compare deployment options fairly and determine whether moving a workload to the cloud will reduce overall costs rather than simply change how those costs are billed.
- **Usage-Based Pricing**: Cloud costs are calculated from billable quantities such as instance runtime, stored data, requests, and data transfer rather than solely from an upfront infrastructure purchase. Understanding these meters helps engineers compare purchasing options, estimate total workload costs, and avoid paying for idle resources or unsuitable commitments.
- **Virtual Private Networks**: A VPN connects networks or individual users without requiring a dedicated physical circuit between every endpoint. In cloud architectures, VPNs provide hybrid connectivity and remote access, often with lower initial costs than dedicated connections but with performance and availability that depend on the underlying transport.
- **Volume Discounts**: Cloud providers can charge lower unit rates as customers consume more of an eligible resource, such as storage or data transfer. Understanding the applicable thresholds, aggregation rules, and billing periods helps engineers estimate costs accurately and recognize when consolidated billing can improve pricing.
- **Vulnerability Assessment**: A vulnerability assessment determines which weaknesses exist, which resources they affect, and how urgently they need attention. In cloud environments, recurring assessments help engineers address vulnerable dependencies, exposed workloads, and insecure configurations as deployments and threat information change.
- **Workload Predictability**: Predictability helps engineers decide how much compute usage they can safely commit to and how much should remain flexible. Matching purchasing options to measured demand reduces costs without confusing predictable usage with interruption tolerance or guaranteed capacity.

## Services on the exam

The 112 AWS services the CLF-C02 exam covers.

[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena), [Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora), [Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront), [Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch), [Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito), [Amazon Comprehend](https://blowstack.com/tools/cloud-services-hub/amazon-comprehend), [Amazon Connect](https://blowstack.com/tools/cloud-services-hub/amazon-connect), [Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose), [Amazon DocumentDB (with MongoDB compatibility)](https://blowstack.com/tools/cloud-services-hub/amazon-documentdb-(with-mongodb-compatibility)), [Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb), [Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2), [Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling), [Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs)), [Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr)), [Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs)), [Amazon Elastic File System (Amazon EFS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-file-system-(amazon-efs)), [Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks)), [Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache), [Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr), [Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge), [Amazon FSx](https://blowstack.com/tools/cloud-services-hub/amazon-fsx-(for-all-types)), [Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty), [Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector), [Amazon Kinesis Data Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-streams), [Amazon Lex](https://blowstack.com/tools/cloud-services-hub/amazon-lex), [Amazon Lightsail](https://blowstack.com/tools/cloud-services-hub/amazon-lightsail), [Amazon Macie](https://blowstack.com/tools/cloud-services-hub/amazon-macie), [Amazon Neptune](https://blowstack.com/tools/cloud-services-hub/amazon-neptune), [Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service), [Amazon Polly](https://blowstack.com/tools/cloud-services-hub/amazon-polly), [Amazon Q](https://blowstack.com/tools/cloud-services-hub/amazon-q), [Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight), [Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds), [Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift), [Amazon Rekognition](https://blowstack.com/tools/cloud-services-hub/amazon-rekognition), [Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53), [Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3), [Amazon S3 Glacier](https://blowstack.com/tools/cloud-services-hub/amazon-s3-glacier), [Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker), [Amazon Simple Email Service (Amazon SES)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-email-service-(amazon-ses)), [Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns)), [Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs)), [Amazon Textract](https://blowstack.com/tools/cloud-services-hub/amazon-textract), [Amazon Transcribe](https://blowstack.com/tools/cloud-services-hub/amazon-transcribe), [Amazon Translate](https://blowstack.com/tools/cloud-services-hub/amazon-translate), [Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc), [Amazon WorkSpaces](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces), [Amazon WorkSpaces Applications](https://blowstack.com/tools/cloud-services-hub/amazon-appstream-2), [Amazon WorkSpaces Secure Browser](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces-web), [AWS Amplify](https://blowstack.com/tools/cloud-services-hub/aws-amplify), [AWS Application Discovery Service](https://blowstack.com/tools/cloud-services-hub/aws-application-discovery-service), [AWS Application Migration Service](https://blowstack.com/tools/cloud-services-hub/aws-application-migration-service), [AWS Artifact](https://blowstack.com/tools/cloud-services-hub/aws-artifact), [AWS Auto Scaling](https://blowstack.com/tools/cloud-services-hub/aws-auto-scaling), [AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup), [AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch), [AWS Billing and Cost Management](https://blowstack.com/tools/cloud-services-hub/aws-billing-and-cost-management), [AWS Budgets](https://blowstack.com/tools/cloud-services-hub/aws-budgets), [AWS Certificate Manager (ACM)](https://blowstack.com/tools/cloud-services-hub/aws-certificate-manager-(acm)), [AWS Client VPN](https://blowstack.com/tools/cloud-services-hub/aws-client-vpn), [AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation), [AWS CloudHSM](https://blowstack.com/tools/cloud-services-hub/aws-cloudhsm), [AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail), [AWS CodeBuild](https://blowstack.com/tools/cloud-services-hub/aws-codebuild), [AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline), [AWS Command Line Interface (AWS CLI)](https://blowstack.com/tools/cloud-services-hub/aws-command-line-interface-(aws-cli)), [AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer), [AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config), [AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower), [AWS Cost and Usage Report](https://blowstack.com/tools/cloud-services-hub/aws-cost-and-usage-report), [AWS Cost Explorer](https://blowstack.com/tools/cloud-services-hub/aws-cost-explorer), [AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms)), [AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect), [AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service), [AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk), [AWS Elastic Disaster Recovery](https://blowstack.com/tools/cloud-services-hub/aws-elastic-disaster-recovery), [AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate), [AWS Firewall Manager](https://blowstack.com/tools/cloud-services-hub/aws-firewall-manager), [AWS Global Accelerator](https://blowstack.com/tools/cloud-services-hub/aws-global-accelerator), [AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue), [AWS Health Dashboard](https://blowstack.com/tools/cloud-services-hub/aws-health-dashboard), [AWS IAM Identity Center (AWS Single Sign-On)](https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on)), [AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam)), [AWS IoT Core](https://blowstack.com/tools/cloud-services-hub/aws-iot-core), [AWS IoT Device Management](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-management), [AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms)), [AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda), [AWS License Manager](https://blowstack.com/tools/cloud-services-hub/aws-license-manager), [AWS Management Console](https://blowstack.com/tools/cloud-services-hub/aws-management-console), [AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace), [AWS Migration Evaluator](https://blowstack.com/tools/cloud-services-hub/aws-migration-evaluator), [AWS Migration Hub](https://blowstack.com/tools/cloud-services-hub/aws-migration-hub), [AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations), [AWS Outposts](https://blowstack.com/tools/cloud-services-hub/aws-outposts), [AWS Pricing Calculator](https://blowstack.com/tools/cloud-services-hub/aws-pricing-calculator), [AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink), [AWS Schema Conversion Tool (AWS SCT)](https://blowstack.com/tools/cloud-services-hub/aws-schema-conversion-tool-(aws-sct)), [AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager), [AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub), [AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts)), [AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield), [AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn), [AWS Storage Gateway](https://blowstack.com/tools/cloud-services-hub/aws-storage-gateway), [AWS Support](https://blowstack.com/tools/cloud-services-hub/aws-support), [AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager), [AWS Tools and SDKs](https://blowstack.com/tools/cloud-services-hub/aws-tools-and-sdks), [AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway), [AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor), [AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf), [AWS Well-Architected Tool](https://blowstack.com/tools/cloud-services-hub/aws-well-architected-tool), [AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray), [Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))

## Concepts on the exam

The 124 cloud concepts the CLF-C02 exam covers, each explained with the AWS services for it: https://blowstack.com/tools/cloud-concepts-hub?certification=aws-certified-cloud-practitioner

## Other practice exams

- [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional)
- [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional)
- [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate)
- [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner)
- [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate)
- [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty)
- [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist)
- [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional)
- [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate)
- [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate)
- [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty)
- [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate)
