Training / Certifications / AWS Cloud Practitioner / The AWS Well-Architected Framework

AWS Cloud Practitioner (CLF-C02) · Lesson 5 of 26

The AWS Well-Architected Framework

Name the six pillars of the AWS Well-Architected Framework, tell them apart from clue words in a question, and explain what the AWS Well-Architected Tool does.

Domain 1: Cloud Concepts (24%)Task 1.2About 5:53CaptionsStatic view for reduced motion
Lesson 5: The AWS Well-Architected Framework Illustrative example: the store is a sample workload Six pillarsOperational excellence, security,reliability, performance efficiency,cost optimization, sustainabilityTelling them apartClue words for each pillar,plus the AWS Well-ArchitectedTool to review a workloadYour workloadOperational excellenceSecurityReliabilityPerformance efficiencyCost optimizationSustainabilityDesign principles + best practicesWhat the framework gives youBest practices for six areasDesign principles for each pillarQuestions to review a workloadHelp weighing trade-offs between pillarsGuidance, not automationIt shows risks. Your team makes the changes.1 Operational excellenceRun workloads well, see how they operate,and keep improving the process.Design principles includeSafely automate: operations as codeMake frequent, small, reversible changesAnticipate failure, run game daysLearn from every operational eventAt the storeSmall updates ship from a template and rollback in minutes if something goes wrong.2 SecurityProtect data, systems and assetsusing cloud technologies.Design principles includeStrong identity and least privilegeTraceability: log and audit changesApply security at all layersProtect data in transit and at restAt the storeStaff get only the access they need,and customer data is encrypted.3 ReliabilityDo its job correctly and consistently,and recover quickly when something fails.Design principles includeAutomatically recover from failureTest recovery proceduresScale horizontally: many small resourcesStop guessing capacityAt the storeIf a web server fails, a healthy one takesover and customers keep shopping.4 Performance efficiencyUse computing resources efficiently, asdemand changes and technology evolves.Design principles includeUse advanced technology as a serviceGo global in minutesUse serverless architecturesExperiment more oftenAt the storeThe team tests two instance types and keepsthe one that serves pages fastest.$5 Cost optimizationDeliver business valueat the lowest price point.Design principles includeAdopt a consumption modelMeasure overall efficiencyStop spending on undifferentiated heavy liftingAnalyze and attribute spendingAt the storeTest servers stop at night, and tagsshow which team spends what.6 SustainabilityReduce the environmental impact of aworkload: less energy, fewer resources.Design principles includeUnderstand your impact, set goalsMaximize utilizationUse managed servicesAdopt more efficient hardware and softwareAt the storeOne busy server instead of two idle ones;old order data moves to colder storage.ReliabilityDoes it keep working andrecover after a failure?Server fails → replaced automaticallyPerformance efficiencyIs this the right resource, andis it used efficiently?Slow pages → faster resource typeCost optimizationAre we paying for anythingthat adds no value?Idle servers → stop or downsizeSustainabilityHow much energy and how manyresources per order?Low utilization → consolidatevsvsDefine a workloadThe store's web appAnswer questionsGrouped by pillarSee the risksHigh and medium risksImprovement planTrack with milestonesLenses add focused questionsThe Well-Architected Framework lens is appliedto every workload. Add Lens Catalog lenses,such as Serverless Applications, MachineLearning or SaaS, or write a custom lens.No chargein the AWS ManagementConsoleYour AWS resources bill as usualIf the question says……think“Recover automatically from failure”Reliability“Use resources efficiently as demand changes”Performance efficiency“Run, monitor and improve operations”Operational excellence“Least privilege, traceability, encryption”Security“Avoid unnecessary costs”Cost optimization“Minimize environmental impact”Sustainability“Review a workload against best practices”AWS Well-Architected ToolOperational excellenceRun, monitor, improveSecurityProtect data and systemsReliabilityRecover, meet demandPerformance efficiencyRight resource, efficiently$Cost optimizationNo unnecessary costSustainabilityLess environmental impactCheck a workload: AWS Well-Architected ToolNo charge · questions for each pillar · risks → improvement plan · lenses

Tip: turn your phone sideways or use full screen for larger labels.

Captions match the narration word for word. Press Space to play or pause and the arrow keys to change scenes.

Learning objective

Name the six pillars of the AWS Well-Architected Framework, tell them apart from clue words in a question, and explain what the AWS Well-Architected Tool does.

Exam mapping

Domain 1: Cloud Concepts (24%). Task statement 1.2 in the official exam guide.

