- A
Durability
Why wrong: Durability refers to data persistence and protection from loss — not the ability to dynamically scale and pay per use.
- B
Elasticity and pay-as-you-go pricing
Elasticity enables scaling from 10 to 1,000 servers on demand; pay-as-you-go ensures billing only for actual server-hours consumed — eliminating waste from idle capacity.
- C
Multi-tenancy
Why wrong: Multi-tenancy describes multiple customers sharing infrastructure — it's an architectural characteristic, not the scaling and billing model.
- D
Service Level Agreement (SLA)
Why wrong: SLAs define uptime commitments — they're not the billing or scaling model described.
Quick Answer
The correct answer is elasticity combined with pay-as-you-go pricing. Elasticity is the cloud characteristic that automatically provisions and de-provisions resources to match fluctuating demand, allowing you to scale from 10 servers to 1,000 and back without manual intervention. Pay-as-you-go pricing then ensures you are billed only for the compute hours actually consumed during each period, making the experimental and production workloads cost-effective. On the AWS Certified Cloud Practitioner CLF-C02 exam, this scenario tests your understanding of how elasticity and consumption-based billing work together as distinct cloud advantages—a common trap is confusing elasticity with simple scalability, which lacks the automatic scaling and de-scaling component. Remember the memory tip: elasticity handles the “how much and when,” while pay-as-you-go handles the “how much you pay.”
CLF-C02 Cloud Concepts Practice Question
This CLF-C02 practice question tests your understanding of cloud concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A startup is evaluating cloud vs. on-premises for their new product. Which cloud characteristic means they can experiment with 10 servers for a week, then scale to 1,000 servers for a product launch, and back to 10 afterward — paying only for what they use?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Elasticity and pay-as-you-go pricing
Elasticity is the cloud characteristic that allows resources to automatically scale up or down based on demand, while pay-as-you-go pricing ensures you only incur costs for resources actually consumed. In this scenario, the startup can provision 10 servers for a week, scale to 1,000 servers for a launch, and then scale back to 10 — paying only for the compute hours used during each period. This combination of rapid scaling and consumption-based billing is unique to cloud computing and directly supports the described experimental and production workloads.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Durability
Why it's wrong here
Durability refers to data persistence and protection from loss — not the ability to dynamically scale and pay per use.
- ✓
Elasticity and pay-as-you-go pricing
Why this is correct
Elasticity enables scaling from 10 to 1,000 servers on demand; pay-as-you-go ensures billing only for actual server-hours consumed — eliminating waste from idle capacity.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Multi-tenancy
Why it's wrong here
Multi-tenancy describes multiple customers sharing infrastructure — it's an architectural characteristic, not the scaling and billing model.
- ✗
Service Level Agreement (SLA)
Why it's wrong here
SLAs define uptime commitments — they're not the billing or scaling model described.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse elasticity with durability or high availability, mistakenly thinking that data persistence or uptime guarantees enable scaling, when in fact elasticity is specifically about dynamic resource adjustment and pay-as-you-go is about cost alignment.
Detailed technical explanation
How to think about this question
Under the hood, elasticity is powered by orchestration services like AWS Auto Scaling, which uses CloudWatch metrics and scaling policies to add or remove EC2 instances via launch templates. Pay-as-you-go billing is tracked per resource at a granular level (e.g., per-second billing for EC2 instances launched after October 2, 2017), ensuring costs align exactly with usage. A real-world scenario: a startup running a viral marketing campaign can use a target tracking scaling policy to automatically add 100 servers within minutes when CPU utilization exceeds 70%, then scale back to 10 servers after the campaign ends — all without manual intervention or upfront commitments.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Cloud Concepts — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Concepts practice questions
Targeted practice on this topic area only
- →
All CLF-C02 questions
1,024 questions across all exam domains
- →
AWS Certified Cloud Practitioner CLF-C02 study guide
Full concept coverage aligned to exam objectives
- →
CLF-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CLF-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cloud Concepts practice questions
Practise CLF-C02 questions linked to Cloud Concepts.
Security and Compliance practice questions
Practise CLF-C02 questions linked to Security and Compliance.
Cloud Technology and Services practice questions
Practise CLF-C02 questions linked to Cloud Technology and Services.
Billing, Pricing, and Support practice questions
Practise CLF-C02 questions linked to Billing, Pricing, and Support.
AWS shared responsibility model practice questions
Practise CLF-C02 questions linked to AWS shared responsibility model.
AWS IAM practice questions
Practise CLF-C02 questions linked to AWS IAM.
AWS pricing practice questions
Practise CLF-C02 questions linked to AWS pricing.
AWS support plans practice questions
Practise CLF-C02 questions linked to AWS support plans.
AWS S3 practice questions
Practise CLF-C02 questions linked to AWS S3.
AWS EC2 practice questions
Practise CLF-C02 questions linked to AWS EC2.
Practice this exam
Start a free CLF-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CLF-C02 question test?
Cloud Concepts — This question tests Cloud Concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Elasticity and pay-as-you-go pricing — Elasticity is the cloud characteristic that allows resources to automatically scale up or down based on demand, while pay-as-you-go pricing ensures you only incur costs for resources actually consumed. In this scenario, the startup can provision 10 servers for a week, scale to 1,000 servers for a launch, and then scale back to 10 — paying only for the compute hours used during each period. This combination of rapid scaling and consumption-based billing is unique to cloud computing and directly supports the described experimental and production workloads.
What should I do if I get this CLF-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This CLF-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CLF-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.