Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Assurance, Audit & Model Risk”
Assurance Map
A single view of which risks are covered by which assurance activity, exposing both the gaps nobody is looking at and the duplication several parties are paying for.
Independent Assurance
Assessment by a function with no involvement in designing or operating the control, which is what makes the assessment worth anything.
Model Inventory
A complete register of models in use with their purpose, owner, risk tier and validation status — the artifact everything else in model governance depends on.
Advisory Review Model
Running architecture review as a consulting service that improves designs rather than as an approval gate that permits them.
Architecture Cost Model
A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
Arrival Rate Model
Driving a load test by requests arriving per second regardless of how the system responds, rather than by a fixed number of virtual users.
C4 Model
A set of four nested diagram levels — context, container, component, code — that keeps each diagram at one consistent level of abstraction.
Capability Model
A structured map of what a business does, independent of how it is organised or which systems support it, used to align technology investment with function.
Cost Accountability Model
The arrangement determining whether teams merely see their costs or are financially charged for them, and the behaviour each produces.
Cost Model Sensitivity
Identifying which assumptions in a cost projection dominate the outcome, so effort goes into the estimates that actually matter.
Embedding Model Migration
The process of moving a corpus to a new embedding model, which requires re-embedding everything because vectors from different models are not comparable.
Execution Model Fit
Matching a workload's traffic shape, duration and state requirements to the execution model that suits it, rather than choosing one model for everything.
Fourth Party Risk
The dependencies of your dependencies, which you did not choose, may not know about, and remain accountable for.
Governance Operating Model
The arrangement of decision rights, review points and automated controls through which architectural intent is maintained across an organisation.
Licence Metric Risk
The exposure created when a software licence is priced on a unit that cloud architecture changes unpredictably, such as cores, sockets or instances.
Migration Risk Register
A maintained record of what could go wrong in a migration, with likelihood, impact, owner and mitigation, reviewed as the programme progresses.
Model Card
A structured record of what a model is for, how it was built and where it should not be used — written for the people who will deploy or be affected by it.
Model Context Protocol
An open protocol that standardises how AI applications connect to external tools, data sources and prompts.
Model Router
Directing each request to a model chosen by the task's difficulty, cost and latency budget, rather than sending everything to the largest model available.
Model Routing
Directing each request to the cheapest model capable of handling it, rather than sending all traffic to the most capable one.
A deployed model performed well in validation and its business metric has declined over four months. Nothing has been deployed. What do you investigate?
The model did not change; its world did Three distinct causes, and they need different responses: Data drift. The input distribution has moved — a new customer
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
The business wants to deploy a model that ranks loan applications, with a credit officer making the final decision. What must the architecture provide, and what will you insist on before go-live?
Classify first, because it determines everything else This decides access to credit for individuals. Under any consequence based classification it is high risk:
A CDC pipeline feeding your warehouse falls three hours behind during a source system's batch job, and the source's transaction log retention is 24 hours. What is the risk and what do you change?
The immediate risk Lag consumes the retention window. At three hours behind against a 24 hour retention, you have 21 hours of margin. If the consumer stops enti
A business unit wants an assistant answering questions from 200,000 internal documents. They ask whether to fine-tune a model or use retrieval. How do you decide?
Retrieval, for this requirement, and the reasoning is not about quality Four properties decide it: Freshness. Documents change. Retrieval reflects a change as s
A document collaboration product needs sharing with individuals, teams, and inherited folder permissions. Which authorization model?
The requirement is relationship shaped The questions this product must answer are: is this user a member of a team that has access to a folder that contains thi
A team wants event sourcing for a new order service, citing audit requirements. What do you recommend?
The recommendation: probably an audit log, not event sourcing If the requirement is audit , event sourcing is a very expensive way to obtain it. An append only
An internal AI assistant gives confidently wrong answers. The team wants to upgrade to a better model. What do you check first?
Establish whether the model ever saw the right content Log the retrieved chunks alongside each answer, then take the wrong answers and check: was the correct so
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
Design the audit logging for a system handling financial transactions. What is logged, where does it go, and what makes it hold up?
What is logged Significant actions only , defined explicitly rather than logging everything — an audit trail nobody can search is not usable evidence: Authentic
For each of these, choose a queue or a stream and justify it — order fulfilment tasks, an audit trail, cache invalidation, and rebuilding a search index.
Order fulfilment tasks — queue Each task is consumed once by one worker and is then irrelevant. Nothing re reads it; no second consumer needs the same task. Wha
Assurance, Audit & Model Risk
General material on assurance, architectural governance and risk oversight.
Model Risk Management
Inventory, validation, monitoring and challenge for models that make consequential decisions.
AI Risk Tiering
Classifying a use case by potential harm, and the obligations each tier triggers.
Audit Evidence
Producing durable, tamper-evident proof as a by-product rather than as a project.
Model Documentation
Model cards, intended use, limitations, and the record a regulator will ask for.
Model Evaluation & Red-Teaming
Adversarial testing of a probabilistic system with no fixed expected output.
Risk Appetite
The stated tolerance that tells you which risks you are allowed to accept.
Risk Assessment Methods
Qualitative matrices, FAIR and scenario analysis, and the illusion of a precise score.
Three Lines Model
Ownership, oversight and independent assurance, and where architecture sits in it.
Architecture Compliance Checks
Automating conformance to standards so review effort goes to the genuinely novel.
Bias & Fairness Controls
Measuring disparate outcomes, choosing a fairness definition, and living with the trade-off.
Certification Impact on Architecture
What SOC 2 and ISO 27001 actually require of a design, and what they do not.
Change Advisory vs Automated Gates
Replacing a weekly board with evidence a machine produces on every change.
Continuous Controls Monitoring
Testing controls continuously instead of sampling them once a year.
Control Design vs Operation
A control that is well designed and never runs fails exactly like one that is absent.
Design Authority
How an ARB should decide, what it should not review, and how it avoids becoming a queue.
Exception & Waiver Management
Time-boxed, owned deviations with a remediation date, rather than permanent silence.
Human-in-the-Loop Design
Meaningful review rather than a rubber stamp, and designing against automation bias.
Security Design Review
Reviewing an architecture for security while changing it is still cheap.
Segregation of Duties
Splitting authority so no single actor can both make and approve a change.
C4 Model
Context, container, component and code as four separate diagrams.
Exit & Concentration Risk
Being able to leave a provider, and what the regulator asks when you cannot.
Migration Risk
Bounding blast radius, staging by cohort, and honest readiness reporting.
Model Selection
Capability, latency, cost and the evaluation that decides between them.