Data Architecture

CIMP · 50 questions

• A city CIO says the data architecture project is done because a cloud warehouse was purchased. What should the information management lead emphasize?
• A county wants one platform tuned for both high-volume permit transactions and heavy cross-year analytics. Which architecture stance is most sound?
• Three agencies must exchange permit status without growing a web of brittle point-to-point feeds. What interoperability architecture move best reduces that sprawl?
• Business units need consolidated operational reporting without hammering the live OLTP permit system. Which pattern best fits that need?
• Leaders argue endlessly that warehouses are always right and lakes are always wrong—or the reverse. How should the architect choose?
• A new architecture initiative finds undocumented feeds and shadow databases across departments. Where should architecture work start?
• A municipality wants a target data architecture that can adapt as services change. What process stance best supports that goal?
• A statewide program proposes replacing every departmental data system in one cutover weekend. What modernization approach is more sustainable?
• Agencies repeatedly remap the same citizen and organization attributes for every new interface. Which interoperability design reduces that pairwise cost?
• A city is organizing its data estate and wants clearer ownership as services evolve. How should data domains be aligned?
• Emergency outage maps must refresh within minutes, while annual grant audits tolerate day-old extracts. What should architecture do with that difference?
• A legacy partner still requires nightly batch file drops while modern apps consume APIs. How should the architecture treat this situation?
• An analytic platform accumulates raw dumps with no certification steps and users stop trusting dashboards. What was missing from the analytic architecture?
• Non-architect executives struggle to grasp dense technical diagrams of the reference architecture. What communication approach helps most?
• Each operational application keeps its own conflicting copy of customer-of-record attributes. When governance can support it, what operational architecture preference is stronger?
• Sensitive resident health-related fields are proposed for an open analytic zone used by many contractors. What should guide placement?
• City asset inventory consumers need timely notice when an asset record changes, not only a nightly warehouse refresh. Which movement pattern fits?
• Project teams keep making conflicting trade-offs on master data and automation of controls. What foundational artifact should architecture publish?
• Departmental marts each define ‘open case’ differently, breaking enterprise performance reporting. What analytic architecture response is appropriate?
• A program lifts a brittle point-to-point integration graph into the cloud unchanged. What limitation should leaders expect?
• Shared datasets used across agencies lack owners, interface contracts, and freshness expectations. What modern architecture orientation addresses that gap?
• Heavy operational reports run directly against the live OLTP licensing database and cause lock contention for clerks. What architecture response is indicated?
• Partner agencies reinterpret status codes differently in every message exchange. Which interoperability assets should architecture elevate?
• Analytic storage costs rise because rarely used history sits on the same expensive tier as hot dashboards. What architecture practice should be applied?
• A team proposes a high-impact change to the city’s core data platform patterns. What lightweight governance practice should apply?
• A city licensing office maps current information flows for permit issuance and finds five separate person stores holding overlapping applicant identities. What should the architecture team prioritize next?
• Two municipal systems need to exchange case status repeatedly. Leadership wants durable system-to-system access without hard-coding database links between teams. Which pattern best fits?
• A county analytics team wants flexible landing of raw operational extracts plus trusted curated tables for official dashboards. Which layered pattern best describes that mediate approach?
• Platform engineers discover aging ETL jobs, undocumented schemas, and brittle overnight feeds, but the roadmap only lists new cloud projects. What should architecture leadership add?
• Emergency dispatch case stores must recover within minutes, while a best-effort monthly park-usage dashboard can tolerate longer outages. How should resilience be designed?
• A project proposes a new “integration database” so every department can dump and query shared tables freely, with no named owner or quality controls. What is the main architecture risk?
• A civic transformation program is planning architecture change by listing vendor replacements year by year. What planning approach better supports durable outcomes?
• A water utility must ingest high-frequency meter sensor readings continuously and also apply periodic batch GIS layer updates under one governed estate. What ingestion approach fits?
• A permits API is changing fields that several downstream agency apps consume. What practice best protects consumers from breaking producer changes?
• Multiple city applications each maintain their own copies of status codes, country codes, and fee categories that drift apart. What architectural placement helps?
• Analysts need freedom to experiment in sandboxes, but council briefing packs must use only certified metrics. How should architecture draw the boundary?
• The team chose an event-driven integration pattern for inter-agency case updates after debating hub-and-spoke alternatives. What documentation practice best preserves that rationale?
• A regional shared-services proposal would store citizen identity attributes in a cloud region outside the jurisdiction’s residency rules. How should architecture treat that constraint?
• Municipal traffic-event facts grow rapidly and analysts filter almost always by event date and district. At architecture pattern depth, what physical-design awareness helps performance?
• Three BI tools in the same city government show different “open case” counts for the same week. What architectural layer most directly mitigates competing metric definitions?
• After cutover to a new permitting platform, legacy databases remain online “just in case,” quietly attracting new writes. What should the modernization roadmap include?
• A city’s overnight pipelines occasionally stall silently, ship broken schemas, or spike in volume without alerts. What should architecture include among non-functionals?
• As more agencies join a shared services program, every team adds direct custom links to every other system. What integration direction scales better?
• A program places the only master person hub exclusively behind the warehouse team for analytics, while operational permitting apps keep creating conflicting local persons. What placement mistake is this?
• Domain teams want local data copies for autonomy, while the enterprise architecture board wants one centralized store for consistency. What is the sound response?
• A newly annexed department brings five legacy systems into the city’s data estate. What should architecture provide so onboarding is repeatable?
• A new benefits domain service must use data from a noisy legacy eligibility system without absorbing that system’s tangled model. Which boundary pattern helps?
• Two years into an architecture program, executives ask how to judge success beyond counting new diagrams. Which outcome metrics fit best?
• The city wants domain product teams to move fast without each reinventing pipelines, identity, and platform glue. Which team-topology pattern supports that?
• Leaders ask what principle should close a data-architecture program so tomorrow’s team can evolve the estate safely. What should be emphasized?