A city selects Apache Spark as the engine for micro-batch and stream analytics on curb-sensor events. What does that choice primarily recognize?
Select an answer to reveal the explanation.
Short Explanation
Picking Spark for curb-sensor streams means the city wants one engine that can chew live-ish micro-batches and related analytics. It is not the new home for every ledger or a paper-form toy. Think analytics platform, not CAP courtroom.
Full Explanation
Apache Spark is widely used as a platform for streaming (including micro-batch styles) and broader analytics on large datasets. Selecting it for curb-sensor analytics recognizes that role. It does not replace all relational and CAD systems, is not a paper form designer, and does not outlaw streams via CAP.