Cloud Concepts Fundamentals — CLF-C02 practice questions

Practice questions for this topic, with explained answers.

Domain: Cloud Concepts ·100 questions · 30 easy · 40 intermediate · 30 hard · page 3 of 7

Question 31 clf-cloud-concepts-fundamentals-031

Easy · Choose one

"Stop guessing your capacity needs" is one of the general design principles of the AWS Well-Architected Framework. What does it recommend?

  1. a Purchase three-year commitments for every workload before it is deployed
  2. b Estimate demand once a year and adjust the environment at the annual review
  3. c Provision for the highest load the workload will ever experience and leave that capacity running
  4. d Use as much or as little capacity as you need and scale in and out automatically
Show answer & explanation

Answer: D

Why D is correct

The principle states that you use as much or as little capacity as you need and scale in and out automatically, which eliminates both expensive idle resources and the performance consequences of limited capacity. Guessing is replaced by measuring actual demand and letting automation respond to it.

Why the others are wrong

  • A — Commitment-based purchasing is a cost technique for steady baseline usage. It does not determine how much capacity runs at any moment, and committing before deployment is guessing.
  • B — An annual adjustment cycle is far too slow to track real demand and reintroduces the forecasting problem.
  • C — Provisioning permanently for the maximum load is the on-premises pattern the principle is written against, and it produces exactly the expensive idle resources it warns about.

Last verified: 2026-08-26

Question 32 clf-cloud-concepts-fundamentals-032

Easy · Choose one

Which AWS service helps a customer review their workloads against the AWS Well-Architected Framework and provides a plan to address identified issues?

  1. a AWS Compute Optimizer
  2. b AWS Config
  3. c AWS Systems Manager
  4. d AWS Well-Architected Tool
Show answer & explanation

Answer: D

Why D is correct

The AWS Well-Architected Tool provides a consistent process for reviewing a workload against the pillars of the framework. It asks structured questions, identifies high-risk and medium-risk issues, and produces an improvement plan with links to the relevant guidance.

Why the others are wrong

  • A — AWS Compute Optimizer analyzes utilization metrics and recommends better-suited resource configurations. Its scope is rightsizing, not the six pillars.
  • B — AWS Config records resource configurations and evaluates them against rules for compliance. It does not conduct a framework-based architectural review.
  • C — AWS Systems Manager operates and manages nodes, handling tasks such as patching and running commands. It is an operations tool, not a review framework.

Last verified: 2026-08-26

Question 33 clf-cloud-concepts-fundamentals-033

Easy · Choose one

Which Well-Architected pillar is defined as the ability of a workload to perform its intended function correctly and consistently when it is expected to, including recovering from disruptions?

  1. a Operational excellence
  2. b Sustainability
  3. c Performance efficiency
  4. d Reliability
Show answer & explanation

Answer: D

Why D is correct

That is the definition of the reliability pillar. It covers the ability to recover from infrastructure or service disruptions, dynamically acquire resources to meet demand, and mitigate disruptions such as misconfigurations and transient network issues.

Why the others are wrong

  • A — Operational excellence is about supporting development and running workloads effectively, and about continually improving processes and procedures.
  • B — Sustainability is about minimizing the environmental impact of running the workload.
  • C — Performance efficiency is about using resources efficiently to meet requirements as demand and technologies change.

Last verified: 2026-08-26

Question 34 clf-cloud-concepts-fundamentals-034

Intermediate · Choose one

A team creates a full-size copy of its production environment on demand, runs a load test against it, and then deletes it the same day. Which Well-Architected general design principle does this illustrate?

  1. a Test systems at production scale
  2. b Drive architectures using data
  3. c Improve through game days
  4. d Consider evolutionary architectures
Show answer & explanation

Answer: A

Why A is correct

The principle "test systems at production scale" says to create a production-scale test environment on demand, complete the testing, and then decommission the resources. Because you pay only while the environment is running, you can simulate the live environment for a fraction of the cost of maintaining a permanent on-premises test estate.

