A city enterprise architect must explain ingestion, storage, processing, and serving layers to non-technical directors. What is the main purpose of those layers?
Select an answer to reveal the explanation.
Short Explanation
Layers are like a kitchen line: intake, pantry, prep, and plating. Keep those jobs apart so the city is not stirring raw logs into the public dashboard by hand. One emailed spreadsheet is not an architecture.
Full Explanation
Layered Big Data architectures separate ingestion, storage, processing, and serving so each concern can scale and change independently. Directors grasp that raw collection is not the same as curated delivery to apps and dashboards. Spreadsheet monocultures, paper-only serving, or processing without storage miss why layers exist. Clear layer purpose prevents treating the lake as both warehouse and user interface.