Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “BI Governance”
Certified Report
A small set of reports explicitly endorsed as authoritative, with an owner and a review cadence, distinguished from everything else people have built.
Automated Governance
Encoding architectural rules as executable checks in the build pipeline, so conformance is verified continuously rather than reviewed periodically.
Code List Governance
Managing the small shared enumerations — currencies, country codes, statuses, product categories — whose uncontrolled change breaks systems quietly.
Governance Operating Model
The arrangement of decision rights, review points and automated controls through which architectural intent is maintained across an organisation.
AI Gateway
A shared proxy in front of model providers that centralises routing, keys, quotas, caching, logging and safety policy.
Account Vending
Automated creation of new cloud accounts pre-configured with the organisation's networking, identity, logging, guardrails and cost allocation.
Application Portfolio Management
Maintaining an inventory of every application with its owner, cost, business value and technical health, and using it to decide what to invest in, replace or retire.
Architecture Decision Log
The ordered, immutable collection of a system's decision records, read as a history rather than as a specification.
Architecture Decision Record
A short, immutable document capturing one architectural decision, its context, the alternatives, and its consequences.
Architecture Principle
A durable, agreed rule that constrains design decisions in advance, stated with its rationale and its implications.
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Budget Guardrail
An automated control that constrains or alerts on spend before an invoice arrives, rather than reporting overspend after the fact.
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.
Cloud Exit Plan
A documented, costed assessment of what leaving a provider or service would require — increasingly a regulatory expectation and a better lock-in control than portability itself.
Compliance Framework
A published set of control requirements an organisation is assessed against, which turns security posture into evidence somebody else will check.
Configuration Drift
Divergence between the infrastructure described in code and the infrastructure actually running, usually caused by manual changes.
Data Catalog
A searchable inventory of datasets with their schema, owner, meaning, freshness, quality and classification.
Data Contract
An explicit, versioned, enforced agreement between a data producer and its consumers about schema, semantics, quality and change policy.
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.
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.
Error Budget Policy
The written agreement about what happens when the error budget is exhausted, which is what turns an SLO from a number into a control.
FinOps
The practice of giving engineering teams visibility into and accountability for the cost of what they build and run.
Fitness Function
An automated check that an architectural characteristic still holds, run continuously rather than reviewed occasionally.
Landing Zone
A pre-configured, governed cloud environment — accounts, networking, identity, logging, guardrails — into which workloads can be deployed safely.
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
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
Equifax was breached in 2017 through a vulnerability with a patch available two months earlier. Beyond "patch faster", what architectural and governance failures does that imply?
The case, as publicly reported Apache Struts vulnerability CVE 2017 5638 was disclosed in March 2017 with a patch available. An internet facing dispute portal a
Three teams have independently chosen three different message brokers. Design the selection and governance process going forward.
Understand why it happened before correcting it Three independent choices usually mean there was no easy default, no forum for the decision, or a central proces
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 DR test fails: the secondary region cannot launch enough instances. What happened, and what standing checks prevent it?
What happened Service quotas in the secondary region are far lower than in the primary , because nothing has ever run there at scale. Quotas are per account and
An organisation is starting cloud adoption. Three teams want to deploy next month. What must exist first, and what can wait?
What must exist before anything reaches production Account structure. Separation by environment and by workload, because an account is the strongest isolation b
Architecture decisions in your organisation are either ignored or bottlenecked in a review board. Design something better.
Why both failure modes have the same cause A review board is a synchronous, low bandwidth, high latency channel: teams wait, decisions are made by people distan
Cloud spend has grown 60% in a year while revenue grew 15%. The CFO wants a 30% reduction. How do you respond?
Change the metric before accepting the target Absolute spend is the wrong frame. Cost per unit of business value — per order, per active user, per gigabyte proc
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
Half your production changes are made through the console during incidents. The IaC repository no longer matches reality. What do you do?
Why this matters beyond tidiness The code has stopped being a description of reality, which removes the properties it was adopted for: the ability to recreate a
Leadership wants to buy an enterprise architecture repository tool. How do you advise?
Ask what question it will answer Tools fail here for one reason: the content goes stale. Within a year the repository lists systems that no longer exist, omits
BI Governance
Dashboard sprawl, certified reports, and the number the board is allowed to see.
Architecture Governance
Preventive, automated controls rather than review meetings.
Cloud Governance
Preventive policy, tagging, quotas and cost and security guardrails.
Cost Governance
Budgets, anomaly alerts, quotas and preventive policy.
Data Governance
Ownership, lineage, quality, catalogues and who may see what.
Data Governance & Semantics
General material on ownership, meaning, quality and control of data at enterprise scale.
Assurance, Audit & Model Risk
General material on assurance, architectural governance and risk oversight.
Business Glossary
Agreeing what a term means before arguing about which number is right.
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.