CLF-C02 Exam Notes — Task Statement 1.2

Identify design principles of the AWS Cloud

Focus areas: AWS Well-Architected Framework · Six pillars · Differences between pillars · Design principles per pillar · Well-Architected Tool

Question 1

What is the AWS Well-Architected Framework?

A. A billing calculator that only estimates Amazon EC2 costs
B. AWS’s best practices and core strategies for architecting systems in the cloud so you can design, build, and operate reliable, secure, efficient, and cost-effective systems
C. A hardware catalog of servers that customers must purchase and rack themselves
D. A support plan that replaces AWS Support

Click to reveal answer

**Correct Answer:** B **Explanation:** The AWS Well-Architected Framework is AWS’s collection of **best practices and core strategies** for cloud architecture. It helps you design, build, and operate systems that are reliable, secure, efficient, and cost-effective, increasing the likelihood of success. - **A** describes something closer to AWS Pricing Calculator. - **C** is on-premises procurement, not a design framework. - **D** confuses the framework with AWS Support plans. **Exam tip / trap:** If a question asks *what the framework is*, think **best practices for architecture**, not a product you buy. Keywords: *reliable, secure, efficient, cost-effective*.

Question 2

The AWS Well-Architected Framework is based on which six pillars? (Choose six.)

A. Operational excellence
B. Security
C. Reliability
D. Performance efficiency
E. Cost optimization
F. Sustainability
G. Vendor lock-in
H. Manual capacity guessing

Click to reveal answer

**Correct Answer:** A, B, C, D, E, F **Explanation:** The six pillars are: 1. **Operational excellence** — run workloads effectively and improve processes 2. **Security** — protect data, systems, and assets 3. **Reliability** — workload performs correctly and consistently when expected 4. **Performance efficiency** — use computing resources efficiently as demand and tech change 5. **Cost optimization** — deliver business value at the lowest price point 6. **Sustainability** — reduce environmental impact, especially energy use - **G** and **H** are not pillars. “Stop guessing capacity” is a *design principle*, not a pillar name. **Exam tip / trap:** Memorize all **six** names. Older materials listed five pillars; **sustainability** was added later and **does appear on CLF-C02**. Do not invent pillars such as “elasticity” or “agility” — those are cloud benefits (Task 1.1), not WAF pillar names.

Question 3

A solutions architect wants to review a workload against the latest AWS architectural best practices. Which AWS tool compares a workload to the Well-Architected Framework?

A. AWS Well-Architected Tool
B. AWS Pricing Calculator
C. Amazon CloudFront
D. AWS Snowball

Click to reveal answer

**Correct Answer:** A **Explanation:** The **AWS Well-Architected Tool** reviews your workloads and compares them to the latest AWS best practices from the Well-Architected Framework. You answer questions about a workload and receive a report with identified risks and improvement guidance. - **B** estimates cost, not architecture quality. - **C** is a CDN. - **D** is a data-migration device. **Exam tip / trap:** Tool vs framework: the **Framework** is the documented best practices; the **Tool** is the console service that *measures* a workload against those practices.

Question 4

Which of the following are general design principles of the AWS Well-Architected Framework? (Choose TWO.)

A. Stop guessing capacity and use Auto Scaling so supply meets demand
B. Test systems at production scale and improve through game days
C. Always over-provision hardware years in advance
D. Avoid automation so every change is performed manually in production
E. Never allow architectures to evolve after launch

Click to reveal answer

**Correct Answer:** A, B **Explanation:** The lesson lists these general cloud design principles: - Stop guessing capacity; use **Auto Scaling** so supply meets demand - **Test systems at production scale** - **Automate** the architecture (makes experimentation easier) - Allow **evolutionary** changes - Use **data** to drive improvements - Improve through **game days** and production-level tests - **C**, **D**, and **E** reverse those principles. **Exam tip / trap:** “Game days” = scheduled exercises that simulate failure or load to see how the system and team respond. If you see *game day*, think Well-Architected general principles / operational excellence / reliability testing — not a pricing term.

Question 5

Which pillar of the AWS Well-Architected Framework is defined as the ability to support development and run workloads effectively, gain insight into operations, and continuously improve processes and procedures to deliver business value?

