Choosing Kinesis Data Analytics for Real-Time Stream Processing
A company is building a new data analytics platform on AWS. The platform ingests streaming data from multiple sources, processes it in real time, and stores the results in Amazon S3 for later analysis. The data volume is expected to be up to 50 GB per day. The company needs to choose a service for real-time stream processing. Which AWS service is most appropriate for this use case?
Quick Answer
The answer is Amazon Kinesis Data Analytics, as it is purpose-built for real-time stream processing with SQL or Apache Flink, directly matching the need to transform streaming data on the fly before landing results in Amazon S3. Unlike Kinesis Data Streams, which only ingests raw data, or Kinesis Data Firehose, which simply loads data into destinations without processing logic, Kinesis Data Analytics allows you to run continuous queries and stateful computations against live streams. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this question tests your ability to distinguish between the Kinesis family services based on their specific roles in a streaming pipeline—a common trap is confusing ingestion (Data Streams) or delivery (Firehose) with actual processing. Remember the memory tip: “Analytics does the thinking, Streams does the drinking, Firehose does the sinking.”
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 Analytics
Amazon Kinesis Data Analytics is the most appropriate service for real-time stream processing because it allows you to process streaming data in real time using SQL or Apache Flink. Option A (Amazon Kinesis Data Firehose) is designed for loading streaming data into data stores like S3, not for real-time processing. Option B (Amazon Kinesis Data Streams) is a data ingestion service that captures and stores data streams, but does not provide built-in processing capabilities. Option D (Amazon EMR) is primarily used for batch processing of large data sets using frameworks like Hadoop and Spark, and is not optimized for real-time stream processing.
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 Kinesis Data Firehose
Why it's wrong here
Firehose loads data into destinations; it does not perform real-time processing.
- ✗
Amazon Kinesis Data Streams
Why it's wrong here
Data Streams ingests data but does not process it; you need a consumer.
- ✓
Amazon Kinesis Data Analytics
Why this is correct
Kinesis Data Analytics processes streaming data in real time.
- ✗
Amazon EMR
Why it's wrong here
EMR is for batch processing, not real-time streaming.
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,660 original SAP-C02 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
7 more ways this is tested on SAP-C02
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 data analytics company is building a real-time streaming pipeline using Amazon Kinesis Data Streams. The data is consumed by multiple consumer applications, each with different processing requirements. The company wants to ensure that each consumer can process records independently without affecting others and can reprocess data from a specific point in time. Which feature should the company use?
medium- ✓ A.Use Enhanced Fan-Out with a timestamp to start reading.
- B.Increase the data retention period to 365 days.
- C.Use resharding to increase the number of shards.
- D.Use the Kinesis Client Library (KCL) with checkpointing.
Why A: Enhanced Fan-Out (EFO) provides each consumer with a dedicated 2 MB/second read throughput per shard, ensuring independent processing without contention. By using the SubscribeToShard API with a starting position specified via a timestamp, consumers can reprocess data from a specific point in time, meeting the requirement exactly.
Variation 2. A company is designing a real-time analytics pipeline for IoT data. They need to ingest millions of messages per second, process them with low latency, and store results in Amazon S3. Which combination of services should they use?
medium- ✓ A.Amazon Kinesis Data Streams, Amazon Kinesis Data Analytics, Amazon Kinesis Data Firehose
- B.Amazon SQS, AWS Lambda, Amazon S3
- C.Amazon Kinesis Data Streams, Amazon Redshift, Amazon S3
- D.Amazon IoT Core, AWS Lambda, Amazon DynamoDB
Why A: Kinesis Data Streams ingests high-throughput data, Kinesis Data Analytics processes it in real-time, and Kinesis Data Firehose delivers the results to S3. Option B uses SQS, which is not designed for millions of messages per second, and Lambda may throttle under high load. Option C uses Redshift, which is a data warehouse; while streaming data can be loaded into Redshift, it is not a real-time streaming destination and typically requires Firehose. Option D uses IoT Core for ingestion, but DynamoDB is not optimized for storing large analytical results; S3 would be more appropriate.
Variation 3. A company is designing a new real-time analytics platform that ingests millions of events per second from IoT devices. The events must be processed with low latency (under 100 ms) and stored for replay. The company wants to use managed services. Which combination of AWS services should the company use?
hard- ✓ A.Amazon Kinesis Data Streams + AWS Lambda
- B.Amazon S3 + AWS Lambda
- C.Amazon Kinesis Data Firehose + Amazon Redshift
- D.Amazon SQS + AWS Lambda
Why A: Amazon Kinesis Data Streams can ingest and buffer millions of events per second with sub-100 ms latency, and AWS Lambda can process each record in near real-time as it arrives in the stream. This combination meets the low-latency requirement and allows events to be replayed from the stream's retention window (up to 365 days with extended retention).
Variation 4. A company is designing a real-time analytics platform that ingests data from thousands of IoT devices. The platform must process and store high-velocity data with low latency. Which TWO AWS services should be used together to meet these requirements? (Choose TWO.)
medium- A.AWS Lambda
- ✓ B.Amazon Kinesis Data Streams
- ✓ C.Amazon Kinesis Data Analytics
- D.Amazon S3
- E.Amazon SQS
Why B: Amazon Kinesis Data Streams is correct because it is designed to ingest and store high-velocity data streams from thousands of IoT devices with low latency, providing durable, ordered data that can be consumed in real time. Amazon Kinesis Data Analytics is correct because it can process streaming data from Kinesis Data Streams using SQL or Apache Flink to perform real-time analytics without needing to store the data first, meeting the low-latency processing requirement.
Variation 5. A company is designing a real-time analytics platform that ingests data from thousands of IoT devices. Each device sends a JSON payload every second. The company needs to store the raw data for a month and then aggregate it into hourly summaries for long-term storage. The solution must be serverless and cost-effective. Which combination of AWS services should the company use?
hard- A.Amazon Kinesis Data Streams to ingest data, AWS Lambda to transform and aggregate, Amazon S3 for storage.
- ✓ B.Amazon Kinesis Data Streams to ingest data, Amazon Kinesis Data Analytics to aggregate in real-time, Amazon Kinesis Data Firehose to deliver aggregated data to S3, and an S3 Lifecycle policy to expire raw data after 30 days.
- C.Amazon Kinesis Data Streams to ingest data, Amazon Kinesis Data Firehose to deliver to S3, and Amazon Athena to query raw data.
- D.Amazon SQS to ingest data, AWS Lambda to process and aggregate, Amazon DynamoDB for raw data, S3 for summaries.
Why B: Kinesis Data Streams ingests real-time data, Kinesis Data Analytics performs real-time aggregation, and Kinesis Data Firehose delivers aggregated data to S3. An S3 Lifecycle policy can expire raw data after 30 days. Option A uses Lambda for aggregation, which is not ideal for streaming aggregations. Option C misses the real-time aggregation step. Option D uses SQS, which is not designed for real-time streaming, and DynamoDB is not suitable for raw data storage at high volumes.
Variation 6. A company is designing a real-time analytics pipeline to process streaming data from IoT devices. The solution must be serverless and handle data transformation before storage. Which combination of services is most cost-effective?
medium- ✓ A.Amazon Kinesis Data Streams, AWS Lambda, and Amazon Kinesis Data Firehose to Amazon S3
- B.Amazon Kinesis Data Streams, Amazon EC2 instances for transformation, and Amazon S3
- C.Amazon Simple Queue Service (SQS), AWS Lambda, and Amazon S3
- D.Amazon Kinesis Data Analytics for real-time SQL and Amazon S3
Why A: It combines Kinesis Data Streams for real-time ingestion, AWS Lambda for serverless data transformation, and Kinesis Data Firehose to buffer and deliver transformed data to Amazon S3. This architecture is serverless, scales automatically, and is cost-effective as you pay only for data throughput and compute time without provisioning any servers.
Variation 7. A company is designing a new real-time analytics platform that processes streaming data from IoT devices. The data must be ingested, processed with windowed aggregations, and stored in Amazon S3 for long-term analytics. The solution must handle late-arriving data and provide exactly-once processing semantics. Which combination of AWS services should the architect use?
hard- A.Use Amazon Kinesis Data Firehose to ingest data and AWS Glue for processing.
- B.Use Amazon EMR with Spark Streaming to process data from Kinesis Data Streams.
- C.Use AWS Lambda to process records from Kinesis Data Streams and store in S3.
- ✓ D.Use Amazon Kinesis Data Analytics for Apache Flink to process data from Kinesis Data Streams and output to S3.
Why D: Amazon Kinesis Data Analytics for Apache Flink provides built-in support for windowed aggregations, exactly-once processing semantics, and handling late-arriving data via allowed lateness and watermarking. It can output processed results directly to Amazon S3 using a Flink sink, meeting all requirements for a real-time analytics platform.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-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 SAP-C02 exam.