Cloud Concepts
Well-Architected Design Principles
CoreUse the six AWS Well-Architected pillars to identify the primary design concern in a workload scenario.
Aligned to the current CLF-C02 exam guide, verified August 15, 2026.
Why this matters
The exam expects more than recalling pillar names. You need to connect a stated outcome to the pillar that addresses it most directly.
Must Know
- The AWS Well-Architected Framework helps evaluate workloads through six complementary pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability.
- A practice can benefit several pillars, but an exam scenario normally includes one primary intended outcome.
- The framework provides principles and questions rather than one mandatory architecture.
- The AWS Well-Architected Tool supports a structured way to assess workloads against the framework.
Compare and Distinguish
- Operational excellence vs reliability: improve how the workload is run versus ensure it performs correctly and recovers from failure.
- Performance efficiency vs cost optimization: choose and evolve resources effectively versus eliminate waste and unnecessary expense.
- Security vs reliability: protect data and manage risk versus sustain and recover correct operation.
- Sustainability vs cost optimization: reduce environmental impact versus optimize financial value; one action may help both.
Scenario examples
- Scenario: A team automates changes, observes outcomes, and improves procedures after incidents. Think: Operational excellence.
- Scenario: A workload must recover automatically from a failed component. Think: Reliability.
- Scenario: Engineers regularly adopt more efficient resource types as technology evolves. Think: Performance efficiency.
- Scenario: A company reduces the environmental impact of idle compute while still meeting demand. Think: Sustainability is the stated outcome, even though cost may also improve.
Exam traps
- The framework is not a list of AWS products and does not prescribe one design for every workload.
- Cost optimization does not mean selecting the cheapest option regardless of business requirements.
- Reliability is not the same as security, even though security incidents can affect availability.
- Sustainability is not merely another name for performance or cost efficiency.
Key takeaways
- Operate and improve: operational excellence. Protect: security. Recover: reliability.
- Use resources well: performance efficiency. Avoid waste: cost optimization. Reduce environmental impact: sustainability.
- Choose the pillar from the primary outcome, not from a product mentioned in the scenario.
How it works
- Teams describe a workload, examine it through each pillar, identify risks or improvement opportunities, and prioritize actions according to business context.
- The Well-Architected Tool records answers, risks, and improvement plans for structured assessments.
- Framework guidance evolves, so design decisions should be revisited as requirements and AWS capabilities change.
When to use it
- Use the framework to examine an existing or proposed workload across complementary design concerns.
- Use the pillar definitions when a scenario asks which outcome a practice primarily supports.
- Use AWS CAF instead when the question is about organizational adoption capabilities and transformation readiness.
Security and governance implications
- Security is a dedicated pillar, but every pillar includes decisions that can affect risk.
- A Well-Architected assessment does not transfer responsibility for secure configuration or data protection to AWS.
Troubleshooting signals
- If several pillars seem helpful, underline the requested outcome and select the pillar whose definition states that outcome.
- Do not choose a pillar solely because an AWS service name appears in the scenario.
More detail
- Well-Architected thinking makes trade-offs explicit. Improving one concern can affect another, so teams evaluate decisions against workload context rather than chasing a single universal score.
- Pillar questions guide discussion and improvement. Cloud Practitioner candidates should recognize the concern each pillar addresses, not memorize detailed design checklists.
- The framework evaluates workloads. AWS CAF, by contrast, helps an organization prepare for and govern broader cloud-enabled transformation.
Ready for the quiz?
- Which pillar focuses on learning from operational events?
- How does reliability differ from performance efficiency?
- What clue makes sustainability the primary pillar?
- Why can one design decision affect several pillars?
Related objectives
- D1.2