CLF-C02 Storage and Database Services Guide

Study CLF-C02 Storage and Database Services: key concepts, common traps, and exam decision cues.

Storage and database questions are high yield on CLF-C02 because they reward simple classification discipline. You do not need expert tuning knowledge. You do need to know whether the requirement is for object, block, file, backup, relational, or NoSQL service shapes.

Object storage: Storage model for objects and metadata, not for attached instance disks.

Block storage: Disk-style storage presented to a host, such as an EC2 instance.

Relational database: Database model organized around structured tables and relationships.

What AWS is really testing here

AWS wants you to separate:

  • object, block, and file storage
  • storage choice from backup-management choice
  • relational database needs from NoSQL needs
  • storage durability questions from data-migration questions

Storage chooser

Need Strongest first fit Why
durable object storage Amazon S3 This is the object-storage lane.
block storage attached to an EC2 instance Amazon EBS This is the attached-disk lane.
managed shared file system Amazon EFS or Amazon FSx This is the file-storage lane for shared access.
centralized backup management across supported services AWS Backup This is the backup-management lane, not a raw storage type.
hybrid cached or on-premises file-storage integration AWS Storage Gateway This is the hybrid storage bridge lane.

S3 vs EBS vs EFS

This is one of the most important CLF-C02 service-family distinctions.

If the requirement is mainly about… Think first about…
storing objects durably S3
a disk attached to one EC2 instance EBS
a managed shared file system used by multiple systems EFS or FSx

If the question is about an instance boot disk or attached storage volume, S3 is usually the wrong first answer. If it is about durable object storage, EBS is usually the wrong first answer.

Storage management and cost basics

CLF-C02 also uses storage questions to test simple management and cost logic:

  • S3 storage classes match different access patterns
  • lifecycle policies move or expire objects over time
  • AWS Backup centralizes backup operations across supported services

Those are often better answers than raw storage type changes when the question is really about management or cost optimization.

Database chooser

Need Strongest first fit Why
managed relational database Amazon RDS or Amazon Aurora The workload needs a relational engine.
NoSQL key-value or document-style workload Amazon DynamoDB This is the managed NoSQL lane.
move a database into AWS AWS DMS and sometimes AWS SCT This is the database migration lane.

At the Cloud Practitioner level, the important distinction is not one advanced engine detail. It is whether the workload is relational or NoSQL.

Common traps

Trap Better thinking
“S3 stores data, so it can replace attached instance storage.” S3 is object storage, not instance-attached block storage.
“EFS and EBS are basically the same.” EBS is attached block storage; EFS is a managed shared file system.
“DynamoDB is just AWS’s relational database option.” DynamoDB is the managed NoSQL lane.
“Lifecycle and backup are storage types.” They are management capabilities, not raw storage shapes.

Sample exam question

An application needs a persistent disk attached directly to an EC2 instance. Which AWS service is strongest first?

  1. Amazon S3
  2. Amazon EBS
  3. Amazon Route 53
  4. AWS Config

Correct answer: 2

Why: The requirement is for attached block storage on an EC2 instance, which is exactly the EBS lane.

Decision order that usually wins

  1. Ask whether the requirement is object, block, file, backup, relational, or NoSQL.
  2. If the stem says durable object storage, think S3.
  3. If it says attached disk for EC2, think EBS.
  4. If it says shared managed file system, think EFS or FSx.
  5. If it is a database question, separate relational from NoSQL before choosing the service.

Quiz

Loading quiz…
Revised on Monday, June 15, 2026