A. Operational excellence
B. Security
C. Cost optimization
D. Sustainability

Click to reveal answer

**Correct Answer:** A **Explanation:** **Operational excellence** = run workloads effectively + gain operational insight + continuously improve processes to deliver business value. Five design principles from the lesson: 1. Perform operations as **code** 2. Make **frequent, small, reversible** changes 3. **Refine** operations procedures frequently 4. **Anticipate** failure 5. **Learn** from all operational failures - **B** is protect data/systems/assets. - **C** is lowest price point for business value. - **D** is environmental impact. **Exam tip / trap:** Keywords for this pillar: *run effectively*, *insight into operations*, *continuously improve processes*, *operations as code*, *runbooks*, *game days*. Do not pick Reliability just because the word “failure” appears — “learn from operational failures” is Operational Excellence.

Question 6

A team stores infrastructure definitions in version control and deploys changes with scripts instead of clicking in the console. They make small updates that can be rolled back quickly. Which operational excellence design principles are they following? (Choose TWO.)

A. Perform operations as code
B. Make frequent, small, reversible changes
C. Protect data in transit and at rest
D. Democratize advanced technologies
E. Understand your environmental impact

Click to reveal answer

**Correct Answer:** A, B **Explanation:** - **Operations as code** — procedures and infrastructure are defined in code (version control, scripts, IaC), same as application code. - **Frequent, small, reversible changes** — tiny updates that can be undone reduce blast radius. - **C** is a **Security** principle. - **D** is **Performance efficiency**. - **E** is **Sustainability**. **Exam tip / trap:** Matching a principle to the **wrong pillar** is the #1 trap on this task. If the story is about *how the team operates and deploys*, it is Operational Excellence — even if security or cost also improve as a side effect.

Question 7

Which pillar focuses on protecting data, systems, and assets, and on using cloud technologies to improve security?

A. Security
B. Reliability
C. Performance efficiency
D. Cost optimization

Click to reveal answer

**Correct Answer:** A **Explanation:** The **Security** pillar is the ability to protect data, systems, and assets and to take advantage of cloud technologies to improve security. Seven design principles from the lesson: 1. Implement a **strong identity foundation** 2. Maintain **traceability** 3. Apply security at **all layers** 4. **Automate** security best practices 5. Protect data **in transit and at rest** 6. **Keep people away from data** 7. **Prepare for security events** **Exam tip / trap:** “Defense in depth” / “all layers” = Security. “Keep people away from data” means reduce direct human access (use tools, automation, and least privilege) — it does **not** mean “do not hire security staff.”

Question 8

A company wants every API call logged, encryption enabled for data at rest and in transit, and IAM used so users have only the permissions they need. Which Well-Architected pillar are these practices primarily associated with?

A. Security
B. Sustainability
C. Performance efficiency
D. Cost optimization

Click to reveal answer

**Correct Answer:** A **Explanation:** Map the story to Security principles: | Story detail | Security principle | |---|---| | IAM, least privilege | Strong identity foundation | | Every API call logged | Maintain traceability | | Encryption in transit and at rest | Protect data in transit and at rest | - **B** is energy/environment. - **C** is efficient use of compute. - **D** is lowest cost. **Exam tip / trap:** CloudTrail/logging can support both Security (traceability) and Operational Excellence (insight). On CLF, if the stem emphasizes *identity, encryption, protect data*, choose **Security**.

Question 9

Which security design principle means applying controls at the edge, VPC, subnet, load balancer, instance, and application — not only at the network perimeter?

A. Apply security at all layers
B. Go global in minutes
C. Maximize utilization
D. Stop guessing capacity

Click to reveal answer

**Correct Answer:** A **Explanation:** **Apply security at all layers** (defense in depth) is a Security pillar principle. Do not rely on a single firewall. Use multiple controls throughout the stack. - **B** is Performance efficiency. - **C** is Sustainability. - **D** is Reliability (and a general WAF principle). **Exam tip / trap:** “All layers” / “defense in depth” = Security. “Stop guessing capacity” is Reliability, *not* Security.

Question 10

