Chapter 1 of 424% of exam

Cloud Concepts and the Well-Architected Framework

This chapter introduces what cloud computing is and why organizations adopt it. You will learn the core value propositions of the AWS Cloud, the difference between capital and operating expenses, and the benefits of elasticity, scalability, and agility. It also covers cloud deployment and service models and the six pillars of the AWS Well-Architected Framework that guide sound design.

The value proposition of cloud computing

Cloud computing delivers IT resources on demand over the internet with pay-as-you-go pricing. Instead of buying and maintaining physical data centers, organizations rent compute, storage, and networking as they need it. This shifts spending from large upfront investments to variable costs that track actual usage.

Trade capital expense for variable expense

Pay for resources only as you consume them instead of investing heavily in data centers before you know how you will use them.

Benefit from massive economies of scale

Because AWS aggregates usage across many customers, it achieves lower costs and passes pay-as-you-go savings back to customers.

Stop guessing capacity

Provision what you need and scale up or down automatically, avoiding both over-provisioning and running short of capacity.

Stop spending on undifferentiated heavy lifting

Let AWS handle racking, powering, and maintaining servers so your teams can focus on work that differentiates the business.

Elasticity, scalability, and agility

A defining strength of the cloud is the ability to change the amount of resources quickly. Elasticity adds and removes capacity automatically to match demand, scalability lets a system grow to handle load, and agility lets teams obtain resources in minutes to experiment and innovate.

Elasticity matches supply to demand

Resources scale out during peaks and scale in during lulls, so you pay only for what you use at any moment.

Scale vertically or horizontally

Vertical scaling increases the size of a single resource, while horizontal scaling adds more resources such as additional instances.

Agility lowers the cost of experimentation

Fast provisioning and easy tear-down reduce the risk of trying new ideas, encouraging innovation.

Go global in minutes

Applications can be deployed across multiple Regions worldwide to reach users with low latency without building physical sites.

Deployment and service models

Workloads can run entirely in the cloud, entirely on-premises, or in a hybrid combination. Cloud services are also categorized by how much the provider manages, from infrastructure building blocks to complete applications.

Cloud, hybrid, and on-premises deployments

A hybrid model connects on-premises infrastructure with cloud resources, often used during migration or when data must stay local.

Infrastructure as a Service (IaaS)

Provides fundamental compute, storage, and networking building blocks with the most customer control.

Platform as a Service (PaaS)

Manages the underlying infrastructure so teams can focus on deploying and managing applications.

Software as a Service (SaaS)

Delivers a complete, provider-managed application that the customer simply uses, such as web-based email.

The six pillars of the Well-Architected Framework

The AWS Well-Architected Framework describes best practices for building secure, high-performing, resilient, and efficient workloads. It is organized into six pillars that help teams evaluate architectures and make informed trade-offs.

Operational excellence and security

Operational excellence focuses on running and monitoring systems to deliver value, while security protects data, systems, and assets.

Reliability and performance efficiency

Reliability ensures a workload performs correctly and recovers from failures, while performance efficiency uses resources efficiently as needs evolve.

Cost optimization

Delivers business value at the lowest price point by choosing appropriate pricing models and eliminating waste.

Sustainability

Minimizes the environmental impact of workloads by maximizing utilization and reducing the resources required.

Reliability and resilience concepts

Cloud architectures are designed to keep running despite failures. Understanding availability, fault tolerance, and loose coupling helps you build systems that remain dependable under stress.

High availability

Systems are designed to remain operational with minimal downtime, often by removing single points of failure.

Fault tolerance

A fault-tolerant system continues operating correctly even when some components fail, typically through redundancy.

Loose coupling

Reducing dependencies between components limits the impact of any single failure and improves resilience.

Design for failure

Assume components can fail and build redundancy and recovery into the architecture from the start.

Test your knowledge

Practice questions on Cloud Concepts and the Well-Architected Framework

Practice now →

Security, Identity, and Compliance

Last updated: July 2026