Overview
Architecture Governance is how an enterprise makes sure its architectures are actually followed and kept current. This unit defines it as the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level. It covers controls over architecture work, compliance with internal standards and external obligations, and clear accountability to stakeholders. It sits within a wider hierarchy of corporate, technology and IT governance, and draws on characteristics such as discipline, transparency, independence, accountability, responsibility and fairness.
The unit then covers the three mechanisms the TOGAF Standard uses to make governance real. The Architecture Board oversees the architecture and decides on changes and dispensations. Architecture Contracts record agreements on deliverables, quality and fitness for purpose. Architecture Compliance reviews check projects against the architecture. These mechanisms do their main work in ADM Phases G and H.
How it's tested
Governance questions are short recall and recognition items. Expect a definition of Architecture Governance, a benefit to pick from a list, a responsibility of the Architecture Board, the role of an Architecture Contract, or a description of an implementation that you match to one of the compliance terms.
-
Role and responsibility
A governance activity, such as granting a dispensation or ensuring consistency between sub-architectures, is matched to the Architecture Board.
-
Purpose of a mechanism
A question asks what an Architecture Contract or a compliance review is for. Correct answers stress agreement on deliverables and quality, or early detection of non-conformance.
-
Compliance level match
An implementation is described in terms of which specification features it implements and whether it adds others, and you choose the compliance level.
A stem describes a project that cannot meet an architecture standard and asks who may allow a time-limited exception. The project sponsor is tempting because they own the budget. But exceptions to the architecture are dispensations, and granting them is a responsibility of the Architecture Board, which keeps the decision visible and recorded in the Governance Log. The words 'exception to the architecture' are the clue.
Learning outcomes 5
Official learning outcomes from the The Open Group outline, in outline order.
6.1 Briefly explain the concept of Architecture GovernanceManaging and controlling architectures at enterprise level.
- What it means
- Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level. It implements controls over the creation and monitoring of architecture components and activities, ensures compliance with internal and external standards, and provides accountability to a defined stakeholder community.
- What to understand
- It sits within a hierarchy: corporate governance, then technology and IT governance, then architecture governance. Its characteristics include discipline, transparency, independence, accountability, responsibility and fairness.
- How it shows up
- A stem offers definitions and asks which describes Architecture Governance; the one about managing and controlling architectures at enterprise level fits.
- Common confusion
- Treating governance as the same thing as project management or as a one-off approval.
6.2 Explain why Architecture Governance is beneficialAlignment, best practice, protected assets, visible risk.
- What it means
- Governance links IT processes, resources and information to organizational strategy and objectives, integrates and institutionalizes best practices, aligns with industry frameworks such as COBIT, and helps the organization make full use of its information, infrastructure and software assets.
- What to understand
- It also protects digital assets, supports regulatory and best-practice requirements such as auditability, security and accountability, and promotes visible risk management. These are enterprise-level benefits, not benefits to one project.
- How it shows up
- A 'which is a benefit of Architecture Governance' question offers 'promotes visible risk management' among distractors.
- Common confusion
- Choosing benefits that are really about faster project delivery or lower headcount.
6.3 Briefly explain the role of an Architecture Board and its responsibilitiesThe executive body that oversees the architecture.
- What it means
- The Architecture Board is a cross-organizational body that oversees implementation of the architecture strategy. Its responsibilities include consistency between sub-architectures, identifying reusable components, flexibility of the EA to meet changing needs, enforcing Architecture Compliance, improving the maturity of the architecture discipline, and providing a basis for decisions on changes to the architecture.
- What to understand
- Operationally it monitors Architecture Contracts, resolves escalated conflicts, grants dispensations and ensures governance information is published. It should have strong executive sponsorship and a small core membership; the TOGAF Standard suggests four or five permanent members and no more than ten. It is set up when the Architecture Capability is established.
- How it shows up
- A stem asks which body grants dispensations from architecture compliance: the Architecture Board.
- Common confusion
- Treating the Architecture Board as a project steering committee or as the team that designs architectures.
6.4 Briefly explain the role of Architecture ContractsJoint agreements on deliverables, quality and fitness for purpose.
- What it means
- Architecture Contracts are joint agreements between development partners and sponsors on the deliverables, quality and fitness for purpose of an architecture. They make the architecture enforceable by recording what will be delivered and how conformance will be judged.
- What to understand
- Contracts can exist between the architecture function and the business (the Statement of Architecture Work acts as one) and between the architecture function and implementation partners. They are central to Phase G, where they are signed and then monitored by the Architecture Board.
- How it shows up
- A stem asks what document records the agreement between architects and an implementation partner about deliverables and quality: an Architecture Contract.
- Common confusion
- Thinking an Architecture Contract is a commercial procurement contract with a vendor.
6.5 Briefly explain the need for Architecture ComplianceCheck that projects follow the architecture, and how closely.
- What it means
- Compliance reviews check that projects and solutions conform to the architecture. They catch errors early, when correction is cheaper, ensure best practices are applied, identify where standards need changing, and expose services that could be shared.
- What to understand
- TOGAF defines graded levels: Irrelevant, Consistent, Compliant, Conformant, Fully Conformant and Non-conformant. Results are recorded in a Compliance Assessment during Phase G.
- How it shows up
- A stem describes an implementation that correctly implements every specification feature and adds extra ones, and asks for the compliance level: Conformant.
- Common confusion
- Treating compliance as simple pass or fail, or mixing up Compliant and Conformant.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Architecture Governance definition
The practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level.
- Remember
- It covers controls, compliance with internal and external standards, and accountability to stakeholders.
- Tested as
- Direct definition question for outcome 6.1.
- Trap
- Choosing a definition of project governance.
-
Governance characteristics
Discipline, transparency, independence, accountability, responsibility and fairness describe good governance.
- Remember
- Independence means processes and decisions avoid conflicts of interest.
- Tested as
- List recognition in governance questions.
- Trap
- Adding speed or profitability as a characteristic.
-
Benefits of Architecture Governance
Links IT to strategy, institutionalizes best practice, aligns with frameworks such as COBIT, protects digital assets, supports auditability and regulation, and promotes visible risk management.
- Remember
- They are enterprise-level benefits.
- Tested as
- Outcome 6.2.
- Trap
- Picking project-level benefits.
-
Architecture Board
A cross-organizational, executive-sponsored body that oversees the architecture, enforces compliance, decides on changes and grants dispensations.
- Remember
- Small core: four or five permanent members, no more than ten.
- Tested as
- Responsibility matching questions.
- Trap
- Making it responsible for designing the architecture.
-
Dispensation
A granted, usually time-bound, exception allowing a project to deviate from the architecture.
- Remember
- Granted by the Architecture Board and recorded in the Governance Log.
- Tested as
- 'Who grants' and 'where recorded' questions.
- Trap
- Thinking project managers or sponsors can grant it alone.
-
Architecture Contract
A joint agreement between development partners and sponsors on the deliverables, quality and fitness for purpose of an architecture.
- Remember
- Signed and monitored in Phase G; the Statement of Architecture Work is one form.
- Tested as
- Outcome 6.4 and Phase G questions.
- Trap
- Treating it as a commercial supplier contract.
-
Compliance levels
Irrelevant, Consistent, Compliant, Conformant, Fully Conformant and Non-conformant grade how an implementation matches the specification.
- Remember
- Compliant: some specified features missing, but what is implemented follows the specification. Conformant: all specified features implemented correctly, plus extras.
- Tested as
- Compliance-level matching questions.
- Trap
- Swapping Compliant and Conformant.
-
Compliance review purpose
Reviews catch errors early, ensure best practice, identify standards that need change and find services that could be shared.
- Remember
- Early detection is cheaper than late correction.
- Tested as
- Outcome 6.5 'why compliance' questions.
- Trap
- Thinking reviews exist only to block non-compliant projects.
-
Governance hierarchy
Corporate governance contains technology and IT governance, which in turn contain Architecture Governance.
- Remember
- Architecture Governance must align with the levels above it.
- Tested as
- Context for definition questions.
- Trap
- Placing Architecture Governance above IT governance.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Compliant vs. Conformant vs. Fully Conformant
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Compliant | Some specified features are not implemented, but everything implemented follows the specification | Gaps allowed; no extra features | Thinking compliant means everything is implemented |
| Conformant | All specified features are implemented correctly, and the implementation also has features not in the specification | Complete, plus extras | Swapping it with compliant |
| Fully Conformant | Full correspondence between specification and implementation | Nothing missing and nothing extra | Using it for any implementation that passes review |
Irrelevant vs. Consistent vs. Non-conformant
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Irrelevant | The implementation has no features in common with the specification | The specification does not apply | Treating it as a failure |
| Consistent | Common features follow the specification, but some specified features are missing and some extras exist | Partial overlap, no violations | Confusing it with compliant |
| Non-conformant | Some specified features are implemented, but not in accordance with the specification | An actual violation | Using it for features that are simply missing |
Architecture Board vs. Architecture Contract
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Architecture Board | Executive body that oversees architecture, enforces compliance and grants dispensations | A decision-making group | Making it the design team |
| Architecture Contract | Agreement on deliverables, quality and fitness for purpose | A document the Board monitors | Treating it as a vendor purchase contract |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Compliant means complete
- What candidates pick
- Compliant for an implementation that delivers every specified feature plus some extras.
- Why it looks right
- In everyday language, compliant sounds like the strongest positive word.
- Why it's wrong
- That description is Conformant. Compliant means some specified features are missing but what is implemented follows the specification.
Clue to watch for 'Plus additional features' points to Conformant; 'some features not implemented' points to Compliant.
-
Sponsor grants exceptions
- What candidates pick
- The project sponsor as the authority for an exception to architecture standards.
- Why it looks right
- Sponsors control funding and priorities.
- Why it's wrong
- Dispensations from the architecture are granted by the Architecture Board so they stay visible and governed.
Clue to watch for 'Exception to the architecture' or 'dispensation' means the Architecture Board.
-
Board as design team
- What candidates pick
- An option saying the Architecture Board develops the Target Architecture.
- Why it looks right
- The Board is the senior architecture body.
- Why it's wrong
- Architects develop the architecture; the Board oversees, decides, enforces compliance and resolves escalations.
Clue to watch for Verbs such as oversee, approve, enforce and resolve fit the Board; design and model do not.
-
Contract as procurement
- What candidates pick
- An answer describing the Architecture Contract as the commercial agreement with a supplier.
- Why it looks right
- 'Contract' usually means a legal purchase agreement.
- Why it's wrong
- Architecture Contracts are agreements on architecture deliverables, quality and fitness for purpose between sponsors, architects and development partners.
Clue to watch for Look for 'deliverables', 'quality' and 'fitness for purpose' in the option.
-
Compliance as pass or fail
- What candidates pick
- A statement that compliance reviews result in either approval or rejection.
- Why it looks right
- Reviews often feel like gates.
- Why it's wrong
- TOGAF grades compliance across six levels and uses reviews to catch problems early and improve standards, not only to block projects.
Clue to watch for Options mentioning levels or early detection fit TOGAF's view of compliance.
Answer framework
Use these steps to answer a governance question by identifying the mechanism and its precise role.
- Decide whether the stem asks about governance in general, a governing body, an agreement document or a check on an implementation project.
- For general questions, look for enterprise-level control, compliance with internal and external standards, and accountability to a clearly identified stakeholder community.
- For decisions, exceptions, escalations or consistency across architectures, choose the Architecture Board.
- For agreements about deliverables, quality and fitness for purpose, choose the Architecture Contract, which is used mainly in Phase G.
- For checks on a project, choose a compliance review and match the described implementation carefully to one of the six compliance levels, checking for missing features, extra features and violations.
Practice question
Want more like this? The TOGAF EA Foundation practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the definition and benefits of Architecture Governance, which are short and answer outcomes 6.1 and 6.2 directly. Learn the definition phrase 'managed and controlled at an enterprise-wide level', then a handful of benefits such as linking IT to strategy, visible risk management and support for auditability.
Next, learn the three mechanisms as a set: the Architecture Board (a decision-making body), Architecture Contracts (agreements on deliverables and quality) and compliance reviews (checks on implementation). Write one verb for each, such as decide, agree and check, so you can sort options quickly.
The most commonly underestimated area is the compliance levels. They look easy, but Compliant and Conformant are reversed by many candidates. Draw two overlapping circles, one for the specification and one for the implementation, and sketch each level: no overlap (Irrelevant), partial overlap (Consistent), implementation inside specification (Compliant), specification inside implementation (Conformant), identical circles (Fully Conformant).
Finish by linking governance to Phases G and H and to the deliverables it uses. Then practise compliance-level and Architecture Board questions until each takes under a minute.
FAQ
How many questions does Architecture Governance carry?
The official OGEA-101 exam plan allocates 3 of the 40 questions to this unit, which is 7.5% of the paper and the smallest allocation.
What does the Architecture Board do?
It oversees the architecture, ensures consistency between sub-architectures, enforces compliance, decides on changes, resolves escalated issues and grants dispensations. It does not design the architecture itself.
What is the difference between compliant and conformant?
A compliant implementation leaves out some specified features but implements the rest correctly. A conformant implementation implements every specified feature correctly and also adds features the specification does not cover.
When are Architecture Contracts used?
They are central to Phase G, where they are agreed with implementation partners and monitored by the Architecture Board. The Statement of Architecture Work from Phase A also acts as a contract between the architecture function and the sponsor.
Why bother with compliance reviews?
They catch non-conformance early when it is cheaper to fix, confirm best practice is applied, show where standards may need to change and identify services that could be shared.
Where is governance set up in the ADM?
The governance structures, including the Architecture Board, are established in the Preliminary Phase as part of the Architecture Capability, and they operate mainly in Phases G and H.
How much time should I give this unit?
As a planning estimate, about 3 hours of a 40-hour plan, with most of it on the Board's responsibilities and the compliance levels.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 5 knowledge
You have just worked through the Architecture Board, Architecture Contracts and the six compliance levels. Test whether you can tell Compliant from Conformant under exam timing.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the TOGAF EA Foundation AI tutor Get any concept explained your way