Answer-first summary for fast verification
Answer: The producer experienced network-related timeouts., There was a change in the number of shards, record processors, or both.
In Amazon Kinesis Data Streams, duplicated data can occur from both the producer and consumer sides. Option A is correct because if the producer (KPL) experiences network-related timeouts and doesn't receive a confirmation, it will retry sending the same record, causing duplicates in the stream. Option C is also correct because on the consumer side (KCL), changes in the number of shards (such as during scaling up or down) or changes in record processors (such as workers starting/restarting) trigger rebalancing. During rebalancing, a new record processor might start processing records from the last successfully written checkpoint, leading to reprocessing and duplication of records that were processed but not yet checkpointed.
Author: Ritesh Yadav
Ultimate access to all questions.
Question 60 A company is building an inventory management system and an inventory reordering system to automatically reorder products. Both systems use Amazon Kinesis Data Streams. The inventory management system uses the Amazon Kinesis Producer Library (KPL) to publish data to a stream. The inventory reordering system uses the Amazon Kinesis Client Library (KCL) to consume data from the stream. The company configures the stream to scale up and down as needed. Before the company deploys the systems to production, the company discovers that the inventory reordering system received duplicated data. Which factors could have caused the reordering system to receive duplicated data? (Choose two.)
A
The producer experienced network-related timeouts.
B
The stream's value for the IteratorAgeMilliseconds metric was too high.
C
There was a change in the number of shards, record processors, or both.
D
The AggregationEnabled configuration property was set to true.
E
The max_records configuration property was set to a number that was too high.
No comments yet.