Which pillar is the ability of a workload to perform its intended function correctly and consistently when it is expected to, including operating and testing the workload through its total lifecycle?

A. Reliability
B. Operational excellence
C. Performance efficiency
D. Sustainability

Click to reveal answer

**Correct Answer:** A **Explanation:** **Reliability** = the workload does the right thing, consistently, when you need it — across its full lifecycle (including testing recovery). Five design principles from the lesson: 1. **Automatically recover** from failure 2. **Test recovery procedures** 3. **Scale horizontally** to increase aggregate workload availability 4. **Stop guessing capacity** 5. **Manage change in automation** **Exam tip / trap:** Reliability vs Operational Excellence: - **Reliability** = *the workload* stays correct and available (failover, Auto Scaling, recovery testing). - **Operational excellence** = *how people and processes* run and improve operations (runbooks, small changes, learn from failures). If the stem says “workload performs its intended function,” it is Reliability.

Question 11

A company uses Amazon EC2 Auto Scaling so the application adds instances when traffic rises, instead of guessing peak size months ahead. Recovery is automated if an instance fails. Which Well-Architected pillar do these design principles primarily support?

A. Reliability
B. Sustainability only
C. Security
D. Vendor lock-in

Click to reveal answer

**Correct Answer:** A **Explanation:** Two Reliability principles appear in the stem: - **Stop guessing capacity** — let the system scale to demand - **Automatically recover from failure** — replace unhealthy instances without waiting for a human Horizontal scaling also increases aggregate availability (another Reliability principle). Auto Scaling can *also* help cost and performance, but the principles named here sit under **Reliability**. **Exam tip / trap:** Auto Scaling shows up under **Reliability** (availability/capacity), **Performance efficiency** (meet demand), and **Cost optimization** (don’t pay for idle). Read the *goal* in the question: if it is “stay available / don’t guess capacity / recover,” pick **Reliability**.

Question 12

Which reliability design principle is demonstrated by regularly simulating an Availability Zone failure to confirm that failover runbooks work?

A. Test recovery procedures
B. Protect data in transit and at rest
C. Democratize advanced technologies
D. Establish sustainability goals

Click to reveal answer

**Correct Answer:** A **Explanation:** **Test recovery procedures** means you do not wait for a real disaster to discover that backups or failover do not work. Game days and AZ-failure simulations belong here (and overlap with general WAF “improve through game days”). - **B** Security - **C** Performance efficiency - **D** Sustainability **Exam tip / trap:** “Test recovery” = Reliability. “Learn from operational failures” after an incident = Operational Excellence. Both can involve game days; match the *wording* of the stem.

Question 13

Which pillar is the ability to use computing resources efficiently to meet system requirements and to maintain that efficiency as demand changes and technologies evolve?

A. Performance efficiency
B. Cost optimization
C. Security
D. Operational excellence

Click to reveal answer

**Correct Answer:** A **Explanation:** **Performance efficiency** is about using the *right resources, the right way*, and staying efficient as load and technology change. Five design principles from the lesson: 1. **Democratize advanced technologies** (consume them as services; you don’t have to become an expert in every specialty) 2. **Go global in minutes** 3. **Use serverless architectures** 4. **Experiment more often** 5. **Consider mechanical sympathy** (choose technologies that fit how the workload actually works) **Exam tip / trap:** Performance efficiency vs Cost optimization: - **Performance** = meet requirements *efficiently* (right instance type, serverless, global, latest tech). - **Cost** = lowest *price point* for business value. A serverless design can serve both pillars; pick the pillar the question emphasizes.

Question 14

A startup wants to use machine learning and a global content delivery network without hiring a large team of specialists to build those systems from scratch. They also prefer AWS Lambda so they do not manage servers. Which performance efficiency design principles does this describe? (Choose TWO.)

A. Democratize advanced technologies
B. Use serverless architectures
C. Implement a strong identity foundation
D. Keep people away from data
E. Anticipate failure (as the primary goal)

Click to reveal answer

