Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Data Governance & Semantics”
Data Contract
An explicit, versioned, enforced agreement between a data producer and its consumers about schema, semantics, quality and change policy.
Decision Rights Over Data
Who is entitled to decide what a data element means, who may see it and how long it is kept — the substance of governance once the policy documents are set aside.
Capital One's Data Centre Exit
A major US bank closed all eight of its data centres and moved fully to public cloud, treating governance automation as the enabling technology rather than a constraint.
Code List Governance
Managing the small shared enumerations — currencies, country codes, statuses, product categories — whose uncontrolled change breaks systems quietly.
Data Catalog
A searchable inventory of datasets with their schema, owner, meaning, freshness, quality and classification.
Data Lakehouse
A pattern that puts warehouse-style transactions, schema and governance on top of cheap open-format object storage.
Data Lineage
A record of where each dataset came from, what transformed it, and what depends on it — traced at table and ideally column level.
Data Mesh
An organisational approach that gives domain teams ownership of their analytical data as a product, with a self-serve platform and federated governance.
Data Retention Policy
A defined rule for how long each class of data is kept, where, and what happens at the end of it.
Purpose Limitation
The principle that personal data collected for one stated purpose may not be used for an unrelated one without a new lawful basis.
TOGAF
An enterprise architecture framework whose central element is the ADM, an iterative cycle from vision through business, data, application and technology architecture to implementa…
Automated Governance
Encoding architectural rules as executable checks in the build pipeline, so conformance is verified continuously rather than reviewed periodically.
Change Data Capture
Publishing a stream of a database's row-level changes by reading its replication log, without modifying the application that owns it.
Control Plane and Data Plane
The separation between the machinery that makes changes to a system and the machinery that serves its traffic.
Finance and Sales report different revenue for the same quarter. Both are convinced they are right. You are asked to fix the data. Where do you start?
Assume neither number is wrong The instinct is to look for a bug. In practice the overwhelming majority of these cases are two defensible definitions with no me
A CDO proposes moving to a data mesh because the central data team is a bottleneck with a nine-month backlog. How do you assess the proposal?
Agree with the diagnosis, examine the prescription The bottleneck is real and it is structural rather than a matter of capacity. A central team receives data fr
A dashboard has been wrong for three weeks. Nobody knows which upstream produced the table it reads. What is the governance failure, and what fixes it?
The failures, and there are three 1. No lineage. The question "which upstream produced this?" should be answerable in seconds by following a derived dependency
The analytics bill has tripled in six months with no corresponding growth in users or data volume. Where do you look?
Get cost per query, attributed Almost every analytical engine can report bytes scanned and compute time per query, with the identity that ran it. Without that a
You are setting data quality thresholds for a dataset with five consuming teams. How do you decide the numbers?
Not by the data team, and not one number for everyone Fitness for purpose differs by consumer. Ninety five percent completeness on an attribute is fine for a ma
You bought a data catalogue eighteen months ago. It is populated and nobody uses it. What went wrong?
Populated is not the same as useful Two failures produce this outcome and they need different fixes. The content went stale. Technical metadata was loaded once
A GDPR erasure request arrives for a customer. Where does their data actually live, and what makes this expensive to retrofit?
Where the data lives Longer than people expect, and enumerating it is most of the work: Primary database · read replicas · caches · search indexes · analytical
A business sponsor asks for a real-time data platform because "the competition has one". Reporting is currently a nightly batch that lands at 06:00 and nobody has complained. How do you handle this?
Do not answer the technology question "Real time platform" is a solution, and it has arrived without a problem attached. Answering it directly leads either to a
A new platform must serve a public partner API, three internal front-ends with different data needs, and high-volume service-to-service traffic. Choose the API styles and defend the choice.
Resist "pick one" These are three different problems with three different consumers. Standardising on one style optimises for architectural tidiness at the expe
A query that ran in 50ms for two years now takes 90 seconds. Nothing was deployed and the data volume grew normally. What happened?
The most likely cause: a plan flip The optimiser's choice is a function of estimated row counts. As the data grows or its distribution shifts, an estimate cross
A regulated client requires that no traffic between their data centre and your SaaS platform traverses the public internet. Design the connectivity and justify the cost.
Two distinct requirements hiding in one sentence Traffic must not traverse the public internet — a routing requirement. The client must be able to demonstrate i
A regulator asks whether customer data is encrypted. The team says yes, disks are encrypted. Is that a sufficient answer?
What disk encryption actually protects against Someone obtaining the physical medium or a raw storage snapshot. In a cloud context that means a provider employe
A vendor SaaS product embeds a model that scores customers, and its output drives an automated decision in your process. Your model governance framework covers models you build. What do you do?
The obligation does not transfer with the outsourcing You are accountable for the decision. That the scoring is performed by a vendor changes who operates the m
Choose storage for four workloads: a Postgres data directory, user-uploaded images, a shared build cache, and seven years of audit records.
Postgres data directory — block storage It needs low latency random reads and writes and a filesystem, and it attaches to one instance. That is precisely block
Data Governance & Semantics
General material on ownership, meaning, quality and control of data at enterprise scale.
BI Governance
Dashboard sprawl, certified reports, and the number the board is allowed to see.
Data Access Models
Role, attribute and purpose-based access over analytical data, and how they compose.
Data Catalog
Discovery, ownership and technical metadata, and why catalogues go stale.
Data Contracts
Producers committing to schema, semantics and freshness, and breaking builds when they do not.
Data Mesh
Domain ownership, data as a product, self-serve platform, and federated governance.
Data Observability
Freshness, volume, schema and distribution monitoring for pipelines that fail silently.
Data Products
A dataset with an owner, an interface, an SLO, and consumers who can rely on it.
Data Quality Dimensions
Completeness, accuracy, timeliness, consistency, validity and uniqueness as testable claims.
Data Sharing & Clean Rooms
Collaborating on data neither party may hand over, with computation as the interface.
Data Stewardship
The operating model that makes ownership a role rather than a slide.
Master Data Management
One authoritative record for a customer or product across systems that each have their own.
Reference Data
Code lists, hierarchies and currencies — small, shared, and quietly load-bearing.
Data Governance
Ownership, lineage, quality, catalogues and who may see what.
Business Glossary
Agreeing what a term means before arguing about which number is right.
Retention & Purge
Deleting from an append-only estate, and proving the deletion happened.
Row & Column-Level Security
Restricting slices of a table rather than the whole table, and where it is enforced.
Self-Service vs Governed
Letting analysts move fast without four teams reporting four different revenues.
Semantic Layer
Metric definitions held once and served to every tool that asks.
Sensitivity Labelling
Propagating a classification through joins and derived tables so controls follow the data.
Tokenisation & Masking
Dynamic masking, deterministic tokens, and preserving joinability without exposure.
Exactly-Once Semantics
What the phrase really means, where it holds, and the idempotent sink underneath it.
Streaming Data
Windowing, watermarks, late arrivals and exactly-once semantics.
CRDTs
Data types that converge without coordination, and the semantics you must accept.
Architecture Governance
Preventive, automated controls rather than review meetings.
Change Data Capture
Turning a database's replication log into a stream, and its coupling risk.
Client Caching & Data Layer
Stale-while-revalidate, invalidation and optimistic updates on the client.
Cloud Governance
Preventive policy, tagging, quotas and cost and security guardrails.