Why the others are wrong

  • B — Drive architectures using data means collecting data on how architectural choices affect workload behavior and making fact-based decisions. The load test may produce such data, but the principle illustrated by creating and deleting the environment is testing at production scale.
  • C — Improve through game days means scheduling simulated events in production to test how the architecture, processes, and people respond. This scenario is a scheduled load test on a disposable copy, not a simulated production incident.
  • D — Consider evolutionary architectures means allowing the design to change over time as innovations become available, supported by automation and on-demand testing.

Last verified: 2026-08-26

Question 35 clf-cloud-concepts-fundamentals-035

Intermediate · Choose one

An operations team schedules a regular exercise in which it deliberately simulates a failure event in production to see how the architecture, the runbooks, and the on-call engineers respond. Which Well-Architected general design principle is this?

  1. a Test systems at production scale
  2. b Automate with architectural experimentation in mind
  3. c Stop guessing your capacity needs
  4. d Improve through game days
Show answer & explanation

Answer: D

Why D is correct

Game days are described as regularly scheduled exercises that simulate events in production so that the team can see how the architecture and its processes actually perform. They surface gaps that documentation review never finds and build organizational experience in handling real events.

Why the others are wrong

  • A — Testing at production scale means standing up a full-size environment on demand for testing. A game day is run against the live production system and its people.
  • B — Automating with experimentation in mind is about creating and replicating workloads cheaply, tracking changes to automation, and reverting when needed.
  • C — Stop guessing your capacity needs concerns scaling capacity to demand rather than forecasting it in advance.

Last verified: 2026-08-26

Question 36 clf-cloud-concepts-fundamentals-036

Intermediate · Choose one

A team defines its infrastructure and its operational runbooks as version-controlled code, and triggers those procedures automatically in response to events. Which operational excellence design principle does this reflect?

  1. a Refine operations procedures frequently
  2. b Perform operations as code
  3. c Learn from all operational failures
  4. d Anticipate failure
Show answer & explanation

Answer: B

Why B is correct

Performing operations as code means applying the same engineering discipline used for application code to the whole environment: define the workload as code, script operational procedures, and trigger them automatically in response to events. AWS notes that this limits human error and produces consistent responses to events.

Why the others are wrong

  • A — Refining operations procedures frequently means looking for opportunities to improve procedures as they are used and as the workload evolves.
  • C — Learning from all operational failures means driving improvement from lessons learned and sharing them across teams.
  • D — Anticipate failure means running pre-mortem exercises to identify potential sources of failure and testing the response procedures for them.

Last verified: 2026-08-26

Question 37 clf-cloud-concepts-fundamentals-037

Intermediate · Choose one

A company adopts a policy that all releases must be small, deployed frequently, and reversible if they cause problems. Which pillar and design principle does this policy support?

  1. a Operational excellence, make frequent, small, reversible changes
  2. b Reliability, test recovery procedures
  3. c Security, prepare for security events
  4. d Cost optimization, measure overall efficiency
Show answer & explanation

Answer: A

Why A is correct

This is the operational excellence design principle "make frequent, small, reversible changes." Small increments make it far easier to identify which change caused a problem, and reversibility means a bad release can be withdrawn quickly rather than fixed under pressure, so the flow of beneficial changes into the workload increases without raising risk.

Why the others are wrong

  • B — Testing recovery procedures is about validating that failure recovery works, typically by simulating failures before they happen in earnest.
  • C — Preparing for security events concerns incident management policy, investigation processes, and response simulations.
  • D — Measuring overall efficiency compares the business output of a workload against the cost of delivering it. It is a financial measure, not a release practice.

Last verified: 2026-08-26

Question 38 clf-cloud-concepts-fundamentals-038

Intermediate · Choose one

An architecture review recommends replacing one very large database server with several smaller instances behind a distribution layer, so that the failure of any one instance removes only part of the capacity. Which reliability design principle does this follow?

  1. a Automatically recover from failure
  2. b Scale horizontally to increase aggregate workload availability
  3. c Manage change through automation
  4. d Test recovery procedures
Show answer & explanation

Answer: B

Why B is correct

Scaling horizontally replaces one large resource with multiple smaller ones so that a single failure does not take down the whole workload. Distributing requests across many small units also shrinks the blast radius of any one failure, which raises aggregate availability.

