A media platform has two jobs. One updates a live viewer dashboard from clicks as each click arrives. The other rebuilds yesterday's viewing table from a closed set of files. Which pairing of processing styles fits the two jobs?
Select an answer to reveal the explanation.
Short Explanation
A live microphone is not the same job as a sealed box of yesterday's tapes. You stream the clicks as they arrive, and you run the closed viewing files as a batch over a finished set. The trap is forcing both jobs into one style because both of them touch events.
Full Explanation
Streaming processes events as they arrive, which matches a dashboard that must change with each new click. Batch processing runs over a bounded collection that is already complete, which matches yesterday's viewing files once that set is closed. Pairing the live clicks with a stream and the closed files with a batch is the fit. Treating both jobs as batches makes the dashboard wait for a closed file even though the clicks are still arriving. Treating both jobs as streams keeps a finished historical set on a continuous feed it no longer needs. Reversing the pair streams the closed files and batches the live clicks, so the dashboard lags and the historical rebuild is framed as an open-ended feed. Exam caveat: running a batch often does not turn it into a stream; a stream is defined by handling arrivals continuously, and a batch is defined by a bounded input set. Operational check: confirm the click job consumes each event on arrival and the viewing job reads only the finished file set for yesterday.