A finance desk wants unusual permit-fee refunds flagged as payment events stream in, not only after a nightly batch. Which approach fits that need?
Select an answer to reveal the explanation.
Short Explanation
Nightly batches are like checking the cash drawer after closing. Streaming anomaly checks are the clerk who watches the drawer while customers are still in line. Odd refunds get spotted as they happen.
Full Explanation
Streaming applications process continuous event flows and can apply rules or models to detect outliers with low latency. For civic payment and refund streams, that means unusual patterns can be flagged as they arrive rather than only after batch windows close. The use case illustrates anomaly detection as a streaming workload, not merely a reporting afterthought.