**Correct Answer:** A, B **Explanation:** - **Democratize advanced technologies** — consume ML, media, global delivery, etc. as managed services instead of building the capability in-house. - **Use serverless architectures** — Lambda and similar services remove server management and often scale automatically. “Go global in minutes” is also a performance efficiency principle (CDN/Regions), but it was not one of the listed correct options. - **C** and **D** are Security. - **E** is Operational Excellence / Reliability wording, not the focus of this stem. **Exam tip / trap:** *Serverless*, *go global in minutes*, *managed advanced services*, *experiment often* → Performance efficiency. “Mechanical sympathy” is a rare keyword meaning pick the service that matches the workload’s shape (for example, don’t use a disk-heavy database for a purely in-memory cache workload).

Question 15

Which pillar is the ability to run systems that deliver business value at the lowest price point?

A. Cost optimization
B. Reliability
C. Security
D. Performance efficiency

Click to reveal answer

**Correct Answer:** A **Explanation:** **Cost optimization** = deliver business value at the lowest price point. The lesson notes that this pillar is covered in more depth under Domain 4 (Billing, Pricing, and Support), but you must still recognize it as a Well-Architected pillar and distinguish it from the others. Typical practices (useful at CLF level): - Adopt a **consumption** (pay-for-what-you-use) model - **Right-size** resources - Use **managed services** to reduce undifferentiated heavy lifting - Measure efficiency and attribute spend **Exam tip / trap:** Lowest price ≠ ignore security or reliability. Cost optimization still assumes you meet business requirements. If the stem is *only* about money/price/waste, pick Cost optimization. If it is about *efficient compute to meet requirements*, pick Performance efficiency.

Question 16

Which pillar focuses on environmental impacts — especially energy consumption and efficiency — so architects can reduce resource usage?

A. Sustainability
B. Security
C. Reliability
D. Operational excellence

Click to reveal answer

**Correct Answer:** A **Explanation:** **Sustainability** addresses environmental impact, especially energy consumption and efficiency, and reducing resource usage. Six design principles from the lesson: 1. **Understand your impact** 2. **Establish sustainability goals** 3. **Maximize utilization** 4. **Anticipate and adopt** newer, more efficient hardware and software 5. **Use managed services** 6. **Reduce the downstream impact** of your cloud workloads **Exam tip / trap:** Sustainability is the **sixth** pillar and is in scope for CLF-C02. “Maximize utilization” here means fewer idle resources (better for the planet) — don’t confuse it with Cost optimization, though they overlap. If the stem mentions *carbon, energy, environment, downstream impact*, choose Sustainability.

Question 17

A company sets a goal to reduce the carbon footprint of its analytics jobs, moves those jobs to managed services, and right-sizes clusters so they are not sitting idle. Which Well-Architected pillar is the primary focus?

A. Sustainability
B. Security
C. Reliability
D. Identity foundation

Click to reveal answer

**Correct Answer:** A **Explanation:** Carbon footprint + managed services + less idle capacity maps directly to Sustainability principles: establish goals, use managed services, maximize utilization, reduce downstream impact. Right-sizing also helps **Cost optimization**, but the stem’s stated goal is environmental (carbon). On CLF, choose the pillar that matches the *stated business goal*. **Exam tip / trap:** One workload can touch several pillars. Always answer the pillar the question *asks about*, not every pillar that could apply.

Question 18

Which statements correctly contrast Well-Architected pillars? (Choose TWO.)

A. Reliability focuses on the workload performing correctly and recovering from failure; operational excellence focuses on how teams run and continually improve operations
B. Performance efficiency focuses on using resources efficiently as demand and technology change; cost optimization focuses on the lowest price point for business value
C. Security and sustainability are different names for the same pillar
D. Cost optimization means turning off all encryption to save money
E. Operational excellence replaces the need for IAM

Click to reveal answer

**Correct Answer:** A, B **Explanation:** Distinguishing pillars is an explicit exam skill. | Pillar | Primary question it answers | |---|---| | Operational excellence | How do we operate and improve how we work? | | Security | How do we protect data, systems, and assets? | | Reliability | Does the workload work correctly whenever it should? | | Performance efficiency | Are we using the right resources efficiently? | | Cost optimization | Are we delivering value at the lowest price? | | Sustainability | What is our environmental impact, and how do we reduce it? | - **C**, **D**, and **E** are false and unsafe. **Exam tip / trap:** Never choose an answer that sacrifices security “to save money.” Cost optimization does not override Security.

