Courseiva
Cloud Technology and ServicesmediumMultiple ChoiceObjective-mapped

CLF-C02 Cloud Technology and Services Practice Question

A manufacturing company collects sensor data from thousands of IoT devices every second. The data includes temperature, pressure, and vibration readings. The company needs to store this time-series data and perform real-time queries to detect anomalies, as well as run historical analysis. The data volume is extremely high and will grow continuously. The company wants a fully managed, serverless solution that can automatically scale to handle the data volume and provide built-in analytics functions for time-series. Which AWS service should the company use?

⚠ Common exam trap

Many candidates choose DynamoDB (Option A) because they associate it with high-scale IoT workloads, but they overlook the requirement for built-in time-series analytics functions and automatic tiered storage, which Timestream uniquely provides as a purpose-built time-series database.

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

Amazon Timestream

Amazon Timestream is a fully managed, serverless time-series database service designed specifically for IoT and operational applications. It automatically scales to handle trillions of events per day, provides built-in time-series analytics functions (e.g., smoothing, approximation, interpolation), and supports both real-time queries and historical analysis with separate storage tiers (in-memory for recent data and magnetic for historical data). This makes it the ideal choice for the company's high-volume sensor data requirements.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Amazon DynamoDB

    Why it's wrong here

    Amazon DynamoDB is a fully managed NoSQL database that provides single-digit millisecond latency for key-value and document workloads. While it can store time-series data using techniques like time-to-live and write sharding, it lacks built-in time-series analytics functions and is less optimized for the high-ingestion rates and query patterns typical of IoT sensor data. It is not the best choice for this use case.

    When this WOULD be correct

    A company needs a fully managed NoSQL database for a web application that requires single-digit millisecond latency at any scale, with flexible schema for user profiles and session data, and can handle high traffic with auto-scaling.

  • Amazon Timestream

    Why this is correct

    Amazon Timestream is a purpose-built time-series database that can efficiently ingest, store, and analyze trillions of time-stamped data points per day. It is serverless and auto-scaling, with built-in time-series analytics functions such as interpolation, smoothing, and approximation. This makes it the ideal choice for the company's IoT sensor data requirements.

  • Amazon ElastiCache for Redis

    Why it's wrong here

    Amazon ElastiCache for Redis is an in-memory caching service that provides sub-millisecond latency for caching and session management use cases. It is not designed for persistent storage of large volumes of time-series data, nor does it provide built-in time-series analytics capabilities. It would be an inefficient and costly choice for this workload.

  • Amazon RDS for MySQL

    Why it's wrong here

    Amazon RDS for MySQL is a managed relational database service suitable for traditional transactional workloads. While it can store time-series data, it is not optimized for the extreme write throughput and storage scalability required for thousands of IoT devices generating data every second. Additionally, it lacks specialized time-series query functions and would require significant manual optimization.

    When this WOULD be correct

    A company needs a fully managed relational database for a traditional OLTP application with structured data, ACID transactions, and complex joins, and requires MySQL compatibility for existing applications.

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.

Amazon TimestreamCorrect answer

Why this is correct

Amazon Timestream is a purpose-built time-series database that can efficiently ingest, store, and analyze trillions of time-stamped data points per day. It is serverless and auto-scaling, with built-in time-series analytics functions such as interpolation, smoothing, and approximation. This makes it the ideal choice for the company's IoT sensor data requirements.

Amazon DynamoDBWrong answer — click to see why

Why this is wrong here

DynamoDB is a key-value and document database, not optimized for time-series data. It lacks built-in time-series analytics functions and can become expensive and complex to manage for high-frequency sensor data with continuous growth.

★ When this WOULD be the correct answer

A company needs a fully managed NoSQL database for a web application that requires single-digit millisecond latency at any scale, with flexible schema for user profiles and session data, and can handle high traffic with auto-scaling.

Why candidates choose this

Candidates may think DynamoDB's scalability and serverless nature make it suitable for IoT data, but they overlook that it is not purpose-built for time-series workloads and lacks native time-series functions.

Amazon RDS for MySQLWrong answer — click to see why

Why this is wrong here

Amazon RDS for MySQL is a relational database not optimized for time-series data; it lacks built-in time-series analytics functions and auto-scaling for high-velocity IoT data, requiring manual sharding and indexing.

★ When this WOULD be the correct answer

A company needs a fully managed relational database for a traditional OLTP application with structured data, ACID transactions, and complex joins, and requires MySQL compatibility for existing applications.

Why candidates choose this

Candidates may assume any database can handle time-series data and overlook the specialized requirements, or they may be more familiar with RDS and underestimate the need for a purpose-built service.

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 ClassMin DurationRetrievalUse Case
S3 StandardNoneImmediateFrequently accessed data
S3 Standard-IA30 daysImmediateInfrequent access, rapid retrieval
S3 One Zone-IA30 daysImmediateNon-critical infrequent data
S3 Intelligent-TieringNoneImmediate–hoursUnknown or changing access patterns
S3 Glacier Instant90 daysMillisecondsArchive with instant retrieval
S3 Glacier Flexible90 daysMinutes–hoursArchive, flexible retrieval
S3 Glacier Deep Archive180 daysHoursLong-term compliance archive

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 →

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.