Question 580
During operational handoff for this problem: Streaming events are delivered at least once, and an application assumes each row is a new financial transaction. Which guardrail should be included?
Explanation
Correct Answer
Track producer sequence IDs and deduplication metrics. This reduces recurrence of: Transport replay semantics and business-level uniqueness are separate concerns. The verification should demonstrate: A duplicate-event fixture does not inflate the final business count while genuine changes remain.
Incorrect Answers
Implement idempotent downstream merge keys and replay tests. That safeguard is aimed at ANOTHER risk: A data team uses Snowpipe to load raw events but expects it to automatically merge updates into existing customer rows. It is less targeted than the control for: Transport replay semantics and business-level uniqueness are separate concerns.
Test notification delivery after cloud policy and storage routing changes. That safeguard is aimed at ANOTHER risk: A storage bucket sends events but a Snowpipe pipe never loads new objects because its notification integration is unconfigured. It is less targeted than the control for: Transport replay semantics and business-level uniqueness are separate concerns.
Review FORCE and PURGE options during production code changes. That safeguard is aimed at ANOTHER risk: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. It is less targeted than the control for: Transport replay semantics and business-level uniqueness are separate concerns.