Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
60 results for “Architecture Governance”
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.
Reference Architecture
A pre-approved, documented template for a recurring class of solution, so that similar problems do not get individually redesigned.
AI Gateway
A shared proxy in front of model providers that centralises routing, keys, quotas, caching, logging and safety policy.
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.
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.
Compliance Framework
A published set of control requirements an organisation is assessed against, which turns security posture into evidence somebody else will check.
Data Lakehouse
A pattern that puts warehouse-style transactions, schema and governance on top of cheap open-format object storage.
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.
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.
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…
Technology Radar
A published, periodically-reviewed view of which technologies are endorsed, tolerated, being trialled, or to be avoided.
Well-Architected Review
A structured self-assessment of a workload against defined pillars — operational excellence, security, reliability, performance, cost, and sustainability.
Architecture Cost Model
A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
Architecture Style
A named, coarse-grained way of organising a whole system, as distinct from a pattern that solves one recurring problem inside it.
Architecture Trade-off Analysis Method
A structured evaluation that scores an architecture against prioritised quality-attribute scenarios and identifies the points where those attributes conflict.
Cell-Based Architecture
Partitioning a service into complete, independent copies of itself, each serving a subset of customers, so a failure is bounded to one cell.
Clean Architecture
Concentric layers with a strict dependency rule — source code dependencies point only inwards, towards higher-level policy.
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
When is an architectural decision worth an ADR, and what makes an ADR useful two years later?
What the interviewer is testing Whether you document decisions as a habit, and whether you know that most documentation fails because it records the wrong thing
You are reviewing a design for an internal tool with 200 users. It proposes Kubernetes, microservices, Kafka, a service mesh and CQRS. How do you handle the review?
What the interviewer is testing Judgement, and whether you can push back without alienating a team. Anyone can spot over engineering; the question is what you d
You inherit an estate of roughly 400 applications, no reliable inventory, and a mandate to reduce cost and risk. What do you do in the first ninety days?
What the interviewer is testing Whether you can sequence work at portfolio scale, and whether you go for evidence before strategy. This is the enterprise archit
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
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.
Operating Models
How delivery, platform and governance functions fit together.
AI-Era Architecture
General material on architecting systems that include models.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Architecture Communication
General material on communicating architecture.
Architecture Cost Modelling
Pricing a design before building it, at expected and at ten times volume.
Architecture Decision Records
One decision, its context, alternatives and consequences, kept immutable.
Architecture Decision-Making
General material on making and recording architectural decisions.
Architecture Diagrams
Choosing an audience and refusing to mix levels of abstraction.
Architecture Documentation
What to write down, at what altitude, and what nobody will ever read.
Architecture Fundamentals
General material on what solution architecture is and what an architect is accountable for.
Architecture Patterns
General material on architectural patterns and their trade-offs.
Architecture Principles
Durable agreed rules that rule options out, stated with rationale and implications.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Architecture Reviews
Reviewing early enough to influence rather than to veto.
Architecture Roadmaps
Sequencing change across an estate with dependencies and funding.
Architecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.
Architecture Styles
System-level organising shapes, and how they differ from problem-level patterns.
Business Architecture
General material on the business side of architecture.
Cell-Based Architecture
Complete isolated copies each serving a subset of customers.
Clean Architecture
Concentric layers with dependencies pointing only inwards.
Cloud Architecture
General material on designing for cloud platforms.
Enterprise Architecture
Portfolio-level architecture: standards, governance and the estate as a whole.
AI-Era Architecture
AI workloads meeting security, data, networking, reliability and cost.
API & Integration Architecture
Contracts between systems, and the compatibility discipline that keeps them working.
Architecture Communication
Explain the same architecture to a CEO, an engineering manager and an engineer.
Architecture Decision-Making
Where senior engineer becomes architect: evaluate, choose, write it down.
Architecture Fundamentals
What architecture actually is: drivers, constraints, trade-offs and the principles behind them.
Architecture Patterns
Patterns as tools for recurring problems, with forces and consequences.
Business Architecture
Connecting technology decisions to the outcomes that fund them.