Objective and prerequisite
Use lesson 01’s distinction between a requirement and a product label to classify design goals and migration decisions. A design review needs a stated success measure. A migration plan needs dependencies and a recoverable sequence. Repeated provisioning needs a reusable definition. These are related project activities, but none can be replaced merely by saying that an environment is now in the cloud. By the end, explain why a proposed next step follows from a named constraint and what evidence would change that step.
Six review perspectives
The Well-Architected pillars are operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. Operational excellence concerns organizing and evolving workloads to deliver value; security concerns protecting data, systems, and assets. Reliability concerns consistent intended function when expected. Performance efficiency concerns efficient resource use to meet performance needs. Cost optimization concerns value at an appropriate price, while sustainability concerns environmental impact and resource use. An improvement can affect several pillars. For a single-choice foundational task, identify the explicitly controlling objective instead of claiming that an activity belongs exclusively to one pillar in every context.
Worked example: a community archive migration
Fictional teaching case: a community archive has a public catalog, a staff import tool, and a legacy index used by both. The index replacement is not yet validated, and the archive requires a way to reverse a failed cutover. First draw the dependency in words: moving either consumer does not prove the index will respond correctly afterward. Next group a proposed migration wave around dependencies that can be tested together. Define what successful cutover would demonstrate and what would trigger rollback. The immediate conclusion is to validate the dependency and recovery conditions before committing to a wave, rather than moving the whole portfolio at once. Check the plan by following a catalog request through the still-required index; if the route is unknown, the plan is not yet supported.
Contrast: repeatability is a different requirement
The same archive asks for identical demonstration environments to be recreated each month. That is a provisioning-definition problem, not a migration-wave decision. CloudFormation uses declarative templates for repeated provisioning, and templates can track infrastructure settings and changes. The console can help a person inspect an environment; a one-off visual action is not automatically a reusable template. Neither interface is universally superior. Match the output: observation for an inspection, a reusable declaration for reproduction, and a dependency-aware sequence for migration. Calling each of these “automation” without specifying the output hides the actual task.
Transfer check and check basis
Try before continuing: a local history project already has a dependency-tested move plan. Its next problem is that nobody can state which resource settings should be recreated after the move. Would another wave diagram resolve that gap? Check basis: not by itself. It needs an appropriate reusable infrastructure definition; migration sequencing and repeatable settings answer different questions. As a second check, name the pillar when the project’s primary measure is reducing environmental resource consumption while maintaining its service target: sustainability, with the service target retained as a constraint. Now use aws-clf-q-005–008 and cards aws-clf-card-04–06. This is conceptual planning, not implementation guidance or a complete migration architecture.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
What is CloudFormation? - AWS CloudFormationWhat is Amazon EC2? - Amazon Elastic Compute CloudWave planning - AWS Prescriptive GuidanceCost optimization - AWS Well-Architected FrameworkOperational excellence - AWS Well-Architected FrameworkPerformance efficiency - AWS Well-Architected FrameworkReliability - AWS Well-Architected FrameworkSecurity - AWS Well-Architected FrameworkSustainability - AWS Well-Architected FrameworkThe pillars of the framework - AWS Well-Architected Framework