Infrastructure as code, in one service. Six questions on templates, stacks and what CloudFormation is for — CLF-C02, 2026 edition.
Try 6 free AWS CloudFormation questions in the exam's own style — every answer explained, no sign-up.
Straight to the 6 free questions ↓CloudFormation is the exam’s answer whenever a question is about infrastructure as code: describing your AWS resources in a file and letting AWS provision them for you. It is a small concept at this level, and it comes up reliably in the largest domain.
AWS CloudFormation lets you define your infrastructure in a template — a text file in YAML or JSON — and it creates those resources for you. The group of resources created from one template is a stack, managed together: create, update or delete the whole set in one action. Because the infrastructure is code, you can deploy it repeatably and consistently across accounts and Regions, and rebuild it exactly if you ever need to.
The benefit the exam tests is repeatability, not speed or cost. Building resources by hand in the console is fine once; doing it identically ten times, or recreating an environment after a mistake, is where a template wins. Any option claiming CloudFormation makes applications faster, makes resources free, or encrypts data automatically is a distractor — it provisions infrastructure, nothing more.
CloudFormation is often confused with Elastic Beanstalk:
Provision infrastructure, versus run an application. If a question is about defining resources as code, it is CloudFormation; if it is about deploying an app without managing the platform, it is Beanstalk.
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 here are usually other services offered where infrastructure-as-code belongs, or an overstated benefit. Recognising “define infrastructure as a template” as CloudFormation is the whole skill, and the reasoning below drills it. For the wider picture, see the cheat sheet.
What does AWS CloudFormation let you do?
CloudFormation is infrastructure as code: you describe the resources you want in a template and it provisions them for you. Why not the others: running virtual servers is EC2, object storage is S3, and sending email is SES. CloudFormation is about defining infrastructure, not being any single one of those resources.
In what format is a CloudFormation template written?
CloudFormation templates are text files written in YAML or JSON, which makes them easy to version-control and review. Why not the others: templates are not compiled binaries or spreadsheets, and they follow a defined structure, not free-form prose. Human-readable YAML or JSON is the format.
In CloudFormation, what is a 'stack'?
A stack is the set of resources CloudFormation creates from one template and manages as a single unit — create, update or delete them together. Why not the others: a single instance is one resource inside a stack, not the stack itself. A billing report and a storage volume are unrelated. The stack is the managed group.
What is a key benefit of using CloudFormation over creating resources by hand in the console?
Because the infrastructure is defined as code, you can deploy it the same way every time, in any account or Region, and rebuild it exactly if needed. Why not the others: CloudFormation does not speed up applications, does not make resources free (you still pay for what it creates), and does not automatically encrypt data. Repeatable, consistent provisioning is the benefit.
What happens to the resources in a CloudFormation stack when you delete the stack?
Deleting a stack tells CloudFormation to remove the resources it provisioned, cleaning up in one action (some resources can be set to retain, but the default is to delete). Why not the others: resources are not kept forever, it is not only the template that goes, and nothing is moved to another account. Managing resources as a group — including teardown — is the point of a stack.
How does CloudFormation differ from AWS Elastic Beanstalk?
CloudFormation is a general infrastructure-as-code tool — it can build almost any set of AWS resources. Elastic Beanstalk is a platform that takes your application and runs it, handling the servers, scaling and load balancing. Why not the others: they are distinct, CloudFormation does not run your app code itself, and neither is a database. Provision infrastructure versus run an application is the difference.
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 →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
Practising with a system
Straight into the player. No account, no email.
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.