DAS-C01 · Question #113
A transport company wants to track vehicular movements by capturing geolocation records. The records are 10 B in size and up to 10,000 records are captured each second. Data transmission delays of a…
The correct answer is B. Kinesis Producer Library (KPL). The Kinesis Producer Library (KPL) is the correct choice because it is specifically engineered to maximize Kinesis shard throughput through two key mechanisms: (1) Aggregation - multiple small records (10 B each in this scenario) are combined into a single Kinesis record up to…
Question
A transport company wants to track vehicular movements by capturing geolocation records. The records are 10 B in size and up to 10,000 records are captured each second. Data transmission delays of a few minutes are acceptable, considering unreliable network conditions. The transport company decided to use Amazon Kinesis Data Streams to ingest the data. The company is looking for a reliable mechanism to send data to Kinesis Data Streams while maximizing the throughput efficiency of the Kinesis shards. Which solution will meet the company's requirements?
Options
- AKinesis Agent
- BKinesis Producer Library (KPL)
- CKinesis Data Firehose
- DKinesis SDK
How the community answered
(35 responses)- A14% (5)
- B77% (27)
- C3% (1)
- D6% (2)
Explanation
The Kinesis Producer Library (KPL) is the correct choice because it is specifically engineered to maximize Kinesis shard throughput through two key mechanisms: (1) Aggregation - multiple small records (10 B each in this scenario) are combined into a single Kinesis record up to the 1 MB limit, dramatically increasing the effective records-per-second per shard; and (2) Collection - multiple PutRecord API calls are batched into a single PutRecords call, reducing API overhead. The scenario's acceptance of a few minutes of delay aligns with KPL's asynchronous buffering behavior. Kinesis Agent is a simple log-shipping tool without aggregation. Kinesis Data Firehose is a delivery service, not a producer, and adds latency. The raw Kinesis SDK (PutRecord/PutRecords) works but lacks KPL's built-in aggregation, leaving throughput efficiency on the table with 10 B records.
Topics
Community Discussion
No community discussion yet for this question.