A board packet claims the AWS Well-Architected Framework has only three pillars. Which statement correctly corrects that claim?
Select an answer to reveal the explanation.
Short Explanation
Three is too short a list for Well-Architected. The real roster is six: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. Compute/storage/networking are service categories, not the pillar set, and Regions are not pillars either.
Full Explanation
The AWS Well-Architected Framework has six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. That statement correctly corrects a board packet claiming only three pillars and keeps municipal architecture reviews aligned to current CLF-C02 expectations.
Claiming exactly three pillars of compute, storage, and networking confuses service categories with Framework pillars. Saying four pillars while excluding sustainability is outdated and incomplete. Claiming nine pillars that map one-to-one to AWS Regions invents a false structure.
Exam caveat: Memorize the six pillar names; older five-pillar materials omit Sustainability. Operational check: update the board architecture template to list all six pillars, train reviewers on Sustainability questions, and reject any packet that still shows a three-pillar model.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.