Skip to main content
Checking session
← Back to CLF-C02

Certification

AWS Certified Cloud Practitioner

Cloud Concepts

Exam domain

Tasks

  1. 1.1 Define the benefits of the AWS Cloud.

    Cloud computing is the on-demand delivery of computing power, databases, storage, applications, and other IT resources over the internet with pay-as-you-go pricing. Instead of making large upfront hardware investments, organizations can provision resources rapidly and adjust them as requirements change.

    A cloud provider such as Amazon Web Services (AWS) operates the underlying infrastructure, while customers build and operate their workloads according to the AWS shared responsibility model.

    Six advantages of cloud computing

    AWS overview: Six advantages of cloud computing

    • Trade fixed expense for variable expense: Replace some upfront data-center and hardware costs with usage-based charges.
    • Benefit from economies of scale: AWS aggregates usage across many customers and can offer lower variable costs than many organizations can achieve independently.
    • Stop guessing capacity: Provision based on current demand and adjust capacity rather than relying only on long-range hardware forecasts.
    • Increase speed and agility: Provision resources on demand, experiment more quickly, and shorten infrastructure lead times.
    • Reduce data-center operations: Shift physical infrastructure work to AWS and focus staff on workloads and business outcomes.
    • Reach users globally: Deploy workloads in AWS Regions selected for latency, regulatory, residency, and business requirements.

    Business and technical value

    AWS Cloud value

    Cloud adoption can create business value when architecture, operations, governance, and usage support the intended outcome. Potential benefits include cost efficiency, staff productivity, operational resilience, agility, global reach, and improved resource utilization.

    • Cost efficiency: Elasticity and usage-based pricing can reduce idle capacity, but savings depend on utilization, architecture, pricing choices, and cost governance.
    • Staff productivity: Managed services can reduce some infrastructure maintenance so teams can spend more time on differentiated work.
    • Operational resilience: Redundant architectures can continue through component or localized failures. Multi-Availability Zone design improves resilience to localized failures; broader disaster or Regional resilience requires additional architectural decisions.
    • Agility: Rapid provisioning and automation can shorten experimentation and delivery cycles.
    • Sustainability: Efficient infrastructure and managed services can help organizations improve resource utilization, but workload design and customer choices still matter.
    • Security: AWS provides security capabilities and secures the cloud infrastructure. Customers remain responsible for security in the cloud according to the services they use.

    Global infrastructure

    AWS Global Infrastructure

    AWS operates Regions, Availability Zones, and edge locations. These infrastructure components support workload placement, resilient design, and lower-latency content delivery.

    • Region: A geographic area containing multiple isolated Availability Zones. Select Regions according to latency, service availability, compliance, data-residency, and business-continuity requirements.
    • Availability Zone: One or more data centers with independent power, cooling, and networking within a Region. Multi-AZ architectures help isolate localized failures.
    • Edge location: A site used by services such as Amazon CloudFront to cache and deliver content closer to users.
    • Global reach: Multi-Region deployments can serve users in different geographies, but they require deliberate data, networking, failover, and operational design.

    High availability, elasticity, and agility

    • High availability: Design a workload to remain available through expected failures by using appropriate redundancy, health checks, load balancing, and failover. The required scope depends on business availability and recovery objectives.
    • Elasticity: Add or remove resources to match demand. Scaling can be manual or automatic depending on the AWS service and its configuration; it is not universally instantaneous.
    • Agility: Provision infrastructure rapidly, automate repeatable work, and iterate without waiting for physical procurement.

    For example, a retail workload can use configured automatic scaling to add capacity during a promotion and remove it afterward. The response time, limits, and cost outcome depend on the selected services and scaling configuration.

  2. 1.2 Identify design principles of the AWS Cloud.

    The AWS Well-Architected Framework describes architectural best practices for designing and operating secure, reliable, efficient, cost-effective, and sustainable workloads. It provides a consistent way to evaluate decisions and identify improvements.

    AWS Well-Architected Framework

    The six pillars

    • Operational Excellence: Support development and run workloads effectively, gain insight into operations, and continually improve supporting processes and procedures.
    • Security: Use cloud technologies to protect data, systems, and assets while delivering business value through risk assessments and mitigation strategies.
    • Reliability: Ensure a workload performs its intended function correctly and consistently when expected, including operating and testing the workload through its total lifecycle.
    • Performance Efficiency: Use computing resources efficiently to meet system requirements and maintain that efficiency as demand changes and technologies evolve.
    • Cost Optimization: Run systems to deliver business value at the lowest appropriate price point. Understand spending, control where funds are allocated, choose appropriate resources, and manage demand.
    • Sustainability: Minimize the environmental impacts of running cloud workloads by reducing energy consumption and increasing efficiency across workload components.

    Distinguishing the pillars

    • Operational Excellence and Security: Operational Excellence emphasizes how teams operate and improve systems; Security emphasizes protection and risk management.
    • Reliability and Performance Efficiency: Reliability focuses on correct, consistent operation and recovery; Performance Efficiency focuses on selecting and adapting resources to meet requirements efficiently.
    • Cost Optimization and Performance Efficiency: Cost Optimization evaluates value and spending; Performance Efficiency evaluates efficient use of resources to meet performance requirements. Architecture must balance both.
    • Sustainability: Sustainability considers the environmental impact of workload design while the other pillars continue to impose their own requirements.

    General design principles

    AWS Well-Architected general design principles

    • Stop guessing capacity needs: Use cloud capacity and scaling mechanisms to respond to measured demand.
    • Test systems at production scale: Provision representative environments on demand and decommission them after testing.
    • Automate architectural experimentation: Use automation to create repeatable environments, test changes, and limit the cost of experimentation.
    • Allow for evolutionary architectures: Design so architecture can change as requirements and technologies evolve.
    • Drive architecture using data: Use workload measurements and operational evidence to evaluate architectural choices.
    • Improve through game days: Simulate events to test workload and team responses and identify improvements.
  3. 1.3 Understand the benefits of and strategies for migration to the AWS Cloud.

    AWS provides organizational guidance through the AWS Cloud Adoption Framework (AWS CAF) and workload-level choices through migration strategies. A migration plan connects business outcomes, people, governance, platform, security, operations, and the disposition of each workload.

    Components of the AWS Cloud Adoption Framework

    AWS CAF foundational capabilities

    AWS CAF groups organizational capabilities into six perspectives so business and technology stakeholders can identify readiness gaps and coordinate transformation.

    • Business: Align cloud initiatives with strategy, portfolio priorities, innovation, and business outcomes.
    • People: Develop cloud fluency, leadership, workforce skills, culture, and change capabilities.
    • Governance: Coordinate program, risk, portfolio, data, and Cloud Financial Management decisions.
    • Platform: Establish architecture, engineering, data, and delivery capabilities for cloud workloads.
    • Security: Protect confidentiality, integrity, and availability through governance, identity, infrastructure protection, data protection, detection, and response.
    • Operations: Establish observability, event, incident, change, availability, and continuity practices.

    The seven migration strategies

    • Rehost: Move an application to AWS with minimal architectural change.
    • Relocate: Move infrastructure to AWS without redesigning applications or changing existing operational tooling substantially.
    • Replatform: Introduce targeted cloud optimizations without changing the application's core architecture.
    • Refactor or re-architect: Change the application architecture to use cloud-native capabilities or satisfy new business and technical requirements.
    • Repurchase: Replace the existing application with another product, commonly a software-as-a-service offering.
    • Retire: Decommission an application that is no longer needed.
    • Retain: Keep an application in its current environment for now because of dependencies, constraints, priorities, or business value.

    Migration journey and support

    Migrate and modernize with AWS

    Migration commonly proceeds through assess, mobilize, and migrate-and-modernize activities. The sequence is iterative: organizations establish a business case, prepare governance and landing-zone capabilities, group workloads into waves, migrate, validate, and optimize.

    Programs and guidance

    • AWS Migration Acceleration Program (MAP): Provides methodology, tools, training, partner support, and possible financial benefits for eligible engagements. Benefits are subject to program eligibility and terms.
    • AWS CAF: Helps assess and develop organizational cloud-readiness capabilities.
    • AWS Prescriptive Guidance: Provides scenario-based migration patterns and recommendations.
    • AWS Professional Services and AWS Partners: Can provide planning and implementation assistance appropriate to an organization's needs.

    Current tools and services

    • Migration Evaluator: Builds a data-driven business case using environment inventory and utilization information.
    • AWS Transform: Is the current direction for new discovery, assessment, and migration projects following the availability changes for AWS Application Discovery Service and AWS Migration Hub.
    • AWS Migration Hub: Stopped accepting new customers on November 7, 2025. Existing customers can continue using it for ongoing migration projects; new migration projects should use AWS Transform.
    • AWS Transform MGN (formerly AWS Application Migration Service): Supports rehost migrations by continuously replicating source servers and launching them on AWS.
    • AWS Database Migration Service (AWS DMS): Supports homogeneous and heterogeneous database migration and replication with limited downtime.
    • AWS DMS Schema Conversion: Is the current AWS schema-conversion path for supported heterogeneous database migrations. AWS Schema Conversion Tool remains relevant to existing projects where current AWS guidance supports continued use.
    • AWS DataSync: Automates online data transfer between supported storage systems and AWS storage services.
    • Offline and edge alternatives: AWS Snow Family devices are no longer available to new customers. Evaluate AWS DataSync, AWS Data Transfer Terminal, AWS partners, or AWS Outposts for the applicable online transfer, physical transfer, or edge requirement.
  4. 1.4 Understand concepts of cloud economics.

    Cloud economics applies financial and operational principles to align cloud spending with business value. It includes the shift from fixed capacity to usage-based consumption, total cost of ownership (TCO), demand management, rightsizing, licensing, automation, and the use of managed services.

    Core cloud-economics concepts

    • Capital expenditure and operational expenditure: Cloud services can replace portions of upfront infrastructure investment with variable operating expense. The financial result depends on the workload, contract, accounting treatment, and governance.
    • Total cost of ownership: Compare direct costs such as hardware, software, facilities, power, networking, and labor, together with relevant indirect costs and migration expenses.
    • Economies of scale: AWS scale can lower variable prices, but each customer must still select and manage services efficiently.
    • Resource optimization: Match resource types, sizes, storage classes, and capacity models to workload requirements and measured usage.
    • Agility and productivity: On-demand resources, automation, and managed services can reduce lead times and undifferentiated infrastructure work.
    • Cost visibility: Allocation tags, account structures, budgets, and usage data help teams understand and govern spend.

    Fixed and variable costs

    Traditional environments often require fixed commitments for servers, storage, networking, facilities, power, maintenance, software, and staffing. Capacity must be purchased before demand is known, which can create idle capacity or shortages.

    AWS charges are commonly tied to resources provisioned or consumed. Variable cost improves flexibility, but does not guarantee lower cost: outcomes depend on workload utilization, architecture, data transfer, service choice, commitment choice, and ongoing governance.

    Pricing and commitment choices

    • On-Demand pricing: Provides flexibility without a long-term usage commitment for supported services.
    • Savings Plans: Offer discounted eligible usage in exchange for a consistent dollar-per-hour commitment over a one-year or three-year term.
    • Reserved Instances: Are service-specific reservation and discount constructs with their own scope, payment options, and terms; they are distinct from Savings Plans.
    • Spot Instances: Use spare Amazon EC2 capacity at discounted prices and can be interrupted, so they suit interruption-tolerant workloads.

    On-premises cost categories and TCO

    • Hardware and infrastructure: Procurement, refresh, depreciation, networking, and storage.
    • Facilities and utilities: Physical space, power, cooling, backup power, physical security, and maintenance.
    • Software and support: Licensing, subscriptions, maintenance, and vendor support.
    • Labor and operations: Administration, patching, monitoring, database operations, and security work.
    • Risk and opportunity costs: Capacity mismatch, downtime, delayed delivery, and compliance effort where relevant to the business case.

    AWS Migration Evaluator can inventory an existing environment and help create a data-driven migration business case and TCO comparison. AWS Pricing Calculator can estimate AWS service costs when workload requirements and proposed services are known. Estimates and business cases depend on the supplied assumptions and data.

    Licensing strategies

    • Bring Your Own License: Reuse eligible existing licenses when vendor terms and AWS service rules permit it.
    • License included: Pay for software licensing as part of the AWS resource or service price.
    • Select a model according to eligibility, portability, compliance, operational effort, and total cost.

    Rightsizing and continuous optimization

    AWS rightsizing guidance

    Rightsizing uses workload requirements and utilization evidence to select appropriate compute, storage, and database resources. A recommendation is an optimization opportunity, not a savings or performance guarantee.

    1. Collect suitable metrics: Use service metrics and application evidence. Amazon EC2 guest operating-system memory is generally not a default EC2 metric and can be collected by installing and configuring the CloudWatch agent.
    2. Analyze with the selected tool: Use the observation window and prerequisites documented for that tool rather than assuming a universal analysis period.
    3. Evaluate the recommendation: Check performance, availability, licensing, architecture, and business constraints before changing resources.
    4. Implement and verify: Make controlled changes, monitor the result, and repeat as usage evolves.

    Optimization may include resizing compute, removing idle resources, or moving eligible objects among precisely selected Amazon S3 storage classes, including applicable S3 Glacier storage classes. AWS Cost Optimization Hub consolidates and prioritizes supported optimization opportunities. AWS Compute Optimizer provides resource rightsizing recommendations that can feed the hub, while AWS Cost Explorer supports cost and usage analysis rather than serving as the consolidated optimization destination.

    Automation and managed services

    Automation and tooling

    Automation can improve repeatability, reduce manual error, shorten provisioning time, and support cost controls. Outcomes depend on sound policies, testing, observability, and maintenance of the automation itself.

    • Infrastructure as code: AWS CloudFormation and AWS Cloud Development Kit support repeatable infrastructure definitions.
    • Operational automation: AWS Systems Manager supports runbooks, patching, and other managed operations.
    • Elastic capacity: Configured scaling features can adjust capacity according to demand and policy.
    • Managed services: Services such as Amazon Relational Database Service and Amazon DynamoDB can reduce selected infrastructure-management tasks, while customers retain responsibility for workload configuration, data, access, and service-specific controls.

Practice this domain

Try a Domain Sample

Use a focused public sample to validate your understanding before creating an account.

Try Domain Sample