Courseiva
Cloud ConceptsmediumMultiple ChoiceObjective-mapped

CLF-C02 Cloud Concepts Practice Question

A company uses AWS to host its web application. The company's IT manager learns that multiple AWS customers may have virtual machines running on the same physical server within an AWS data center. However, the manager is confident that each customer's data is securely isolated from others and that customers have no visibility into or control over the underlying physical infrastructure. Which essential characteristic of cloud computing does this scenario best demonstrate?

⚠ Common exam trap

It's easy for candidates to confuse resource pooling with multi-tenancy or security isolation, but the exam specifically tests the definition of resource pooling as the provider's ability to serve multiple customers from the same physical infrastructure while maintaining logical separation.

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

Resource pooling

Resource pooling is the correct answer because it describes the cloud characteristic where the provider's computing resources (such as physical servers) are pooled to serve multiple customers using a multi-tenant model. AWS uses hypervisor-based isolation (e.g., Xen or Nitro) to ensure that each customer's virtual machine has no visibility into or control over the underlying physical hardware or other tenants' workloads, while still sharing the same physical server. This directly matches the scenario's description of multiple customers running VMs on the same physical host with secure isolation.

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 quickly provision or release cloud resources, often automatically, to scale outward or inward based on fluctuating demand. The scenario focuses on how the provider's physical hardware is pooled and shared among multiple tenants, not on scaling capacity. Even if demand were constant, the security and multi-tenancy aspects described align with resource pooling, not elasticity.

    When this WOULD be correct

    A question describing a web application that automatically scales its compute capacity from 10 to 100 instances within minutes during a flash sale, then scales back down, would best demonstrate rapid elasticity.

  • Resource pooling

    Why this is correct

    Resource pooling is the cloud characteristic where the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned. The customer generally has no control or knowledge over the exact location of the resources. This matches the scenario exactly.

  • On-demand self-service

    Why it's wrong here

    On-demand self-service means a customer can provision computing capabilities (e.g., servers, storage) as needed automatically without requiring human interaction with the service provider. The scenario does not involve self-provisioning; it is about the underlying shared infrastructure.

    When this WOULD be correct

    A question where a user can provision computing resources (e.g., launch an EC2 instance) through a web portal without contacting AWS support would demonstrate on-demand self-service.

  • Measured service

    Why it's wrong here

    Measured service is the cloud characteristic where a provider meters and monitors resource usage (e.g., compute, storage, bandwidth) to enable transparent billing and pay-as-you-go pricing. The scenario describes multiple customers securely sharing the same physical infrastructure, which is the essence of resource pooling, not usage metering or cost control. Since there is no mention of metering or billing, this option does not match the described situation.

    When this WOULD be correct

    A question that asks which cloud characteristic enables pay-per-use billing, where resource consumption is tracked and charged based on usage metrics, would have measured service as the correct answer.

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.

Resource poolingCorrect answer

Why this is correct

Resource pooling is the cloud characteristic where the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned. The customer generally has no control or knowledge over the exact location of the resources. This matches the scenario exactly.

Rapid elasticityWrong answer — click to see why

Why this is wrong here

Rapid elasticity refers to the ability to quickly scale resources up or down based on demand, not to the sharing of physical infrastructure among multiple customers.

★ When this WOULD be the correct answer

A question describing a web application that automatically scales its compute capacity from 10 to 100 instances within minutes during a flash sale, then scales back down, would best demonstrate rapid elasticity.

Why candidates choose this

Candidates may confuse the concept of multiple customers sharing physical hardware with the idea of rapid scaling, thinking that pooling resources enables quick elasticity, but the question specifically focuses on isolation and lack of visibility into physical infrastructure.

On-demand self-serviceWrong answer — click to see why

Why this is wrong here

The scenario describes multiple customers sharing physical infrastructure with isolation, which is resource pooling, not the ability to provision resources without human interaction.

★ When this WOULD be the correct answer

A question where a user can provision computing resources (e.g., launch an EC2 instance) through a web portal without contacting AWS support would demonstrate on-demand self-service.

Why candidates choose this

Candidates may confuse the ability to independently provision resources with the underlying multi-tenant infrastructure sharing, as both involve user autonomy and cloud benefits.

Measured serviceWrong answer — click to see why

Why this is wrong here

Measured service refers to the metering and billing of cloud resource usage, not to the isolation of customer data on shared physical hardware.

★ When this WOULD be the correct answer

A question that asks which cloud characteristic enables pay-per-use billing, where resource consumption is tracked and charged based on usage metrics, would have measured service as the correct answer.

Why candidates choose this

Candidates may confuse the idea of 'service' with the security isolation provided by the cloud provider, mistakenly thinking that measured service implies some form of separation or control.

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?”

About these practice questions

One of 988 original CLF-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.