Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Risk Assessment Methods”
Quantified Risk Estimate
Expressing a risk as a probability distribution over financial loss rather than as a colour, which makes risks comparable and mitigations arguable on cost.
Legacy System Assessment
A structured evaluation of a system's business value, technical condition and risk, used to decide what to do with it rather than to describe it.
Pre-Mortem
An exercise in which a team imagines a project has already failed and explains why, surfacing risks that a forward-looking risk assessment misses.
Capability Maturity Assessment
Rating each business capability on how well it is currently performed, so investment can be directed at the gap between importance and maturity.
Ethical Impact Assessment
Deliberately examining who could be harmed by a system and how, at the point in design where the answer can still change the outcome.
Fourth Party Risk
The dependencies of your dependencies, which you did not choose, may not know about, and remain accountable for.
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.
Operational Burden Assessment
Quantifying the ongoing engineering effort a self-managed component requires, so it can be compared honestly with a managed service's price.
Portfolio Assessment Matrix
Plotting each application on business value against technical quality, producing a disposition for every system in the estate.
Re-Identification Risk
The probability that pseudonymised data can be linked back to individuals, which is what keeps such data within the scope of data protection law.
Risk Tolerance Statement
The board-level declaration of how much of each risk type the organisation will accept, which is what tells an architect which risks may be accepted without escalation.
Use Case Risk Classification
Assigning an AI application to a risk tier based on the consequence of it being wrong, which then determines the obligations that apply.
Workload Fit Assessment
Choosing between warehouse, lake and lakehouse by the workloads that must run, rather than by which one is currently fashionable.
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.
Attack Surface
The complete set of points where an untrusted actor can interact with a system — and the quantity that reduction genuinely reduces risk.
Business Case Structure
The argument format that gets technical investment funded — problem, options, quantified benefit, cost, risk and a recommendation.
Canary Release
Routing a small fraction of traffic to a new version, watching its metrics, and expanding or rolling back based on what they show.
Capability Heat Map
A capability map coloured by a chosen dimension — maturity, cost, risk, or strategic importance — to make patterns visible to non-technical stakeholders.
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.
Commitment Coverage
The proportion of steady-state usage covered by discounted commitments, balanced against the risk of committing to capacity that is no longer needed.
Database Migration Strategy
The approach for moving data to a new store, which is usually the longest pole and the highest risk in any modernisation.
Decision-Making Under Uncertainty
Choosing well when the information is incomplete — by bounding the downside and buying information, rather than by waiting for certainty.
Evidence by Construction
Designing systems so that operating them produces the audit evidence automatically, rather than reconstructing it from screenshots when an assessment arrives.
A twenty-year-old core system supports most of the business. It is on unsupported technology, three people understand it, and the last replacement attempt was abandoned after two years. Design the programme.
Learn from the abandoned attempt first The most important input is why the last one failed, and the reasons are usually structural rather than technical: a big
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 front-end lead proposes micro-frontends so four teams can deploy independently. The application is a single React SPA. What is your assessment?
Test the premise first The stated goal is independent deployment. Ask what currently prevents it, because the answer is frequently not the architecture. If the
A marketing site is a client-rendered single-page application. Organic traffic is poor and the team blames the search engine. What is your assessment?
The rendering choice is the problem A marketing page is identical for every visitor and highly cacheable. Rendering it in the browser pays for personalisation t
A team proposes exposing their service's database change stream via CDC so other teams can consume it, avoiding the work of building an event API. What is your assessment?
Name what is actually being proposed The proposal is to publish the service's internal schema as its integration contract. CDC does not emit domain events; it e
PCI DSS assessment covers 40 systems and costs a fortune annually. How would you reduce that architecturally?
The principle Scope follows the data. Any system that stores, processes or transmits cardholder data is in scope and inherits the full control set. Reducing sco
Product wants to add a recommendation feature using browsing history. Legal asks for a data protection impact assessment. What does architecture need to supply?
What the assessment actually needs from architecture Legal cannot assess a feature description. They need the data facts, which only the design supplies: A data
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 15-year-old monolith runs the core of the business. Leadership wants microservices. How do you approach it, and what would make you refuse?
What the interviewer is testing Whether you start from the business problem or from the target architecture, and whether you are willing to say no. First, estab
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 regulator asks for evidence that your exit plan from your primary cloud provider is credible. The plan is a twelve-page document. What will they find, and what should you do?
What they will find A document describing an intention. Supervisors have moved from accepting exit plans to asking what has been tested, precisely because most
A team proposes rewriting a critical system from scratch, arguing the existing one is unmaintainable. How do you evaluate this?
Test the diagnosis before the prescription "Unmaintainable" usually means one of several different things, and they have different remedies: Nobody understands
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
Finance wants a three-year commitment on cloud spend for the discount. Engineering is nervous. How do you advise?
Commit to the floor, not to the forecast The safe commitment is the portion of usage that will exist regardless of what happens: the steady baseline, evidenced
Risk Assessment Methods
Qualitative matrices, FAIR and scenario analysis, and the illusion of a precise score.
AI Risk Tiering
Classifying a use case by potential harm, and the obligations each tier triggers.
Assurance, Audit & Model Risk
General material on assurance, architectural governance and risk oversight.
Exit & Concentration Risk
Being able to leave a provider, and what the regulator asks when you cannot.
Legacy Assessment
Understanding what a system does before deciding what to do with it.
Migration Risk
Bounding blast radius, staging by cohort, and honest readiness reporting.
Model Risk Management
Inventory, validation, monitoring and challenge for models that make consequential decisions.
Risk Appetite
The stated tolerance that tells you which risks you are allowed to accept.
Third-Party Risk
Assessing, contracting and monitoring the vendors your architecture now depends on.
Trade-off Analysis Methods
ATAM, scenarios, and naming the points where qualities conflict.
Architecture Compliance Checks
Automating conformance to standards so review effort goes to the genuinely novel.
Audit Evidence
Producing durable, tamper-evident proof as a by-product rather than as a project.
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.
Change Data Capture
Turning a database's replication log into a stream, and its coupling risk.
Communicating Threat Models
Making risk legible to people who will fund or accept it.
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.