Portfolio ↗

Quiz

2868 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2868 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication102 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience92 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

91 questions in Data Governance & Semantics.

  1. Data Access Models beginner

    An analyst can query the customer table. A regulator asks whether she was allowed to use it for the marketing model she built. Role-based access answers one of those questions and not the other. What is the difference between role-, attribute- and purpose-based access, and what does purpose add?

    2 min answer rbacabacpurpose-limitationaccess-control
  2. Data Access Models advanced

    Review this emergency data access design. A shared role called prod_break_glass grants read on every production table. Any team lead can approve a request in a chat channel. The grant has no expiry and is removed when someone remembers. Every use writes a row to an audit table in the same warehouse. It was used 140 times last year. What would you remove, what would you change, and what would you leave alone?

    3 min answer access-controlbreak-glassauditexpiry
  3. Data Catalog advanced

    A catalogue harvests column-level lineage by parsing the orchestrator's job definitions. A version upgrade changes one job format and the parser silently skips those jobs. The catalogue reports no error. What happens over the next three months?

    3 min answer lineagecatalogsilent failureimpact analysis
  4. Data Catalog intermediate

    A company deploys a data catalogue. Six months later almost nobody uses it and most entries are stale. What went wrong, and what would make it work?

    1 min answer catalogmetadataadoptionautomation
  5. Data Catalog intermediate

    An organisation deploys a data catalogue and nobody uses it. What makes a catalogue useful rather than an inventory?

    2 min answer deelcatalogdiscoverylineage
  6. Data Catalog advanced

    Salesforce's Force.com platform was described by Weissman and Bobrowski at SIGMOD 2009 as metadata-driven: many tenants' records share physical tables, with metadata rather than per-tenant schemas describing what each column holds. Your analytics estate sits on a platform of that shape. What breaks in a column-level data catalogue, and what replaces it?

    2 min answer salesforcemulti-tenancymetadatacatalogue
  7. Data Catalog intermediate

    You bought a data catalogue eighteen months ago. It is populated and nobody uses it. What went wrong?

    1 min answer data-governancecatalogueadoption
  8. Data Contracts advanced

    A data platform introduces data contracts and pipelines still break when producers change schemas. What was missing?

    2 min answer freshworksdata-contractsenforcementownership
  9. Data Contracts advanced

    A producer team renames a column. The data contract is defined and the contract test is green. Three hours later four downstream models fail and a board dashboard is blank. The test lived in the consumer's repository and ran on the consumer's schedule. What is the structural defect?

    3 min answer data contractscienforcement pointproducer
  10. Data Contracts advanced

    A schema change in one team's service breaks four downstream data consumers overnight. The contract existed. What failed?

    1 min answer data-contractsenforcementcicoupling
  11. Data Contracts intermediate

    GitLab publishes its data quality approach in its open handbook: a Trusted Data Framework of SQL and YAML test cases with PASS or FAIL results, four test types, and tiered data assets. What problem does that shape solve that a schema registry does not, and what does it cost?

    2 min answer gitlabdata-contractstestingdata-quality
  12. Data Contracts advanced

    You propose data contracts. An application team says "we are not a data team, our database is our own business". How do you respond?

    2 min answer governanceownershipinfluence