A city council slide lists "encrypt everything" under the Cost Optimization pillar of the AWS Well-Architected Framework. Which pillar should that concern be moved to?
Select an answer to reveal the explanation.
Short Explanation
Encrypting data is a lock-and-key story, not a coupon story. Security is the pillar that covers protecting data with encryption, identity, and related controls; Cost Optimization is about spend efficiency and waste. Parking encryption under Cost Optimization mixes up the pillars, even though encryption choices can have cost side effects.
Full Explanation
Encrypting everything belongs under the Security pillar of the AWS Well-Architected Framework, not Cost Optimization. City council slides should place confidentiality and data-protection practices—encryption at rest and in transit, key management, access control—inside Security so sponsors do not confuse cost thrift with protective controls.
Performance Efficiency concerns efficient use of resources to meet requirements, not encryption placement. Reliability concerns recovery and availability under failure. Sustainability concerns environmental impact. Moving “encrypt everything” into those pillars mis-labels a core Security practice and confuses council oversight.
Exam caveat: Encryption and data protection map to Security; Cost Optimization is a frequent wrong bucket on slides. Operational check: update the council architecture one-pager so encryption and IAM controls sit under Security, verify KMS/key policies and TLS are enforced on the named municipal data stores, and keep cost initiatives on a separate Cost Optimization track.
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.