Key takeaways

  • The AWS Well-Architected Framework gives best practices, design principles and review questions in six pillars: operational excellence, security, reliability, performance efficiency, cost optimization and sustainability.
  • Operational excellence: run and monitor workloads and keep improving, with operations as code and small, reversible changes. Security: protect data, systems and assets with least privilege, traceability, security at all layers and encryption.
  • Reliability: do the job correctly and consistently and recover from failure (automatic recovery, tested recovery, horizontal scaling, no capacity guessing).
  • Performance efficiency: use the right resources efficiently as demand and technology change (managed services, serverless, go global, experiment).
  • Cost optimization delivers business value at the lowest price point; sustainability, the newest pillar (2021), minimizes environmental impact by maximizing utilization.
  • The AWS Well-Architected Tool is a no-charge console service that reviews a workload against the pillars, shows high and medium risks, and builds an improvement plan. Lenses add domain-specific questions.

Exam tips

How the exam asks about this

Questions describe a situation and expect you to recognize the concept behind it.

If the question mentions…Think
Automatically recover from failure; test recovery proceduresReliability
Select the right resource types and sizes; experiment; go globalPerformance efficiency
Operations as code; small, reversible changes; learn from failuresOperational excellence
Least privilege, traceability, encryption at rest and in transitSecurity
Pay only for what you use; attribute spendingCost optimization
Reduce energy use and environmental impactSustainability
Review a workload against AWS best practices at no chargeAWS Well-Architected Tool

Common traps

  • Reliability is about recovering from failure and meeting demand; performance efficiency is about using the right resources efficiently. A failed server being replaced is reliability, not performance efficiency.
  • Sustainability isn't the same as cost optimization: one measures environmental impact, the other money. The same action, like removing idle servers, can help both.
  • The framework and the Well-Architected Tool don't change your resources: they identify risks, and you make the improvements.
  • There are six pillars, not five. Sustainability is the newest.

Practice

Exam-style questions

Answer each one before you open the explanation.

Question 1. A company wants its application to automatically recover when an Amazon EC2 instance fails. Which pillar of the AWS Well-Architected Framework does this BEST align with?

  1. Performance efficiency
  2. Reliability
  3. Cost optimization
  4. Operational excellence
Show answer

B. Reliability. Automatically recovering from failure is a reliability design principle. Performance efficiency is tempting, but it's about choosing and using resources efficiently, not surviving failures.

Question 2. Which pillar of the AWS Well-Architected Framework focuses on minimizing the environmental impact of running cloud workloads?

  1. Cost optimization
  2. Operational excellence
  3. Security
  4. Performance efficiency
  5. Sustainability
Show answer

E. Sustainability. Sustainability is about reducing energy use and resources for a workload. Cost optimization is tempting because idle resources waste both, but it measures money, not environmental impact.

Question 3. Which TWO are design principles of the security pillar of the AWS Well-Architected Framework? (Select TWO.)

  1. Go global in minutes
  2. Implement a strong identity foundation
  3. Adopt a consumption model
  4. Maintain traceability
  5. Stop guessing capacity
Show answer

B. Implement a strong identity foundation and D. Maintain traceability. A strong identity foundation (least privilege) and traceability (logging and auditing changes) are security principles. Going global is performance efficiency, a consumption model is cost optimization, and stopping guessing capacity is reliability.

Question 4. A company wants to review its workload against AWS architectural best practices and get an improvement plan. Which AWS service should it use?

  1. AWS Config
  2. AWS Trusted Advisor
  3. AWS Well-Architected Tool
  4. AWS CloudTrail
Show answer

C. AWS Well-Architected Tool. The AWS Well-Architected Tool reviews a workload against the framework's questions, shows high and medium risks and builds an improvement plan. Trusted Advisor is tempting, but it runs automated checks on account resources rather than a pillar-by-pillar workload review.

Question 5. A team makes frequent, small, reversible changes to its application and defines its operations as code. Which pillar of the AWS Well-Architected Framework does this practice support?

  1. Operational excellence
  2. Sustainability
  3. Cost optimization
  4. Reliability
Show answer

A. Operational excellence. Small, reversible changes and operations as code are operational excellence design principles. Reliability is tempting because small changes reduce risk, but its principles focus on recovering from failure and meeting demand.

Transcript

Lesson transcript

The full narration, scene by scene. The captions file contains the same text with timings.

Scene 1 · 0:00

Lesson 5: The AWS Well-Architected Framework. So far we've looked at why the cloud saves money and how to keep the bill low. Now we'll look at how to build well on AWS. This is task 1.2 in Domain 1: design principles of the AWS Cloud. We'll cover two ideas. First, the six pillars of the AWS Well-Architected Framework. Second, how to tell the pillars apart on the exam, and the free tool that reviews your workload against them.

Scene 2 · 0:32

