Health inspection records and building permits will share a municipal analytics platform, yet privacy rules differ sharply. What should the architecture treat as a cross-cutting design concern rather than a late bolt-on?
Select an answer to reveal the explanation.
Short Explanation
Sharing a platform is fine—sharing every row with everyone is not. Bake isolation and governance into the blueprint so health data and permits stay in their lanes from day one.
Full Explanation
When diverse municipal datasets share infrastructure, security and governance are architectural cross-cuts: authentication, authorization, encryption, lineage, and logical isolation must be designed with the layers, not added after pipelines fail an audit. Health data often carries stricter handling requirements than permitting records. Treating governance as optional tooling invites leakage and rework across ingestion, processing, and serving.