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 2 of 7

Question 16 clf-cloud-concepts-fundamentals-016

Intermediate · Select 2 answers

A company's on-premises application is sized for peak load and runs at roughly 15 percent average utilization. After migrating, the company runs the same application on AWS with automatic scaling. Which TWO benefits does it gain? (Choose TWO.)

  1. a The application automatically becomes compliant with every regulatory framework
  2. b The application no longer requires any monitoring
  3. c Capacity is matched to actual demand instead of being fixed at the annual peak
  4. d Network latency for all users is reduced to under one millisecond
  5. e Costs move from a large up-front purchase to charges based on consumption
Show answer & explanation

Answer: C and E

Why C and E are correct

Automatic scaling in the cloud attacks the two problems of peak-sized ownership at once. Capacity now follows demand, so the roughly 85 percent of capacity that used to sit idle on average is simply not running, and the spend shifts from a fixed up-front hardware purchase to a variable charge that tracks consumption.

Why the others are wrong

  • A — Compliance is never automatic. AWS provides compliant infrastructure and evidence, but the customer must configure and operate the workload to meet the applicable framework.
  • B — Monitoring becomes more important, not less. Scaling decisions are driven by metrics, and the customer still needs visibility into application health.
  • D — Sub-millisecond latency for every user is physically impossible over long distances. Latency improves when workloads move closer to users, but it is bounded by geography.

Last verified: 2026-08-26

Question 17 clf-cloud-concepts-fundamentals-017

Intermediate · Choose one

A company describes its new AWS architecture as "reliable." Which behavior best demonstrates that claim?

  1. a The workload consistently performs its intended function correctly and recovers automatically from infrastructure disruption
  2. b The workload uses the newest available Amazon EC2 instance generation
  3. c The workload stores every object in at least five AWS Regions
  4. d The workload's monthly cost never increases from one month to the next
Show answer & explanation

Answer: A

Why A is correct

Reliability is the ability of a workload to perform its intended function correctly and consistently when it is expected to, including recovering from infrastructure or service disruptions and dynamically acquiring the resources it needs to meet demand. Automatic recovery, not the absence of failures, is the observable evidence.

Why the others are wrong

  • B — Newer instance generations often improve price and performance, but running modern hardware does not by itself make a workload recover from failure.
  • C — Copying data into five Regions is expensive and rarely justified. Reliability is about meeting stated availability and recovery objectives, not about maximizing replication.
  • D — Flat spending is a cost characteristic. A cheap workload that fails under load is not reliable, and an elastic workload's bill will legitimately rise with demand.

Last verified: 2026-08-26

Question 18 clf-cloud-concepts-fundamentals-018

Intermediate · Choose one

A team argues that because its application runs on AWS, it no longer needs to design for failure. Which response is correct?

  1. a Correct, because AWS guarantees that no individual component will ever fail
  2. b Incorrect, but only for workloads that use Amazon EC2, since managed services never fail
  3. c Incorrect, because the customer is responsible for architecting resilience into the workload, for example by spreading it across multiple Availability Zones
  4. d Correct, because every AWS service replicates workloads across Regions by default
Show answer & explanation

Answer: C

Why C is correct

AWS provides resilient building blocks, but assembling them into a resilient workload is the customer's responsibility under the shared responsibility model. A single instance in a single Availability Zone remains a single point of failure regardless of how good the underlying infrastructure is, which is why the design guidance is to distribute across Availability Zones and to recover automatically.

Why the others are wrong

  • A — AWS makes no such guarantee. Hardware, networks, and software fail, and AWS design guidance explicitly tells customers to assume failures will occur.
  • B — Managed services reduce operational work but are not immune to disruption. Service level agreements for services such as Amazon EC2 and Amazon RDS assume a correctly architected consumer, typically across multiple Availability Zones.
  • D — Most AWS services are Regional and do not replicate across Regions by default. For customer workloads and data, cross-Region replication is an explicit customer configuration.

Last verified: 2026-08-26

Question 19 clf-cloud-concepts-fundamentals-019

Hard · Choose one

Which statement correctly distinguishes scalability from elasticity?

  1. a Scalability is the ability of a system to handle growth by adding resources, while elasticity is the automatic addition and removal of those resources as demand changes
  2. b Scalability is a property of managed services, while elasticity is a property of self-managed servers
  3. c Scalability applies only to storage, while elasticity applies only to compute
  4. d Scalability means the system never fails, while elasticity means the system recovers quickly after it fails
Show answer & explanation