Six pillars hold up a workload. AWS compares building a system to constructing a building: if the foundation isn't solid, problems show up later. The Well-Architected Framework gives you best practices and design principles in six areas, called pillars, and questions to review a workload against them. It also helps you weigh trade-offs between pillars. But it's guidance, not automation: it shows you the risks, and your team makes the changes.

Scene 3 · 1:00

Pillar 1: Operational excellence. The first pillar is operational excellence: running workloads well, seeing how they behave, and continuously improving the way you operate. Its design principles include safely automating operations as code, making frequent, small, reversible changes, anticipating failure, for example with practice events called game days, and learning from every operational event. Our store ships small updates from a template, so a bad change can be rolled back in minutes.

Scene 4 · 1:30

Pillar 2: Security. The second pillar is security: using cloud technologies to protect data, systems and assets. Its design principles include a strong identity foundation with least privilege, so each person gets only the access they need. Traceability, so every action and change is logged and audited. Security at every layer, from the network edge to the code. And protecting data in transit and at rest, for example with encryption.

Scene 5 · 1:59

Pillar 3: Reliability. The third pillar is reliability: a workload doing its job correctly and consistently when it's expected to, and recovering when something breaks. Its design principles include automatically recovering from failure, testing your recovery procedures, scaling horizontally by replacing one large resource with several small ones, and stopping guessing capacity. If one of the store's web servers fails, a healthy server takes over and customers keep shopping.

Scene 6 · 2:28

Pillar 4: Performance efficiency. The fourth pillar is performance efficiency: using computing resources efficiently to meet your requirements, and staying efficient as demand changes and technology evolves. Its design principles include using advanced technologies as managed services, going global in minutes with multiple Regions, using serverless architectures, and experimenting more often. The store's team can test two instance types side by side and keep the one that serves pages fastest.

Scene 7 · 2:56

Pillar 5: Cost optimization. The fifth pillar is cost optimization: delivering business value at the lowest price point. Its design principles include adopting a consumption model, so you pay only for what you use, measuring overall efficiency, stopping spending money on undifferentiated heavy lifting like running data centers, and analyzing and attributing spending. That's what lessons three and four were about: the store stops test servers at night, and tags show which team spends what.

Scene 8 · 3:27

Pillar 6: Sustainability. The sixth pillar, sustainability, is the newest: AWS added it in 2021. It's about reducing the environmental impact of a workload, using less energy and fewer resources for the same work. Its design principles include understanding your impact and setting goals, maximizing utilization, using managed services, and adopting more efficient hardware and software. One busy server uses less energy than two that sit mostly idle.

Scene 9 · 3:56

Telling the pillars apart. Two pairs of pillars cause most mistakes. Reliability asks: does it keep working and recover after a failure? Performance efficiency asks: is this the right resource, and is it used efficiently? A failed server being replaced is reliability; switching to a faster resource type is performance efficiency. Cost optimization is about money wasted. Sustainability is about energy and resources used. Consolidating idle servers helps both, so read the question's goal.

Scene 10 · 4:26

The AWS Well-Architected Tool. To review a real workload, use the AWS Well-Architected Tool in the AWS Management Console, at no charge. You define a workload, such as the store's web app, and answer questions grouped by pillar. The tool shows high and medium risks and builds an improvement plan you can track with milestones. The Well-Architected Framework lens is always applied, and you can add lenses for areas like serverless or machine learning.

Scene 11 · 4:57

How the exam asks about this. Here's how the exam asks about this. Recovering automatically from failure is reliability. Using resources efficiently as demand changes is performance efficiency. Running, monitoring and improving operations is operational excellence. Least privilege, traceability and encryption point to security. Avoiding unnecessary costs is cost optimization, and minimizing environmental impact is sustainability. And reviewing a workload against best practices is the AWS Well-Architected Tool.

Scene 12 · 5:24

Recap: the six pillars. To recap: the Well-Architected Framework has six pillars. Operational excellence runs and improves operations. Security protects data and systems. Reliability recovers from failure and meets demand. Performance efficiency uses the right resources efficiently. Cost optimization avoids unnecessary cost, and sustainability reduces environmental impact. The Well-Architected Tool reviews a workload against them at no charge. Next, we'll see how companies plan their move with the Cloud Adoption Framework.

Download captions (WebVTT)

Sources and accuracy

Checked against AWS documentation and the official CLF-C02 exam guide on October 18, 2026. AWS changes often, so confirm details in the current documentation. Diagrams and numbers in the animation are illustrative.

This free course is independent and isn't affiliated with or endorsed by Amazon Web Services. AWS and AWS Certified Cloud Practitioner are trademarks of Amazon.com, Inc. or its affiliates.

Preparing a team for AWS certification?

I run hands-on AWS training for teams, from Cloud Practitioner basics to architecture, built around your own environment.