Best Primary Ingestion Service for Real-Time IoT Data
A company wants to ingest data from thousands of IoT devices into AWS for real-time analytics. The data is in JSON format and each device sends about 1 KB every second. Which service should be used as the primary ingestion point?
Quick Answer
The answer is Amazon Kinesis Data Streams, as it serves as the primary ingestion point for real-time IoT streaming data due to its ability to handle high-throughput, low-latency data from thousands of devices. Each device sends 1 KB of JSON per second, and Kinesis Data Streams can ingest and persist this data durably while allowing multiple consumer applications to process it concurrently for real-time analytics. On the AWS Certified Data Engineer Associate DEA-C01 exam, this question tests your understanding of streaming ingestion patterns versus message queuing or delivery services; a common trap is choosing Amazon SQS for its simplicity, but SQS is designed for decoupled message queues, not for real-time streaming with multiple consumers. Another pitfall is Amazon Kinesis Data Firehose, which lacks native support for multiple real-time consumers and is better suited for near-real-time loading into data stores. Remember the memory tip: “Streams for streams, Firehose for stores”—Kinesis Data Streams is the durable, replayable pipeline for live data, while Firehose delivers to destinations.
⚠ Common exam trap
Confusing the purpose of Kinesis Data Streams (real-time ingestion with multiple consumers) vs. Kinesis Data Firehose (delivery to storage with latency) is common. Also, remember that AWS IoT Core is a device gateway, not a data ingestion service for analytics.
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 Kinesis Data Streams
Amazon Kinesis Data Streams (D) is the correct choice because it is designed for real-time streaming of large amounts of data from many producers, such as thousands of IoT devices. Each device sends 1 KB per second, resulting in ~1 MB/s total throughput, which Kinesis Data Streams can handle with sharding. It supports multiple consumers for real-time analytics. AWS IoT Core (A) is for device management and MQTT messaging, not a general-purpose ingestion point for analytics. Kinesis Data Firehose (B) is for loading streaming data into storage, but it does not support multiple real-time consumers and has a minimum 60-second buffer latency. Amazon SQS (C) is a message queue for decoupled applications, not built for high-throughput streaming analytics.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
AWS IoT Core
Why it's wrong here
IoT-specific, but Kinesis is more general.
- ✗
Amazon Kinesis Data Firehose
Why it's wrong here
Kinesis Data Firehose is a near-real-time delivery stream that batches and loads data into destinations like S3 or Redshift, but it lacks the sub-second latency and per-record processing required for real-time analytics on 1 KB per second per device; the correct service, Kinesis Data Streams, provides millisecond-level ingestion with custom consumer applications. It is tempting because Firehose simplifies data loading into storage and analytics services, and would be correct if the requirement were for batch-oriented ingestion with minimal transformation, not low-latency streaming.
- ✗
Amazon SQS
Why it's wrong here
Not designed for real-time streaming analytics.
- ✓
Amazon Kinesis Data Streams
Why this is correct
Handles high-volume streaming data.
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 1,711 original DEA-C01 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 DEA-C01
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 wants to ingest streaming data from thousands of IoT devices into AWS for real-time analytics. Which AWS service is best suited for this purpose?
easy- A.Amazon S3
- B.AWS Lambda
- C.Amazon RDS
- ✓ D.Amazon Kinesis Data Streams
Why D: Amazon Kinesis Data Streams is purpose-built for ingesting and processing streaming data at scale from thousands of sources. It can capture and store terabytes of data per hour from IoT devices, enabling real-time analytics with millisecond latencies. The service provides durable, ordered data streams that can be consumed by multiple applications simultaneously.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DEA-C01 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 DEA-C01 exam.