Match each AWS storage service to its description.
Drag a concept onto its matching description — or click a concept then click the description.
Object storage for any data
Block storage for EC2 instances
File storage for multiple EC2 instances
Low-cost archival storage
Hybrid cloud storage integration
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
S3: Object storage for storing and retrieving any amount of data from anywhere.
Each AWS storage service is designed for specific use cases: S3 for object storage, EBS for block storage attached to EC2, EFS for file storage shared across instances, and Glacier for archival.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
S3: Object storage for storing and retrieving any amount of data from anywhere.
Why this is correct
Amazon S3 is a fully managed object storage service that stores data as objects within buckets, using a unique key to retrieve each object via REST APIs over HTTP(S). It is designed for 99.999999999% durability and 99.99% availability, scaling automatically to store and retrieve any amount of data from anywhere on the internet. S3 is ideal for static website hosting, backup, data lakes, and cloud-native applications, and it integrates with lifecycle policies to transition data to colder tiers.
EBS: Block storage volumes for use with EC2 instances.
Why this is correct
Amazon EBS provides persistent block-level storage volumes that you attach to a single EC2 instance in the same Availability Zone. These volumes offer low-latency performance, are provisioned with a specific capacity and IOPS, and survive instance termination unless explicitly deleted. EBS supports snapshots to Amazon S3 for backup and can be used as root volumes or for database workloads requiring durable, high-throughput storage.
EFS: File storage for use with EC2 instances, scalable and elastic.
Why this is correct
Amazon EFS provides a fully managed, elastic, POSIX-compliant file system that can be mounted concurrently on multiple EC2 instances across different Availability Zones using NFS. Storage capacity grows and shrinks automatically as you add or remove files, so you pay only for what you use, with no pre-provisioning. EFS is designed for workloads that require shared file access, such as content management systems, web serving, or analytics pipelines, where multiple instances need consistent file visibility.
Glacier: Low-cost archival storage for data that is accessed infrequently.
Why this is correct
Amazon S3 Glacier is a low-cost archival storage class for data that is accessed infrequently and must be retained for long periods, often years. Retrieval options—Expedited, Standard, and Bulk—allow you to balance cost and speed, with retrieval times ranging from minutes to hours. Because of its very low per-GB cost, Glacier is used for compliance archives, digital preservation, and disaster recovery backups where immediate access is not required.
S3: Block storage volumes for use with EC2 instances.
Why it's wrong here
This pairing is incorrect because S3 is object storage, not block storage. Block storage, such as EBS, provides raw block devices that are attached to a single EC2 instance and appear as a mounted disk, requiring the instance's operating system to format and manage a file system. In contrast, S3 stores complete objects in containers called buckets and is accessed over HTTP APIs; it cannot be attached to an EC2 instance as a volume and is not block-level storage at all.
EBS: Object storage for storing and retrieving any amount of data from anywhere.
Why it's wrong here
This pairing is incorrect because EBS is block storage, not object storage. EBS volumes are network-attached disks that must be mounted to an EC2 instance within the same Availability Zone, and they are accessed through the instance's operating system as raw block devices. Unlike S3, EBS does not provide a globally accessible HTTP API for storing and retrieving arbitrary data from anywhere; instead, it offers sub-millisecond latency storage for a single attached compute instance.
Quick reference
| 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
About these practice questions
This CLF-C02 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
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.