Duplicate curb-sensor events could inflate occupancy counts if the streaming job treats every delivery as unique. What concern does that raise?
Select an answer to reveal the explanation.
Short Explanation
If the pipe can hand you the same curb ping twice, naïve counting throws a party for ghosts. That is the at-least-once versus exactly-once conversation—dedupe or stronger semantics keep occupancy honest. Voltage-versus-block-size myths are a distraction.
Full Explanation
Streaming systems often provide at-least-once delivery, which can surface duplicates; without idempotent processing or exactly-once-oriented handling, aggregates such as occupancy can be inflated. HDFS block size versus sensor voltage, claims that Kafka cannot exist municipally, and drivers that refuse counters miss the processing-semantics issue.