A city redesigns its portal analytics stack and must pick collection, Kafka ingestion, Spark processing, a lake, NoSQL counters, and dashboards that work together. What selection principle should guide the capstone design?
Select an answer to reveal the explanation.
Short Explanation
Modernizing civic portal analytics is an orchestra, not a junk drawer. Collection, Kafka, Spark, lake, hot counters, and dashboards have to play the same score. Pick the pieces so the layered story hangs together from beacon to boardroom.
Full Explanation
A chapter 10 capstone expects coherent integration of BDPC building blocks: client collection, Kafka-style ingestion, Spark processing, lake storage, NoSQL for hot counters, and dashboard serving. Selecting those components as one layered architecture yields a maintainable municipal web analyzer. Fragmented unrelated tools without shared event contracts fail to deliver trustworthy UX and ops insight.