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 common on CLF-C02 because they reward classification skill. You do not need expert tuning knowledge. You do need to know which storage or database shape matches the workload.

Storage chooser

Need Strongest first fit
Durable object storage Amazon S3
Block storage for an EC2 instance Amazon EBS
Managed shared file system Amazon EFS or Amazon FSx
Hybrid cached file access AWS Storage Gateway
Backup across services AWS Backup

The main CLF-C02 habit is not to mix object, block, and file storage.

S3 basics that matter

CLF-C02 often expects you to know that Amazon S3 is:

  • object storage
  • highly durable
  • useful for a wide range of data storage patterns
  • paired with storage classes and lifecycle policies for cost alignment

If the question is about files for one EC2 instance’s attached disk, S3 is often not the first answer. If the question is about durable object storage, it often is.

Database chooser

Need Strongest first fit
Managed relational database Amazon RDS or Amazon Aurora
NoSQL key-value style workload Amazon DynamoDB
In-memory performance use case Memory-based database services such as MemoryDB
Move a database into AWS AWS DMS and sometimes AWS SCT

At a fundamentals level, the important distinction is usually relational versus NoSQL versus memory-based, not one advanced engine detail.

Lifecycle, backup, and storage-class thinking

CLF-C02 also uses storage questions to test cost awareness:

  • lifecycle policies help move or expire data by rule
  • storage classes support different access patterns and cost profiles
  • AWS Backup centralizes backup management across supported services

Decision order that usually wins

Use this order before choosing a storage or database answer:

  1. Decide whether the requirement is object, block, file, backup, relational, or NoSQL.
  2. If the stem says durable object storage, think Amazon S3 before anything attached to an instance.
  3. If the stem says disk attached to EC2, think Amazon EBS.
  4. If many systems need a managed shared file system, think Amazon EFS or FSx.
  5. For databases, separate relational workloads from key-value/document workloads before choosing RDS/Aurora or DynamoDB.

Common traps

  • choosing EBS when the stem wants durable object storage
  • treating EFS and EBS as the same thing
  • confusing DynamoDB with a managed relational database
  • forgetting backup and lifecycle tools when the question is really about management rather than raw storage type

Quiz

Loading quiz…
Revised on Sunday, May 10, 2026