Free CLF-C02 practice questions: Auto Scaling & load balancing

The pair that makes an app elastic and available — scale with demand, route around failure. Seven questions, CLF-C02, 2026 edition.

Try 7 free Auto Scaling and load balancing questions in the exam's own style — every answer explained, no sign-up.

Straight to the 7 free questions ↓

Auto Scaling and Elastic Load Balancing are a pair, and the exam tests them as one idea: making an application elastic (capacity follows demand) and highly available (it survives failures). Learn what each does and how they combine, and this is reliable scoring in the biggest domain.

Two jobs, one goal

EC2 Auto Scaling manages how many instances you run, adding them under load and removing them when demand falls. This gives elasticity and a real cost benefit: you pay only for the capacity you actually need, not for idle over-provisioned servers.
Elastic Load Balancing (ELB) distributes incoming traffic across the instances, and performs health checks — when an instance fails one, the load balancer simply stops routing to it and uses the healthy ones.

Auto Scaling changes the size of the fleet; the load balancer spreads traffic across it. Neither does the other’s job, and the exam likes to reverse them in a distractor.

Why they give high availability

Put the instances in an Auto Scaling group spread across multiple Availability Zones, behind a load balancer, and the failure of an instance — or an entire zone — no longer takes the application down. Traffic routes to healthy instances elsewhere. That is high availability, built from ordinary parts.

Horizontal vs vertical scaling

One concept underneath: Auto Scaling adds more instances (horizontal scaling, or scaling out), rather than making a single instance bigger (vertical scaling, or scaling up). The cloud generally favours scaling out, because many smaller instances behind a load balancer are both elastic and resilient.

How to use the questions below

Answer each one before you reveal the explanation, and when you miss, read past the correct letter to why the other three fail. The distractors usually swap the two roles, or claim a benefit (cost, encryption) that belongs elsewhere. Keeping “scale the fleet” and “balance the traffic” distinct is the whole skill, and the reasoning below drills it. This pairs naturally with Route 53 for routing at the DNS level.

Elastic Load Balancing distributing incoming traffic across an Auto Scaling group of EC2 instances spread over multiple Availability Zones; Auto Scaling adds instances when demand rises and removes them when it falls, and the load balancer routes only to healthy instances.

7 free CLF-C02 practice questions

Answers and explanations — no email wall

CLF-C02 Question 1 of 7

What does a load balancer do when one of its target instances fails a health check?

Answer: A — It stops sending traffic to that instance and routes requests to the healthy ones

A load balancer performs health checks and simply stops routing to any instance that fails, sending requests only to healthy ones. Why not the others: deleting or replacing instances is the job of Auto Scaling, not the load balancer. And it does not keep sending traffic to a failed instance — that is the whole point of health checks. Route around the unhealthy, do not manage its lifecycle.

CLF-C02 Question 2 of 7

What is the cost benefit of EC2 Auto Scaling?

Answer: A — You run only as many instances as demand needs, so you do not pay for idle over-provisioned capacity

Auto Scaling matches capacity to demand — adding instances under load and removing them when idle — so you are not paying for servers you do not need. Why not the others: instances are not free, Auto Scaling deliberately changes the number rather than fixing it, and it has nothing to do with storage cost. Paying only for the capacity you use is the benefit.

CLF-C02 Question 3 of 7

How do EC2 Auto Scaling and a load balancer work together?

Answer: A — Auto Scaling adds or removes instances with demand, and the load balancer distributes incoming traffic across whatever instances are currently running

They are complementary: Auto Scaling manages how many instances exist, and the load balancer spreads traffic across them. Why not the others: the roles are not reversed — the load balancer does not change instance counts, and Auto Scaling does not route traffic. They do different jobs, and both are used together. Scale the fleet, balance the traffic.

CLF-C02 Question 4 of 7

What is an Auto Scaling group?

Answer: A — A collection of EC2 instances managed together for scaling, with a minimum, maximum and desired capacity

An Auto Scaling group is the set of instances Auto Scaling manages, bounded by minimum, maximum and desired capacity settings. Why not the others: a bucket is S3, a load balancer is a separate component, and a private network is a VPC. The group is the managed fleet whose size Auto Scaling adjusts.

CLF-C02 Question 5 of 7

Together, Auto Scaling and a load balancer primarily provide which two benefits?

Answer: A — Elasticity and high availability

Auto Scaling gives elasticity (capacity follows demand) and, with a load balancer spreading traffic across healthy instances in multiple zones, high availability. Why not the others: encryption and compliance are security concerns, global latency is addressed by CloudFront and Route 53, and backups are a separate service. Elasticity plus availability is the pairing's purpose.

CLF-C02 Question 6 of 7

How does placing instances behind a load balancer across multiple Availability Zones help?

Answer: A — If an instance or an entire Availability Zone fails, traffic is routed to healthy instances in the other zones

Spreading instances across Availability Zones behind a load balancer means the failure of one instance or one zone does not take the application down — traffic simply goes elsewhere. Why not the others: this is about availability, not cost or encryption, and you still need instances to serve the traffic. Surviving a zone failure is the benefit.

CLF-C02 Question 7 of 7

Auto Scaling adds more instances to handle load rather than making a single instance bigger. What is this approach called?

Answer: A — Horizontal scaling (scaling out)

Adding more instances to share the load is horizontal scaling, or scaling out — the model Auto Scaling uses. Why not the others: making a single instance larger is vertical scaling (scaling up), a different approach. Encryption and archiving are unrelated. More instances, not bigger ones, is horizontal scaling.

That is exactly how every question in the course works — answer, explanation, why-not. The real set continues in the practice player: 10 free questions, no sign-up.

Continue with the 10 free questions →

Those 7 questions were the start.

The exam does not test whether you recognise a term — it tests whether you can rule out three plausible answers under time pressure. That is what the explanations above are for, and there are 390 more questions built exactly like them.

Collecting questions yourself

Scattered across forums, of unknown age
Answer keys without reasoning
No idea which domain you are weak in

Practising with a system

390 questions in 6 full tests, CLF-C02 (2026)
Every option explained — including the wrong ones
Readiness per exam domain, and drills for your weakest

Start free — 10 questions

Straight into the player. No account, no email.

Frequently asked questions

Is this the current CLF-C02 format?

Yes — these questions follow the CLF-C02 exam guide (2026 edition). Auto Scaling and Elastic Load Balancing sit in the Cloud Technology and Services domain, the largest on the exam at 34%, and the elasticity-and-availability idea appears throughout it.

Are these real exam questions?

No. They are our own questions, written in the style and difficulty of the exam. Reproducing real exam items violates the AWS certification agreement and can get your certification revoked, and a memorised item teaches you nothing about the one you have not seen.

Do I need to configure a scaling policy for the exam?

No. CLF-C02 tests what Auto Scaling and load balancing do, how they work together, and the benefits they provide — elasticity and availability. You will not set up a policy in the exam; you will recognise where the pair belongs.

What is the one-line summary?

Auto Scaling changes how many instances you run to match demand; the load balancer spreads traffic across them and routes around failures. Together they give elasticity and high availability.

Updated for CLF-C02 (July 2026). The sample questions above are our own work in the style of the exam — not real exam items. The exam itself is set and marked by the certification body.