CLF-C02 Cloud Concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Cost Optimization

  Why it's wrong here

  Cost Optimization is one of the original five pillars, but it is not the same as the sixth pillar. Its focus is on minimizing financial waste and maximizing business value — for example, using Spot Instances, Savings Plans, and eliminating idle resources. While right-sizing and higher utilization often reduce both cost and carbon footprint, Sustainability specifically addresses environmental impact by evaluating energy efficiency, lower-carbon Regions, and the embodied carbon of hardware. Confusing the two is common because their practices overlap, but their underlying objectives differ.

• ✓

  Sustainability

  Why this is correct

  Sustainability is the correct sixth pillar of the AWS Well-Architected Framework, added in December 2021. It focuses on minimizing the environmental impacts of running cloud workloads, including energy consumption and carbon emissions. Best practices include choosing lower-carbon AWS Regions, maximizing utilization via right-sizing or autoscaling, and using managed services that benefit from AWS’s efficient infrastructure. This pillar directly addresses the environmental footprint, which the other five pillars do not explicitly cover.

• ✗

  Governance

  Why it's wrong here

  Governance is not one of the six Well-Architected Framework pillars; the six are Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. Governance — the process of defining policies, roles, and compliance controls — is a broader organizational concern addressed by the AWS Cloud Adoption Framework (CAF) or prescriptive guidance, not a pillar. It is also a cross-cutting concern that spans Security and Operational Excellence, but it has no independent pillar status in the Well-Architected Framework.

• ✗

  Resilience

  Why it's wrong here

  Resilience is not a separate pillar; it is a core outcome of the Reliability pillar. The AWS Well-Architected Framework defines exactly six pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. Resilience — the ability to recover from failures and continue operating — is a reliability-oriented design goal achieved through mechanisms like multi-AZ deployments, backup strategies, and fault-injection testing, not an independent framework pillar.

Go deeper

Related to this question