Why the others are wrong

  • A — Automatically recovering from failure means monitoring key performance indicators and triggering automated recovery when thresholds are breached. That is a response mechanism rather than the structural change described here.
  • C — Managing change through automation means applying changes to infrastructure through automation so that the change itself is tracked and reviewable.
  • D — Testing recovery procedures means validating that the recovery path works, typically by simulating failures. It does not change the topology of the workload.

Last verified: 2026-08-26

Question 39 clf-cloud-concepts-fundamentals-039

Intermediate · Choose one

A development team stops running its own search cluster and instead consumes a managed AWS search service, so that its engineers no longer need specialist expertise to operate it. Which performance efficiency design principle does this illustrate?

  1. a Consider mechanical sympathy
  2. b Experiment more often
  3. c Democratize advanced technologies
  4. d Go global in minutes
Show answer & explanation

Answer: C

Why C is correct

Democratizing advanced technologies means delegating complex tasks to the cloud vendor and consuming the technology as a service rather than asking the team to learn to host and run it. AWS gives NoSQL databases, media transcoding, and machine learning as examples of capabilities that become consumable services, which frees the team to focus on product development.

Why the others are wrong

  • A — Mechanical sympathy means choosing the technology approach that aligns best with your goals, for example matching a data store to the workload's access patterns.
  • B — Experimenting more often means using virtual, automatable resources to run comparative tests across instance types, storage options, and configurations.
  • D — Go global in minutes means deploying into multiple AWS Regions to lower latency for customers worldwide.

Last verified: 2026-08-26

Question 40 clf-cloud-concepts-fundamentals-040

Intermediate · Choose one

A team selects a purpose-built database whose data model matches the workload's access patterns instead of forcing every workload onto one general-purpose engine. Which performance efficiency design principle does this reflect?

  1. a Use serverless architectures
  2. b Go global in minutes
  3. c Consider mechanical sympathy
  4. d Democratize advanced technologies
Show answer & explanation

Answer: C

Why C is correct

Mechanical sympathy is the principle of using the technology approach that aligns best with your goals. AWS gives the example of considering data access patterns when selecting a database or storage option, which is precisely the reasoning behind choosing a purpose-built engine over a default one.

Why the others are wrong

  • A — Using serverless architectures removes the need to run and maintain servers for traditional compute activities. That is a different lever, though it may also be appropriate.
  • B — Go global in minutes is about deploying across Regions to reduce latency for a worldwide user base.
  • D — Democratizing advanced technologies is about consuming complex technology as a managed service instead of building expertise to run it.

Last verified: 2026-08-26

Question 41 clf-cloud-concepts-fundamentals-041

Intermediate · Choose one

A finance team and an engineering team jointly build capability in forecasting, budgeting, and cost awareness so that cloud spending is understood and controlled as a discipline. Which cost optimization design principle does this describe?

  1. a Adopt a consumption model
  2. b Stop spending money on undifferentiated heavy lifting
  3. c Analyze and attribute expenditure
  4. d Implement cloud financial management
Show answer & explanation

Answer: D

Why D is correct

Implementing cloud financial management means investing in this discipline the way an organization invests in security or operations: dedicating time, people, knowledge, programs, and processes so that the business becomes cost efficient. It is about building an organizational capability rather than performing a single optimization.

Why the others are wrong

  • A — Adopting a consumption model means paying only for what you use and increasing or decreasing usage with business need, for example stopping development environments outside working hours.
  • B — Stopping undifferentiated heavy lifting means letting AWS carry data center operations and managed service burdens so the team can focus on customers and business projects.
  • C — Analyzing and attributing expenditure means identifying the cost and usage of workloads and assigning them transparently to revenue streams and workload owners.

Last verified: 2026-08-26

Question 42 clf-cloud-concepts-fundamentals-042

Intermediate · Choose one

A company tags its resources so that each workload's cost can be reported to the team that owns it, letting those owners see their own spending and act on it. Which cost optimization design principle does this support?

  1. a Measure overall efficiency
  2. b Analyze and attribute expenditure
  3. c Implement cloud financial management
  4. d Adopt a consumption model
Show answer & explanation

Answer: B

Why B is correct

