A parking-sensor topic uses at-least-once delivery, so a garage analytics consumer may see the same occupancy event more than once. What consumer practice matches that delivery model?
Select an answer to reveal the explanation.
Short Explanation
At-least-once means the mailman might knock twice with the same letter. Your garage app needs a stamp check—process by meter or event id so a second copy does not invent phantom cars. That keeps dashboards honest when delivery retries happen.
Full Explanation
Messaging systems often guarantee at-least-once delivery: after failures and retries, consumers can receive duplicates. Civic occupancy pipelines must therefore apply idempotent updates keyed by stable identifiers rather than blindly incrementing counts. Assuming uniqueness, silencing acknowledgments, or blindly dropping redeliveries either corrupts metrics or loses legitimate events. Matching consumer logic to delivery semantics is a core ingestion awareness skill.