Question 420
For Oceanview Payments, an operational assessment affecting regulated card workflows and employee access uncovers: A source sends duplicate events with identical message IDs and an append-only sink counts every retry as new business activity. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
The test retry produces one accepted business event rather than two counted transactions. The observation provides evidence that the proposed fix (Deduplicate on a stable event identifier within the stated bounded streaming or batch semantics.) addressed the reported issue (A source sends duplicate events with identical message IDs and an append-only sink counts every retry as new business activity.) for Oceanview Payments and its regulated card workflows and employee access. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
The destination contains the expected snapshot and no long-running stream remains active. This is suitable evidence for another condition (A notebook copies a static dataset once but an engineer builds unnecessary continuous streaming infrastructure.) after a different response (Use a controlled batch notebook read and table write for the one-time bounded ingestion requirement.). For Oceanview Payments, it does not prove the required result: The test retry produces one accepted business event rather than two counted transactions.
The stream authenticates successfully and a repository scan does not find the service connection secret. This is suitable evidence for another condition (A streaming workload leaks an Event Hubs connection string into notebook source control.) after a different response (Use appropriate secret storage or workload credentials for supported Event Hubs connectivity.). For Oceanview Payments, it does not prove the required result: The test retry produces one accepted business event rather than two counted transactions.
A late-event test shows permitted events counted and state bounded according to the watermark. This is suitable evidence for another condition (A streaming job needs to aggregate events but late arrivals are held indefinitely because event-time watermarks are absent.) after a different response (Use a suitable event-time watermark and window strategy matched to accepted lateness requirements.). For Oceanview Payments, it does not prove the required result: The test retry produces one accepted business event rather than two counted transactions.