Answer: A

Why A is correct

Scalability is a capability: the architecture can grow to handle more work, whether by adding instances horizontally or by moving to larger instances vertically. Elasticity is the dynamic behavior layered on top: capacity is added automatically when demand rises and, crucially, removed when it falls. A system can be scalable without being elastic, for example if scaling requires a manual change.

Why the others are wrong

  • B — Self-managed fleets can be made elastic with automatic scaling, and managed services vary in how they scale. The distinction is behavioral, not service-category based.
  • C — Both concepts apply across compute, storage, databases, and networking. Neither is restricted to one resource type.
  • D — Never failing and recovering after failure describe fault tolerance and high availability. Neither term is about handling changes in load.

Last verified: 2026-08-26

Question 20 clf-cloud-concepts-fundamentals-020

Hard · Choose one

An architecture runs two application servers behind a load balancer in two Availability Zones. If one server fails, the load balancer routes all traffic to the survivor and users see a brief error for in-flight requests before retrying successfully. Which term most precisely describes this behavior?

  1. a High availability, because the service remains available with only minimal disruption
  2. b Elasticity, because capacity changed when the server failed
  3. c Fault tolerance, because no request is ever affected
  4. d Durability, because no data was lost during the failure
Show answer & explanation

Answer: A

Why A is correct

High availability accepts a small, bounded disruption while the system detects the failure and redirects traffic, and it keeps overall downtime minimal. That is exactly what happens here: in-flight requests fail, health checks remove the bad target, and service continues. Fault tolerance would be the stronger claim that no request was affected at all.

Why the others are wrong

  • B — Elasticity is capacity changing in response to demand. Here capacity changed because of a failure, and the surviving fleet was not resized to match load.
  • C — Fault tolerance means the failure is absorbed with no impact on any request. Because in-flight requests errored and had to be retried, the stronger claim does not hold.
  • D — Durability concerns whether stored data survives over time. It is a storage property and does not describe the availability of the compute tier.

Last verified: 2026-08-26

Question 21 clf-cloud-concepts-fundamentals-021

Hard · Choose one

Amazon S3 storage classes are described as designed for 99.999999999 percent durability and for a separate, lower availability figure. Which statement explains why these two numbers differ?

  1. a Durability is a contractual commitment and availability is a marketing estimate, so the two are not comparable
  2. b Durability applies to data at rest and availability applies to data in transit, so they measure different network paths
  3. c Durability describes the likelihood that stored objects are preserved without loss, while availability describes the proportion of time the service can be reached to retrieve them
  4. d Durability is measured per Region and availability is measured per Availability Zone, which produces different scales
Show answer & explanation

Answer: C

Why C is correct

The two measure different risks. Durability answers "will my object still exist and be intact years from now," and is raised by storing redundant copies across multiple devices and, in most storage classes, across multiple Availability Zones. Availability answers "can I reach the service right now," and is affected by transient conditions such as maintenance or network events. Data can be perfectly durable while temporarily unreachable, which is why the availability figure is always the lower of the two.

Why the others are wrong

  • A — Both are published design targets, and availability is additionally backed by a service level agreement. The difference is what each one measures, not how binding it is.
  • B — Both figures describe the stored data and the service that fronts it. Neither is a statement about the encryption or reliability of data while it is moving over the network.
  • D — Neither figure is defined by counting Regions against Availability Zones. Redundancy contributes to both numbers; the distinction remains preservation versus reachability.

Last verified: 2026-08-26

Question 22 clf-cloud-concepts-fundamentals-022

Hard · Choose one

A CIO states that the main value of moving to AWS is "agility." A colleague argues that the main value is "elasticity." Which statement best clarifies the difference between the two claims?

  1. a Agility is about the speed at which the organization can experiment, build, and release, while elasticity is about capacity automatically tracking demand
  2. b Agility is a financial measure and elasticity is a security measure
  3. c They are the same concept described with different words, so both claims are identical
  4. d Agility applies to development environments and elasticity applies to production environments
Show answer & explanation

Answer: A

Why A is correct

Agility is an organizational outcome: because resources appear in minutes and failed experiments cost only the hours they ran, the business can try more ideas and ship more often. Elasticity is a technical behavior: running capacity grows and shrinks with load. Elasticity contributes to agility, but a team can have elastic infrastructure and still release slowly if its processes are the bottleneck.

