CLF-C02 Cloud Concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Rapid elasticity

  Why it's wrong here

  Rapid elasticity is the ability to scale cloud resources out or in quickly, often automatically, to match current demand—for example, an AWS Auto Scaling group adding or removing EC2 instances based on CPU utilization. While this lets workloads expand dynamically after resources are provisioned, it does not describe the initial act of provisioning a server at all. Elasticity focuses on adjusting capacity in response to fluctuating load, whereas on-demand self-service is about the user's power to create resources without waiting for provider staff—two distinct capabilities that are commonly conflated.

  When this WOULD be correct

  A company experiences unpredictable spikes in traffic and needs its application to automatically add or remove compute instances within minutes to handle the load. The question would ask: 'Which cloud characteristic allows resources to be scaled up and down rapidly based on demand?'

• ✓

  On-demand self-service

  Why this is correct

  On-demand self-service is the NIST essential characteristic that lets a consumer unilaterally provision computing resources, such as EC2 virtual servers, through a web console or API without requiring a service desk ticket or human approval from the provider. In AWS, this capability is what allows developers to spin up instances immediately, paying only for what they use, and it directly answers the question's premise about provisioning without human interaction.

• ✗

  Resource pooling

  Why it's wrong here

  Resource pooling refers to the provider's computing resources being aggregated into a multi-tenant pool that is dynamically assigned and reassigned to consumers based on demand, supporting economies of scale and location independence (e.g., AWS regions and Availability Zones). This characteristic is about how the provider shares resources behind the scenes, not about a user's ability to initiate provisioning. A consumer has no control over which physical hosts serve their workloads, and the mere pooling of resources does not give developers a self-service mechanism to create virtual servers.

  When this WOULD be correct

  A question describing how a cloud provider serves multiple customers from the same physical infrastructure, with resources dynamically allocated and reallocated based on demand, would make resource pooling the correct answer. For example: 'A cloud provider uses shared servers to host multiple customers' workloads, automatically adjusting resource allocation as usage fluctuates.'

• ✗

  Measured service

  Why it's wrong here

  Incorrect. Measured service means cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth). It is about billing and monitoring, not self-provisioning.

  When this WOULD be correct

  A company needs to track and optimize cloud resource usage across departments, with detailed billing reports showing each team's consumption of compute, storage, and bandwidth. Measured service would be the correct answer because it describes the metering and pay-per-use billing model.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”