[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cheat-sheet---en":3,"domain-info---en":3,"topic-info----en":3,"prev-aws-certified-cloud-practitioner-cloud-concepts-well-architected-framework-well-architected-overview-en":4,"next-aws-certified-cloud-practitioner-cloud-concepts-well-architected-framework-well-architected-overview-en":19,"lesson-aws-certified-cloud-practitioner-cloud-concepts-well-architected-framework-well-architected-overview-en":30},null,{"locked":5,"reason":6,"meta":7,"item":3},true,"paywall",{"title":8,"description":9,"isFree":10,"estimatedMinutes":11,"difficulty":12,"learningObjectives":13},"Availability, Elasticity, and Agility","Learn the key properties that make the cloud powerful: high availability, elasticity, scalability, and agility, and how they differ from one another.",false,14,"intermediate",[14,15,16,17,18],"Define high availability and reliability","Explain elasticity and how it follows demand","Compare elasticity with scalability","Describe agility and why it speeds up teams","Match each property to a real scenario",{"locked":5,"reason":6,"meta":20,"item":3},{"title":21,"description":22,"isFree":10,"estimatedMinutes":23,"difficulty":24,"learningObjectives":25},"The Six Pillars of the Well-Architected Framework","Learn the six pillars of the AWS Well-Architected Framework, what each one focuses on, and how to match a business scenario to the right pillar on the exam.",16,"beginner",[26,27,28,29],"Name the six pillars of the Well-Architected Framework","Explain the central focus of each pillar","Match a business scenario to the pillar it belongs to","Distinguish between similar pillars, such as reliability and performance efficiency",{"locked":10,"reason":3,"meta":31,"item":40},{"title":32,"description":33,"isFree":5,"estimatedMinutes":34,"difficulty":24,"learningObjectives":35},"What Is the AWS Well-Architected Framework?","Learn what the AWS Well-Architected Framework is, why a review is a conversation rather than an audit, what its general design principles are, and what the AWS Well-Architected Tool does.",13,[36,37,38,39],"Define the AWS Well-Architected Framework and what it is for","Explain why a Well-Architected review is a conversation, not an audit","List the six pillars and the general design principles","Describe what the AWS Well-Architected Tool does and what lenses are",{"id":41,"title":32,"body":42,"description":33,"difficulty":24,"estimatedMinutes":34,"extension":238,"infographics":239,"isFree":5,"learningObjectives":240,"meta":241,"navigation":5,"path":242,"quiz":243,"seo":287,"stem":288,"__hash__":289},"courses/courses/aws-certified-cloud-practitioner/en/domains/01-cloud-concepts/02-well-architected-framework/01-well-architected-overview.md",{"type":43,"value":44,"toc":225},"minimark",[45,50,54,57,61,64,67,80,84,87,90,94,97,118,121,125,128,167,171,174,177,181,184,204,208],[46,47,49],"h2",{"id":48},"why-this-framework-exists","Why this framework exists",[51,52,53],"p",{},"Building a system in the cloud means making a lot of decisions. Which services to use, how to protect your data, how to handle failures, how much to spend. Each decision has trade-offs, and it is easy to pick something that looks fine today but turns out to be costly or fragile later.",[51,55,56],{},"The AWS Well-Architected Framework gives you a reference point. It collects the best practices that AWS Solutions Architects learned after designing and reviewing thousands of customer architectures. With it you can compare your own design against those practices and see where to improve before a problem reaches production.",[46,58,60],{"id":59},"what-the-well-architected-framework-is","What the Well-Architected Framework is",[51,62,63],{},"The AWS Well-Architected Framework is a set of best practices and foundational questions for designing and operating workloads in the cloud. It helps you understand the pros and cons of the decisions you make, and it gives you a consistent way to measure your architecture against AWS recommendations.",[51,65,66],{},"The framework is organized into three parts that are worth keeping straight:",[68,69,70,74,77],"ul",{},[71,72,73],"li",{},"Six pillars, which are the qualities you expect from a good cloud system.",[71,75,76],{},"A set of general design principles that apply to almost any architecture.",[71,78,79],{},"Questions per pillar that you use to evaluate one specific workload.",[46,81,83],{"id":82},"a-review-not-an-audit","A review, not an audit",[51,85,86],{},"Applying the framework to a workload is called running a Well-Architected review. You answer the questions for each pillar, and from your answers you identify risks and areas to improve.",[51,88,89],{},"AWS is clear on one point: this is a constructive conversation about your architectural decisions, not an audit. Nobody passes or fails you. The goal is to find where you can do better and decide which changes are worth making for your business. An architecture can move away from a best practice on purpose when that decision makes sense for your case, as long as you make it knowingly.",[46,91,93],{"id":92},"the-six-pillars-at-a-glance","The six pillars at a glance",[51,95,96],{},"The framework rests on six pillars. Each one is an area where a good system should be solid:",[98,99,100,103,106,109,112,115],"ol",{},[71,101,102],{},"Operational Excellence",[71,104,105],{},"Security",[71,107,108],{},"Reliability",[71,110,111],{},"Performance Efficiency",[71,113,114],{},"Cost Optimization",[71,116,117],{},"Sustainability",[51,119,120],{},"This lesson only names them. The next lesson covers each pillar in detail, with its definition and an example. For the exam, learn all six by name, because questions tend to use these exact terms.",[46,122,124],{"id":123},"the-general-design-principles","The general design principles",[51,126,127],{},"Alongside the pillars, the framework offers six general design principles that apply to nearly any cloud architecture:",[68,129,130,137,143,149,155,161],{},[71,131,132,136],{},[133,134,135],"strong",{},"Stop guessing your capacity needs."," In the cloud you use as much or as little capacity as you need and scale automatically, so you do not have to bet on a fixed number of servers up front.",[71,138,139,142],{},[133,140,141],{},"Test systems at production scale."," You can spin up a full-size test environment on demand, run your tests, and shut it down afterward. You pay only for the time it ran.",[71,144,145,148],{},[133,146,147],{},"Automate with experimentation in mind."," Automation lets you create and replicate your workload at low cost, track changes, and roll back when something goes wrong.",[71,150,151,154],{},[133,152,153],{},"Consider evolutionary architectures."," In the cloud it is cheap to change a design, so your architecture can keep improving over time instead of being frozen at its first version.",[71,156,157,160],{},[133,158,159],{},"Drive architectures using data."," Collect data on how your workload behaves and use it to make fact-based decisions about how to improve, rather than relying on guesses.",[71,162,163,166],{},[133,164,165],{},"Improve through game days."," Schedule regular game days that simulate real production events to see how your architecture and your team respond, and where you can improve.",[46,168,170],{"id":169},"the-aws-well-architected-tool-and-lenses","The AWS Well-Architected Tool and lenses",[51,172,173],{},"The AWS Well-Architected Tool (WA Tool) is a free service inside the AWS console that guides you through a review. You answer the questions for each pillar against a workload, and the tool shows you the risks it finds and gives recommendations to reduce them. It also lets you save progress with milestones and compare how your architecture changes over time.",[51,175,176],{},"The core framework works for any kind of workload. When you need best practices for a specific case, you apply a lens. A lens extends the framework with recommendations for a particular workload type, for example serverless, machine learning, or high-performance computing. You apply the lens that fits your case on top of the core framework.",[46,178,180],{"id":179},"key-vocabulary","Key vocabulary",[51,182,183],{},"The framework uses a few terms worth recognizing:",[68,185,186,192,198],{},[71,187,188,191],{},[133,189,190],{},"Workload:"," a set of components that together deliver business value. This is the unit you review.",[71,193,194,197],{},[133,195,196],{},"Component:"," the code, configuration, and AWS resources that meet a requirement. Several components make up a workload.",[71,199,200,203],{},[133,201,202],{},"Milestone:"," a marker for a key change in your architecture as it evolves through the product lifecycle.",[46,205,207],{"id":206},"exam-tips","Exam tips",[68,209,210,213,216,219,222],{},[71,211,212],{},"The Well-Architected Framework is a set of best practices and questions for evaluating and improving architectures. It does not run workloads.",[71,214,215],{},"A review is a constructive conversation, not an audit. It does not pass or fail you.",[71,217,218],{},"The AWS Well-Architected Tool is free and lives inside the AWS console.",[71,220,221],{},"Remember that the framework has six pillars and six general design principles.",[71,223,224],{},"Lenses extend the framework with best practices for specific workload types.",{"title":226,"searchDepth":227,"depth":227,"links":228},"",3,[229,231,232,233,234,235,236,237],{"id":48,"depth":230,"text":49},2,{"id":59,"depth":230,"text":60},{"id":82,"depth":230,"text":83},{"id":92,"depth":230,"text":93},{"id":123,"depth":230,"text":124},{"id":169,"depth":230,"text":170},{"id":179,"depth":230,"text":180},{"id":206,"depth":230,"text":207},"md",[],[36,37,38,39],{},"/courses/aws-certified-cloud-practitioner/en/domains/01-cloud-concepts/02-well-architected-framework/01-well-architected-overview",{"passingScore":244,"questions":245},70,[246,255,261,271,279],{"question":247,"type":248,"options":249,"correctAnswer":251,"explanation":254},"What is the AWS Well-Architected Framework?","single",[250,251,252,253],"A service that runs your applications automatically","A set of best practices and questions for evaluating and improving cloud architectures","A mandatory certification you need before you can use AWS","A server type tuned for high performance","The framework documents best practices and a set of foundational questions you use to measure your architecture against AWS recommendations. It does not run workloads, it is not a certification, and it is not a server type.",{"question":256,"type":248,"options":257,"correctAnswer":259,"explanation":260},"A Well-Architected review is a formal audit that gives your architecture a pass or fail grade.",[258,259],"True","False","AWS describes the review as a constructive conversation about your architectural decisions, not an audit mechanism. The point is to find areas to improve, not to hand out a pass or fail result.",{"question":262,"type":263,"options":264,"correctAnswers":269,"explanation":270},"Which of the following are general design principles of the Well-Architected Framework? (Select all that apply.)","multiple",[265,266,267,268],"Stop guessing your capacity needs","Test systems at production scale","Drive architectures using data","Always buy the largest server available",[265,266,267],"Stopping capacity guesses, testing at production scale, and driving decisions with data are three of the six general design principles. Always buying the largest server works against the framework, which favors matching resources to real demand.",{"question":272,"type":248,"options":273,"correctAnswer":276,"explanation":278},"How much does it cost to use the AWS Well-Architected Tool to review a workload?",[274,275,276,277],"A fixed monthly fee per workload","A charge for each question you answer in the review","It is free to use","It is only available with a paid Support plan","AWS offers the Well-Architected Tool at no charge. It gives you a consistent process to review and measure a workload against the framework, with no per-workload fee and no Support plan requirement.",{"question":280,"type":248,"options":281,"correctAnswer":282,"explanation":286},"A team builds a serverless application and wants best-practice guidance specific to serverless, on top of the core framework. What should they apply?",[282,283,284,285],"A Well-Architected lens","A milestone","A seventh pillar","A separate AWS account","A lens extends the framework with best practices for a specific workload type, such as serverless or machine learning. Milestones record changes to an architecture over time, and there is no seventh pillar.",{"title":32,"description":33},"courses/aws-certified-cloud-practitioner/en/domains/01-cloud-concepts/02-well-architected-framework/01-well-architected-overview","5MVfyvCAy-M1WbUQ8EYnBXJXxdNefWK2oc-e4go3m60"]