Why the others are wrong

  • B — Neither is a security measure, and elasticity is not primarily financial, although it has strong cost consequences.
  • C — They are related but distinct. One describes how fast the organization can move; the other describes how running capacity responds to load.
  • D — Both apply in either environment. Production benefits from agility through faster, safer releases, and non-production benefits from elasticity by scaling to zero when idle.

Last verified: 2026-08-26

Question 23 clf-cloud-concepts-fundamentals-023

Hard · Select 2 answers

Which TWO statements about the AWS Cloud value proposition are TRUE? (Choose TWO.)

  1. a The cost and time required to experiment fall significantly, so failed experiments carry a much smaller penalty
  2. b Capacity decisions no longer have to be made far in advance, because resources can be acquired and released as demand changes
  3. c Every workload becomes cheaper on AWS than on premises regardless of how it is architected
  4. d AWS assumes responsibility for the availability of the customer's application code
  5. e Moving to AWS removes the customer's responsibility for securing their own data
Show answer & explanation

Answer: A and B

Why A and B are correct

Two of AWS's stated advantages are captured here. Increased speed and agility means new resources are minutes away, so the cost and time of experimenting drop dramatically and unsuccessful ideas can be abandoned cheaply. Stopping guessing capacity means you access as much or as little capacity as you need and scale up and down with only a few minutes' notice, rather than committing to a size before deployment.

Why the others are wrong

  • C — A workload lifted unchanged onto oversized, always-on instances can easily cost more than it did on premises. Savings follow from rightsizing, elasticity, and the use of managed services.
  • D — AWS is responsible for the availability of its services. Whether the customer's application stays up depends on how the customer architects and operates it.
  • E — Security is a shared responsibility. AWS secures the infrastructure, but data classification, access control, and encryption choices remain with the customer.

Last verified: 2026-08-26

Question 24 clf-cloud-concepts-fundamentals-024

Hard · Choose one

A company that already runs on AWS is deciding whether to build its own custom message queue on Amazon EC2 or to consume a managed queuing service. Which reasoning best reflects the AWS Cloud value proposition?

  1. a Consuming the managed service is preferable because queuing is undifferentiated work, and the engineering effort is better spent on what makes the product distinctive
  2. b Building the queue is preferable because owning the code always reduces long-term cost
  3. c The two options are equivalent, because both run on AWS infrastructure
  4. d Building the queue is preferable because managed services cannot be secured
Show answer & explanation

Answer: A

Why A is correct

A message queue is plumbing: customers do not choose the company's product because of it. AWS's guidance is to stop spending money and effort on undifferentiated heavy lifting and to focus on the projects that differentiate the business. Consuming the managed service also transfers patching, scaling, and availability engineering to AWS.

Why the others are wrong

  • B — Owning code carries ongoing cost in maintenance, on-call burden, security patching, and scaling work. Those costs usually exceed the service charge for commodity infrastructure.
  • C — Running on the same infrastructure does not make the two equivalent. They differ sharply in who carries the operational and availability burden.
  • D — Managed services integrate with identity, encryption, and logging controls, and are frequently easier to secure well than a hand-built equivalent.

Last verified: 2026-08-26

Question 25 clf-cloud-concepts-fundamentals-025

Hard · Select 2 answers

Which TWO characteristics are features of a cloud consumption model that a traditional on-premises model lacks? (Choose TWO.)

  1. a Hardware refresh cycles must be planned and budgeted by the customer every few years
  2. b Resources are provisioned on demand through self-service interfaces without a procurement cycle
  3. c Capacity is procured through a purchase cycle that fixes the size of the environment for years
  4. d Adding capacity in a new country requires a local facility to be commissioned first
  5. e Charges accrue based on the resources actually consumed rather than on owned capacity
Show answer & explanation

Answer: B and E

Why B and E are correct

The two defining shifts are self-service on-demand provisioning, which removes the procurement and installation cycle from the critical path, and consumption-based charging, which replaces the up-front purchase of fixed capacity with a bill that tracks what actually ran. Together they are what AWS means by on-demand delivery of IT resources with pay-as-you-go pricing.

Why the others are wrong

  • A — Refresh planning is an on-premises obligation. On AWS the underlying hardware is refreshed by AWS, and customers migrate to newer instance generations when it suits them.
  • C — A multi-year purchase that fixes environment size is the traditional model. It is the constraint the cloud model removes.
  • D — Commissioning a local facility is the on-premises path. On AWS, a new geography is reached by deploying into an existing Region.

Last verified: 2026-08-26

Question 26 clf-cloud-concepts-fundamentals-026

Easy · Choose one

