A mobile gaming company wants to capture data from its gaming app and make the data available for analysis immediately. The data record size will be approximately 20 KB. The company is concerned…

Question

Options

• AHave the app call the PutRecords API to send data to Amazon Kinesis Data Streams.
• BHave the app call the PutRecordBatch API to send data to Amazon Kinesis Data Firehose.
• CHave the app use Amazon Kinesis Producer Library (KPL) to send data to Kinesis Data Firehose.
• DHave the app call the PutRecords API to send data to Amazon Kinesis Data Streams.

• A
  69% (36)
• B
  10% (5)
• C
  17% (9)
• D
  4% (2)

Explanation

Using the PutRecords API to send data to Amazon Kinesis Data Streams (Option A) is the correct solution. Kinesis Data Streams supports Enhanced Fan-Out (EFO), which provides each registered consumer with its own dedicated read throughput of 2 MB/s per shard - directly satisfying the requirement for 'dedicated throughput for each consumer.' PutRecords allows batch writes for efficiency, and at ~20 KB per record, this fits well within Kinesis shard limits (1 MB/s write, 1,000 records/s). Options B and C route data to Amazon Kinesis Data Firehose, which does not support Enhanced Fan-Out or dedicated per-consumer throughput - it is a delivery service, not a real-time streaming platform with multiple independent consumers. Option D appears identical to Option A in this question, but A is the intended correct answer pointing to Kinesis Data Streams with EFO.

No community discussion yet for this question.