Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Architecture Compliance Checks”
Conformance Automation
Encoding architectural standards as automated checks, so review effort is spent on novel design decisions rather than on verifying known rules.
Compliance Framework
A published set of control requirements an organisation is assessed against, which turns security posture into evidence somebody else will check.
Auditability
The ability to reconstruct who did what, to which resource, when, and from where — reliably enough to be relied upon after the fact.
Data Residency
A requirement that specific data be stored and sometimes processed only within a defined geography.
Data Retention Policy
A defined rule for how long each class of data is kept, where, and what happens at the end of it.
Encryption at Rest and in Transit
Protecting stored data from disclosure if the medium is obtained, and network data from disclosure if the path is observed — two different controls against two different threats.
Obligation Mapping
Translating each legal or regulatory requirement into the specific design constraints it imposes, so that compliance becomes a set of testable properties rather than a document.
Regulatory Constraint
A legal requirement that removes design options — and one that must be established early, because it is not negotiable and is expensive to retrofit.
Architecture Cost Model
A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
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 Development Method
TOGAF's iterative cycle for developing enterprise architecture, which is valuable as a checklist of concerns and harmful when followed literally.
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.
Architecture Roadmap
A sequenced plan of architectural change expressed as capability outcomes and decision points rather than as a fixed timeline of projects.
Architecture Sinkhole
A request that passes through every layer of a layered architecture without any layer adding logic, indicating that the layering is pure overhead for that path.
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.
Architecture Viewpoint
A perspective on a system tailored to the concerns of a particular audience, recognising that no single diagram serves everyone.
Six weeks before launch, an accessibility audit returns 200 issues. The team's automated checks were green. Why, and what do you do?
Why the checks were green Automated tooling reliably decides roughly a third of the criteria: missing alternative text, insufficient contrast, absent form label
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
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
Your organisation is starting SOC 2. Someone proposes scoping it to the whole estate "to be safe". What is your advice?
Scoping wide is not the safe option Everything inside scope must meet the full control set and be evidenced continuously. Everything outside must be demonstrabl
Your platform is built on an append-only event log with a lakehouse behind it. Legal asks how you will satisfy erasure requests within 30 days. What is your answer?
Establish the actual scope first Erasure applies to personal data held about the subject, and it has exceptions — data retained under a separate legal obligatio
A CFO asks why the architecture function should be funded when it ships no features. You have five minutes. What do you say?
Do not answer with activities "We produce standards, run a review board and maintain the technology radar" describes what the function does, not what the busine
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
A regulator asks how you ensure marketing consent withdrawal is honoured everywhere. What does the architecture need to show?
The answer they want is mechanism plus evidence Not "we have a consent database". They want to see how a withdrawal reaches every system that could act on it, a
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
Architecture Compliance Checks
Automating conformance to standards so review effort goes to the genuinely novel.
Compliance Frameworks
SOC 2, ISO 27001, PCI DSS — scope as an architectural lever.
Accessibility Testing
Automated checks, their ceiling, and the manual testing that has to sit above it.
Fitness Functions
Automated checks that an architectural characteristic still holds.
Guardrails
Deterministic checks on input and output that fail closed.
AI-Era Architecture
General material on architecting systems that include models.
Accessibility Architecture
Semantics, focus management and announcements designed in rather than audited in.
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 Governance
Preventive, automated controls rather than review meetings.
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.
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.