How many pillars does the AWS Well-Architected Framework contain, and which pillar was added most recently?

  1. a Six pillars, with sustainability added most recently
  2. b Five pillars, with cost optimization added most recently
  3. c Seven pillars, with resilience added most recently
  4. d Four pillars, with security added most recently
Show answer & explanation

Answer: A

Why A is correct

The AWS Well-Architected Framework has six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. Sustainability was introduced in 2021 and is the newest addition, so any material describing "five pillars" predates that change.

Why the others are wrong

  • B — Cost optimization has been one of the original pillars since the framework was published. Five pillars was the count before sustainability was added.
  • C — There is no separate resilience pillar. Resilience concerns are addressed within the reliability pillar.
  • D — Security has always been a pillar, and the framework has never had only four.

Last verified: 2026-08-26

Question 27 clf-cloud-concepts-fundamentals-027

Easy · Choose one

Which Well-Architected pillar covers the ability to support development and run workloads effectively, gain insight into their operations, and continuously improve supporting processes and procedures to deliver business value?

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

Answer: C

Why C is correct

The operational excellence pillar covers how an organization supports development and runs workloads effectively, gains insight into their operation, and continuously improves supporting processes and procedures. Its design principles include performing operations as code, making frequent small reversible changes, refining operations procedures frequently, anticipating failure, and learning from all operational failures.

Why the others are wrong

  • A — Reliability is about a workload performing its intended function correctly and consistently, including recovering from disruption.
  • B — Cost optimization is about delivering business value at the lowest price point, not about operating procedures.
  • D — Performance efficiency is about using computing resources efficiently to meet requirements and maintaining that efficiency as demand and technologies evolve.

Last verified: 2026-08-26

Question 28 clf-cloud-concepts-fundamentals-028

Easy · Choose one

Which Well-Architected pillar is concerned with using computing resources efficiently to meet system requirements and maintaining that efficiency as demand changes and technologies evolve?

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

Answer: C

Why C is correct

The performance efficiency pillar is about using resources efficiently to meet requirements and sustaining that efficiency as demand shifts and technologies advance. Its design principles are to democratize advanced technologies, go global in minutes, use serverless architectures, experiment more often, and consider mechanical sympathy.

Why the others are wrong

  • A — Security covers protecting data, systems, and assets, and using cloud technologies to improve the security posture.
  • B — Operational excellence covers running workloads and improving the processes and procedures around them.
  • D — Sustainability focuses on minimizing the environmental impact of running cloud workloads, which often overlaps with efficiency but is measured against impact rather than performance requirements.

Last verified: 2026-08-26

Question 29 clf-cloud-concepts-fundamentals-029

Easy · Choose one

"Implement a strong identity foundation" and "apply security at all layers" are design principles of which Well-Architected pillar?

  1. a Cost optimization
  2. b Operational excellence
  3. c Reliability
  4. d Security
Show answer & explanation

Answer: D

Why D is correct

Both are design principles of the security pillar. The full set is: implement a strong identity foundation, maintain traceability, apply security at all layers, automate security best practices, protect data in transit and at rest, keep people away from data, and prepare for security events.

Why the others are wrong

  • A — Cost optimization's design principles concern cloud financial management, adopting a consumption model, measuring efficiency, avoiding undifferentiated heavy lifting, and analyzing and attributing expenditure.
  • B — Operational excellence's design principles concern operations as code, small reversible changes, refining procedures, anticipating failure, and learning from failures.
  • C — Reliability's design principles concern automatic recovery from failure, testing recovery procedures, horizontal scaling, stopping guessing capacity, and managing change through automation.

Last verified: 2026-08-26

Question 30 clf-cloud-concepts-fundamentals-030

Easy · Choose one

Which Well-Architected pillar focuses on minimizing the environmental impacts of running cloud workloads?

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

Answer: C

Why C is correct

The sustainability pillar addresses the long-term environmental, economic, and societal impact of a workload and focuses on reducing the resources and therefore the energy required per unit of work. Its design principles include understanding your impact, establishing sustainability goals, maximizing utilization, adopting more efficient hardware and software offerings, using managed services, and reducing the downstream impact of your workloads.

Why the others are wrong

  • A — Reliability is about correct, consistent operation and recovery from disruption.
  • B — Performance efficiency is about meeting performance requirements with the right resources, measured against those requirements rather than against environmental impact.
  • D — Cost optimization targets the lowest price point for the required business value. Sustainable choices often lower cost too, but the pillar is measured in currency rather than in impact.

Last verified: 2026-08-26