Analyzing and attributing expenditure is about identifying cost and usage accurately and attributing IT costs transparently to revenue streams and individual workload owners. That visibility is what lets owners measure return on investment and act to optimize their own resources.

Why the others are wrong

  • A — Measuring overall efficiency compares the business output of a workload against the cost of delivering it, which is a ratio rather than an attribution exercise.
  • C — Implementing cloud financial management is the broader organizational capability. Attribution is one practice within it, and the question describes that specific practice.
  • D — Adopting a consumption model concerns paying only for resources consumed and scaling usage with business requirements, such as turning off idle non-production environments.

Last verified: 2026-08-26

Question 43 clf-cloud-concepts-fundamentals-043

Intermediate · Choose one

A team consolidates several lightly used workloads onto fewer, better-utilized instances, noting that two hosts running at 30 percent utilization consume more energy than one host running at 60 percent. Which sustainability design principle does this apply?

  1. a Maximize utilization
  2. b Reduce the downstream impact of your cloud workloads
  3. c Establish sustainability goals
  4. d Understand your impact
Show answer & explanation

Answer: A

Why A is correct

Maximize utilization is the principle that calls for rightsizing workloads and implementing efficient designs so the underlying hardware runs at high utilization. AWS uses exactly this comparison, noting that two hosts at 30 percent are less efficient than one at 60 percent because of the baseline power each host draws regardless of load.

Why the others are wrong

  • B — Reducing downstream impact means lowering the energy or resources customers need to use your service, including avoiding forcing them to upgrade their devices.
  • C — Establishing sustainability goals means setting long-term targets such as reducing the compute and storage required per transaction, and planning so that growth reduces impact intensity.
  • D — Understanding your impact means measuring the impact of the workload, modeling future impact, and establishing key performance indicators from that data.

Last verified: 2026-08-26

Question 44 clf-cloud-concepts-fundamentals-044

Intermediate · Choose one

Under the shared responsibility model for sustainability, which statement is correct?

  1. a AWS is responsible for both the efficiency of the infrastructure and the efficiency of customer workloads
  2. b Sustainability is entirely an AWS responsibility once workloads are migrated
  3. c The customer is responsible for the renewable energy sourcing of the AWS Regions they use
  4. d AWS is responsible for sustainability of the cloud, such as efficient infrastructure and renewable power, while the customer is responsible for sustainability in the cloud, such as rightsizing and efficient data storage
Show answer & explanation

Answer: D

Why D is correct

Sustainability follows the same split as the rest of the shared responsibility model. AWS optimizes the infrastructure itself, including efficient shared hardware, high server utilization, water stewardship, renewable power sourcing, and energy-efficient cooling. The customer optimizes what they deploy on it: rightsizing compute, choosing efficient algorithms and storage patterns, and minimizing the resources their workload requires.

Why the others are wrong

  • A — AWS cannot make a customer's oversized, idle, or inefficient workload efficient. Resource selection and utilization sit with the customer.
  • B — Migrating does not transfer workload efficiency to AWS. An oversized, always-on architecture consumes more energy on AWS just as it did on premises.
  • C — Energy sourcing for AWS data centers is an AWS responsibility. Customers can influence their footprint by Region choice, but they do not procure the power.

Last verified: 2026-08-26

Question 45 clf-cloud-concepts-fundamentals-045

Hard · Select 2 answers

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

  1. a Consider mechanical sympathy
  2. b Adopt a consumption model
  3. c Keep people away from data
  4. d Maintain traceability
  5. e Scale horizontally to increase aggregate workload availability
Show answer & explanation

Answer: C and D

Why C and D are correct

Keep people away from data and maintain traceability are both security pillar design principles. Keeping people away from data means using tools and automation to remove the need for direct human access to sensitive data, which reduces mishandling and human error. Maintaining traceability means monitoring, alerting, and auditing actions and changes in real time, and integrating logs and metrics with systems that can investigate and act automatically.

Why the others are wrong

  • A — Considering mechanical sympathy is a performance efficiency pillar design principle.
  • B — Adopting a consumption model is a cost optimization pillar design principle.
  • E — Scaling horizontally to increase aggregate workload availability is a reliability pillar design principle.

Last verified: 2026-08-26