Council staff want a plain-language briefing line that defines Hadoop without vendor hype. Which statement is most accurate at concept level?
Select an answer to reveal the explanation.
Short Explanation
Plain talk: Hadoop is the toolkit cities use to park huge datasets across many machines and crunch them together. It is not a fancy Excel ribbon.
Full Explanation
At concept level, Hadoop is a framework for distributed storage and processing of very large datasets across clusters—an accurate plain-language briefing line for council staff without vendor hype. It situates municipal meter and sensor lakes on coordinated machines rather than one overloaded departmental server, and it explains why cities invest in clusters for archives that outgrow single systems while still needing governed processing. Hadoop is not a desktop spreadsheet add-in for formatting council PDFs or beautifying open-data charts. Hadoop is not a single relational database engine that replaces all municipal SQL systems of record used by clerks for day-to-day transactions. Hadoop is not a social media app used to poll citizens about open-data priorities or engagement campaigns. Exam caveat: keep the definition at framework and ecosystem level; do not equate Hadoop with one narrow product feature or claim it replaces every RDBMS in the city. Operational check: when briefing council, use the distributed storage-and-processing definition, cite one city workload such as meter history, contrast it explicitly with the permitting SQL system of record, and leave a one-pager in the legislative packet so future briefings stay consistent and non-hyped.