AWS Cloud Computing Basics for CLF-C02 Exam Preparation

In a traditional on-premises environment, an organisation typically plans capacity, purchases equipment and maintains the facilities that support it. Cloud computing changes how those resources are obtained and managed. With AWS, customers can provision capabilities such as compute, storage and databases through management tools and APIs without purchasing the underlying physical infrastructure. Access is generally on demand, although quotas, regional availability and capacity constraints still apply. This model can shorten the time between identifying a need and testing a solution. It does not remove the need for architecture, security, financial oversight or ongoing operational management.

A useful financial distinction is between committing money to owned infrastructure and paying for services as they are consumed. Cloud adoption can reduce the need for large upfront infrastructure purchases, but it does not guarantee lower spending. Costs depend on service selection, usage patterns, pricing arrangements and how carefully resources are managed. Idle resources can still create charges, and stopping one component does not necessarily stop charges for associated storage or other resources. For the AWS Cloud Practitioner exam, connect cloud value to agility, flexible capacity and economies of scale rather than assuming that every migration automatically saves money.

Service models describe how management responsibilities are divided. Infrastructure as a Service, or IaaS, provides resources such as virtual machines, networking and storage while leaving substantial configuration and operating system work to the customer. Platform as a Service, or PaaS, provides a managed environment for deploying applications, reducing the infrastructure work developers perform. Software as a Service, or SaaS, delivers a ready-to-use application that customers access and configure. These are useful conceptual categories, not rigid labels for every AWS offering. Always examine what a particular service manages and what the customer must still secure, configure and maintain.

Deployment models answer a different question: where and for whom does the cloud environment operate? Public cloud services are offered by a provider to multiple customers, with controls that separate their resources. A private cloud is dedicated to one organisation and may be operated on premises or hosted elsewhere; an ordinary server room is not automatically a private cloud. Hybrid cloud combines distinct environments, commonly on-premises infrastructure and public cloud services, with connectivity or integration between them. Using multiple cloud providers is generally called multicloud. An Amazon Virtual Private Cloud provides logically isolated networking within AWS; it does not turn AWS into a private cloud.

Scalability is a system's ability to accommodate changes in workload by adjusting capacity. Vertical scaling changes the size or capability of an individual resource, such as selecting a larger virtual machine. Horizontal scaling changes the number of resources, such as adding application instances. Neither approach is automatically better in every situation. A larger machine may be straightforward to adopt, while additional instances may support both higher capacity and greater resilience if the application is designed appropriately. For exam scenarios, first identify whether the requirement concerns a bigger individual resource or more resources working together to serve the workload.

Elasticity emphasises matching capacity to demand as it changes, including reducing capacity when demand falls. For example, an online booking application might add instances during a sales event and remove them afterwards. Automated scaling can support this behaviour, but it depends on configuration, suitable metrics, service capabilities and an architecture that can use the added capacity. Elasticity is therefore not a promise of instant, unlimited resources. It can help avoid overprovisioning, but cost savings depend on what scales down and what remains chargeable. Serverless services reduce infrastructure management and often offer automatic scaling, yet still have quotas and service-specific charging rules.

Availability describes whether a system can perform its intended function when users need it. An AWS Region is a separate geographical area containing multiple Availability Zones. Each Availability Zone consists of one or more discrete data centres with redundant power, networking and connectivity. Zones within a Region are physically separated and connected through low-latency networking. Deploying suitable workloads across multiple Availability Zones can reduce the impact of a failure in one zone. However, simply creating resources in two zones does not make an application highly available: traffic routing, data replication, dependencies and recovery behaviour must also be considered.

Keep availability separate from durability and disaster recovery. Durability concerns the preservation of data over time; it does not guarantee that an application is reachable at every moment. Backups support recovery but do not automatically keep a service running during an outage. Disaster recovery plans address how workloads and data will be restored after disruptive events, using recovery time and data-loss objectives to guide design. Multi-Region architectures can support particular resilience, latency or regulatory requirements, but they add cost and complexity. For CLF-C02, recognise that regional service availability, data residency needs and proximity to users can all influence Region selection.

AWS describes shared responsibility as security of the cloud versus security in the cloud. AWS protects the infrastructure that runs its services, including physical facilities, hardware and the underlying networking and virtualisation layers. Customers remain responsible for how they use those services, including managing their data, permissions and relevant configurations. The exact boundary changes with the service selected. For an Amazon EC2 instance, the customer generally manages the guest operating system, including updates and security patches, as well as installed applications. AWS manages the physical infrastructure and host layer beneath that instance rather than administering everything inside it.

With more abstracted services, AWS takes on additional operational tasks, but customer responsibility does not disappear. For Amazon S3, customers do not patch storage servers; they still control matters such as data classification, access permissions and appropriate protection settings. Identity and access management remains central across service types: users and workloads should receive only the permissions needed for their tasks. Customers must also understand their compliance obligations and evaluate whether their configurations meet them. An AWS compliance certification does not automatically make a customer's application compliant. In exam questions, identify the service first, then locate the task within its responsibility boundary.

Turn each concept into a decision rule before memorising individual services. If demand rises and falls, consider elasticity; if the application must survive a location failure, consider availability and failure isolation. If a question asks who patches a component, identify the service's management boundary. Then connect these rules to the current CLF-C02 exam domains: Cloud Concepts, Security and Compliance, Cloud Technology and Services, and Billing, Pricing and Support. Check the official AWS exam guide for the current scope and the exam page for booking details, because offerings and policies can change. This provides a stronger basis for revision than relying on an old topic checklist.

For learners seeking an AWS certification for beginners, a structured next step is the [Erudex AWS Certified Cloud Practitioner (CLF-C02) course](/courses/aws-cloud-practitioner), followed by targeted [practice tests](/practice). Use practice results to identify conceptual gaps rather than memorising answer positions: explain why the correct option fits and why each alternative does not. Keep any course completion certificate distinct from AWS certification, which is earned by passing the official AWS exam. Before moving into detailed service revision, practise explaining the foundational concepts without notes and apply them to unfamiliar scenarios involving variable demand, sensitive data, operational responsibilities and service interruptions.