Question 19

When designing highly scalable applications on AWS, which practices align with Well-Architected design principles? (Choose TWO.)

A. Design for failure and decouple components (service-oriented design)
B. Implement elasticity with Auto Scaling and use parallelization to split work across components
C. Run every tier on a single Amazon EC2 instance to keep the design simple
D. Guess peak capacity once, buy it, and never change it
E. Avoid automation so changes stay manual

Click to reveal answer

**Correct Answer:** A, B **Explanation:** The lesson emphasizes these cloud design practices (also common on CLF and SAA exams): - **Design for failure** — assume components will fail; recover automatically (Reliability). - **Decouple components** — service-oriented architecture so one failure or scale event does not tightly couple everything. - **Elasticity / Auto Scaling** — match supply to demand. - **Parallelization** — break a job into simple parts and distribute them (for example, split a large dataset into chunks processed at the same time) for faster processing. - **C** is a single point of failure. - **D** violates “stop guessing capacity.” - **E** violates automation principles. **Exam tip / trap:** **Parallelization** ≠ decoupling, but they are related. Decoupling = independent components communicating loosely. Parallelization = divide work and run it at the same time. If you see “break a large job into chunks,” think parallelization.

Question 20

Match each requirement to the most appropriate Well-Architected pillar.

A workload must: (1) encrypt data and use least-privilege IAM, (2) fail over automatically when an instance becomes unhealthy, (3) use the smallest efficient instance type that still meets latency targets, and (4) reduce energy waste by turning off unused development environments at night.

Which mapping is correct?

A. (1) Security (2) Reliability (3) Performance efficiency (4) Sustainability
B. (1) Reliability (2) Security (3) Sustainability (4) Performance efficiency
C. (1) Cost optimization (2) Operational excellence (3) Security (4) Reliability
D. (1) Sustainability (2) Performance efficiency (3) Security (4) Reliability

Click to reveal answer

**Correct Answer:** A **Explanation:** Map each requirement to the pillar whose definition it matches: | Requirement | Pillar | Why | |---|---|---| | Encrypt + least-privilege IAM | **Security** | Identity foundation; protect data | | Automatic failover of unhealthy instance | **Reliability** | Automatically recover from failure | | Smallest efficient instance that still meets latency | **Performance efficiency** | Use compute efficiently to meet requirements | | Reduce energy waste; shut off unused envs | **Sustainability** | Maximize utilization; reduce environmental impact | (Nightly shutdown also saves money — Cost optimization — but the stem said **energy waste**, so Sustainability is the best fit.) **Exam tip / trap:** This is the core Task 1.2 skill: **identify differences between pillars**. Read the *goal words*: protect → Security; recover/available → Reliability; efficient resources/latency → Performance; lowest price → Cost; energy/carbon → Sustainability; processes/runbooks/code → Operational excellence.

Quick revision card — Task 1.2

Pillar	Definition (exam one-liner)	Design-principle keywords
Operational excellence	Run workloads well; insight; improve processes	Operations as code; small reversible changes; refine procedures; anticipate failure; learn from failures
Security	Protect data, systems, assets	Identity foundation; traceability; all layers; automate security; encrypt in transit/at rest; keep people away from data; prepare for events
Reliability	Workload works correctly and consistently when expected	Auto recover; test recovery; scale horizontally; stop guessing capacity; manage change with automation
Performance efficiency	Use compute efficiently as demand and tech evolve	Democratize advanced tech; go global in minutes; serverless; experiment often; mechanical sympathy
Cost optimization	Business value at the lowest price point	Consumption model; right-size; managed services; measure efficiency (Domain 4)
Sustainability	Reduce environmental impact (energy/efficiency)	Understand impact; set goals; maximize utilization; adopt efficient hardware/software; managed services; reduce downstream impact

Also know

Well-Architected Tool = review a workload vs latest best practices
General principles: stop guessing capacity, Auto Scaling, test at production scale, automate, evolve architecture, use data, game days
Scalable app patterns: design for failure, decouple, elasticity, parallelization