Cloud benefits and the Well-Architected Framework
The first questions on the exam test why companies move to the cloud and how AWS defines a good architecture. The vocabulary is small, so learn it precisely.
Benefits of the AWS Cloud
| Benefit | Meaning |
|---|---|
| Variable expense | Pay only for what you use instead of buying hardware upfront |
| Economies of scale | AWS aggregates huge usage, so prices per unit fall |
| Stop guessing capacity | Scale up or down as demand changes |
| Speed and agility | New resources in minutes, not weeks |
| No data center spend | Focus on your applications, not racks and power |
| Go global in minutes | Deploy in many Regions close to customers |
Elasticity means resources grow and shrink automatically with demand. Scalability means the system can handle more load. High availability means the workload keeps running when a component fails.
The six Well-Architected pillars
The AWS Well-Architected Framework describes how to build good workloads. The AWS Well-Architected Tool in the console reviews a workload against the pillars.
| Pillar | Idea |
|---|---|
| Operational excellence | Run and monitor systems, improve processes, perform operations as code |
| Security | Protect data and systems, strong identity, traceability, security at all layers |
| Reliability | Recover automatically from failure, scale horizontally, test recovery |
| Performance efficiency | Use the right resource types, go global, use serverless |
| Cost optimization | Avoid unneeded cost, adopt a consumption model, measure efficiency |
| Sustainability | Minimize the environmental impact of workloads |
Design principles in practice
- Design loosely coupled components, for example with Amazon SQS between a web tier and a processing tier, so one failure does not bring everything down.
- Avoid monolithic designs; split workloads into smaller services.
- Automate: infrastructure as code, automatic scaling and automatic recovery.
- Make frequent, small, reversible changes rather than large rare ones.
- Test at production scale because capacity is cheap to rent for a short time.
Other frameworks
The AWS Cloud Adoption Framework (AWS CAF) helps organizations plan a move. It has six core perspectives: Business, People, Governance, Platform, Security and Operations. Business capabilities include strategy management and data monetization; People includes culture evolution.
Exam traps
- Reliability is recovery and scaling; operational excellence is running and improving operations. Both mention automation.
- “Resource scalability” and “system elasticity” are benefits but are not Well-Architected pillars.
- “Economies of scale” is about AWS lowering prices through volume, not about your own scaling.
- Variable expense replaces capital expense, not operational expense.
- Agile development and tight coupling are not framework principles; loose coupling is.
Practice questions
Choose an answer, then review the explanation to check your understanding.
1. A company replaces a large upfront purchase of servers with services it pays for only while it uses them. Which cloud benefit is this?
Show answer
Answer: B.Pay-as-you-go pricing turns capital expense into variable expense, so there is no big upfront hardware purchase.
2. Which Well-Architected pillar covers the ability to recover from failures and to acquire resources dynamically to meet demand?
Show answer
Answer: C.Reliability is about recovering from disruptions and scaling to meet demand. Its principles include automatic recovery from failure and horizontal scaling.
3. Which design principle belongs to the operational excellence pillar?
Show answer
Answer: A.Perform operations as code (for example with AWS CloudFormation) is an operational excellence principle.
4. Which pillar was added to the framework in 2021 and focuses on the environmental impact of workloads?
Show answer
Answer: A.Sustainability is the sixth pillar. It aims to reduce the environmental impact of running cloud workloads.