5 exercises — practice the language for Architecture Review Boards, waiver requests, architecture decision reviews, and IT governance models.
0 / 5 completed
Enterprise governance key concepts
Architecture Review Board (ARB): Governance body that reviews architecture decisions against enterprise standards.
Waiver request: Formal exception request for deviating from an enterprise standard — time-bound with risk mitigation.
Architecture Decision Review: Structured evaluation of a significant architecture choice before it is made.
IT governance model: Decision rights, accountability structures, and processes ensuring IT aligns with strategy.
Conditional approval: ARB approves the proposal subject to specific conditions being met.
1 / 5
A solution architect submits a proposal to use a NoSQL database for a new customer data platform. The Architecture Review Board requests changes before approval.
What is the role of an Architecture Review Board (ARB)?
An Architecture Review Board (ARB) is the governance mechanism for architecture decisions. It ensures that local decisions (one team choosing a technology or pattern) do not undermine enterprise-wide standards, security posture, or strategic direction. Typical ARB outcomes: Approved / Approved with conditions / Deferred pending clarification / Rejected with rationale. In TOGAF, the ARB is a key component of the Architecture Governance framework.
2 / 5
A team needs to use a technology that is on the enterprise Hold list due to a deadline constraint. They submit a waiver request.
What should a waiver request language include?
A waiver request is the formal mechanism for requesting an exception to an architecture standard. Good waiver language includes: (1) Scope — what specifically is being waived; (2) Justification — the business or technical reason; (3) Risk acknowledgement — what risks the exception introduces; (4) Mitigation — how those risks are managed; (5) Time bound — when the team will remediate or migrate. Waivers are exceptions, not permanent exemptions.
3 / 5
Complete the governance process description:
"All proposed changes to the enterprise reference architecture must go through an Architecture _____ Review — a structured assessment where architects evaluate the proposal against standards, risks, and strategic fit before recommending approval."
An Architecture Decision Review is a formal evaluation process — typically triggered when a team is making a significant architectural choice (adopting a new platform, changing an integration pattern, selecting a cloud provider). It is distinct from a waiver request (which asks for an exception) — a decision review is the standard process for all significant architecture choices. The output is typically an Architecture Decision Record (ADR) with the chosen option, rationale, and any constraints.
4 / 5
What best describes an IT governance model in a large enterprise?
An IT governance model defines: who makes decisions (decision rights), what decisions require escalation, how IT investment is prioritised and authorised, and how risk is monitored and reported. Common frameworks include COBIT, ITIL, and TOGAF's governance components. The governance model answers: "How does the organisation ensure that IT delivers value and manages risk?" It encompasses the ARB, investment approval, portfolio governance, and compliance mechanisms.
5 / 5
Which sentence correctly uses enterprise IT governance vocabulary in an architecture review context?
Option B demonstrates correct governance language: conditional approval (not binary approve/reject), specific conditions (security review, catalog registration), and a time bound (60 days). This is realistic ARB communication — boards rarely give unconditional approval for significant changes; conditions protect enterprise standards while unblocking delivery. Option A is a caricature of governance as obstruction. Option C normalises bypassing governance, which undermines the model entirely.