CLF-C02 Cloud Concepts Practice Question
A healthcare organization stores sensitive patient records in Amazon S3. The organization's compliance team learns that AWS stores data from multiple customers on the same physical hardware. They are concerned that data from different customers could be mixed or accessed by another customer. Which fundamental characteristic of cloud computing explains how AWS allows customers to share physical infrastructure while keeping each customer's data logically isolated?
⚠ Common exam trap
Many candidates confuse 'resource pooling' with 'multi-tenancy' or assume it means data is physically separated, but the exam tests that resource pooling specifically enables logical isolation through software controls, not physical hardware 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 how AWS aggregates computing resources (including storage) from multiple customers into a shared pool, then logically isolates each customer's data through software-defined boundaries. In Amazon S3, this isolation is achieved via bucket policies, IAM roles, and object ACLs that enforce strict access controls, ensuring that even though physical hardware is shared, no customer can access another's data. This characteristic directly addresses the compliance team's concern about data mixing or unauthorized cross-tenant access.
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 cloud characteristic that lets customers transparently scale resources up or down to match demand, often automatically and within minutes, giving the illusion of unlimited capacity. This dynamic provisioning can move workloads across many underlying physical servers, but the movement does not itself create or enforce the logical separation of stored patient records. The isolation that prevents cross-tenant data exposure is an architectural property of resource pooling, not an outcome of elastic scaling.
When this WOULD be correct
A question asking which cloud characteristic allows a company to automatically add compute capacity during a flash sale and reduce it afterward, without manual intervention.
- ✓
Resource pooling
Why this is correct
Resource pooling allows the provider to serve multiple customers from a shared pool of physical resources while logically isolating each customer's data and workloads. AWS uses multi-tenant architectures and security controls to ensure that one customer cannot access another customer's data, even when stored on the same hardware.
- ✗
On-demand self-service
Why it's wrong here
On-demand self-service describes a customer's ability to provision and configure computing resources—such as EC2 instances or S3 buckets—through a web console or API without needing a human administrator at the provider. This characteristic addresses operational convenience and automation, but says nothing about how a multi-tenant physical infrastructure keeps one customer's sensitive patient records from being accessed by another. The isolation mechanism in question is fundamentally a resource pooling design, not a self-service provisioning feature.
- ✗
Measured service
Why it's wrong here
Measured service refers to the cloud provider metering resource consumption—such as compute hours, storage gigabytes, or network I/O—and billing customers on a pay-as-you-go basis. For metering to be accurate, the provider must track usage across shared physical hardware, but the accounting abstraction does not establish the data-plane isolation needed to keep patient records private. It is a billing and optimization feature, not a security control for separating tenant data on the same hosts.
When this WOULD be correct
A question asking which cloud characteristic enables pay-per-use billing and resource usage tracking, such as 'A company wants to track and optimize its cloud spending based on actual consumption. Which cloud characteristic supports this?'
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 allows the provider to serve multiple customers from a shared pool of physical resources while logically isolating each customer's data and workloads. AWS uses multi-tenant architectures and security controls to ensure that one customer cannot access another customer's data, even when stored on the same hardware.
✗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 logical isolation of customer data on shared physical hardware.
★ When this WOULD be the correct answer
A question asking which cloud characteristic allows a company to automatically add compute capacity during a flash sale and reduce it afterward, without manual intervention.
Why candidates choose this
Candidates may confuse the concept of sharing physical infrastructure with the ability to rapidly adjust resources, thinking that elasticity implies some form of resource sharing.
✗Measured serviceWrong answer — click to see why▾
Why this is wrong here
Measured service refers to the ability to monitor and control resource usage for billing and optimization, not to the logical isolation of customer data on shared physical infrastructure.
★ When this WOULD be the correct answer
A question asking which cloud characteristic enables pay-per-use billing and resource usage tracking, such as 'A company wants to track and optimize its cloud spending based on actual consumption. Which cloud characteristic supports this?'
Why candidates choose this
Candidates may confuse 'measured service' with the idea that AWS measures and separates customer data, but it actually pertains to metering usage for billing, not data isolation.
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?”
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
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 →
Same concept, more angles
1 more way this is tested on CLF-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company uses Amazon EC2 instances to run its workloads. The company's IT team does not know the exact physical server where each instance runs, and instances from multiple customers may be hosted on the same physical hardware. The team only specifies the AWS Region and Availability Zone. Which essential characteristic of cloud computing does this scenario BEST represent?
medium- A.On-demand self-service
- ✓ B.Resource pooling
- C.Rapid elasticity
- D.Measured service
Why B: Resource pooling is the correct answer because the scenario describes how AWS aggregates compute resources from multiple physical hosts into a shared pool, which is then dynamically assigned and reassigned to customers based on demand. The IT team has no control over or knowledge of the exact physical server, and instances from different customers can run on the same hardware, which is the defining behavior of resource pooling as defined by NIST SP 800-145.
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.