The Open Group Certifications in 2026: TOGAF Enterprise and Business Architecture

The Open Group certification portfolio in 2026 is centered on current bodies of knowledge rather than the older assumption that “TOGAF certification” always means TOGAF 9. For enterprise architecture, the modern path is based on the TOGAF Standard, 10th Edition and uses the OGEA exam family. TOGAF 9 credentials remain relevant for existing holders, but new candidates should begin with the current Enterprise Architecture or Business Architecture qualifications unless a bridge route applies.

The Open Group portfolio now spans both legacy and current TOGAF generations, so status labeling matters. TOGAF 9 Certified describes the earlier qualification, while current exams include OGEA-101, OGEA-102, OGEA-103, OGEA-10B, and OGBA-101.

OGEA-101 establishes the current Enterprise Architecture foundation

The OGEA-101 TOGAF Enterprise Architecture Part 1 exam validates foundational knowledge of the TOGAF Standard. Current Open Group guidance describes a 40-question, 60-minute multiple-choice exam with a 60 percent passing score. The scope includes concepts, the Architecture Development Method, introductory ADM techniques, application of the ADM, governance, and architecture content.

Foundation study should focus on relationships rather than isolated definitions. Understand how the Preliminary Phase establishes capability, how the ADM phases move from vision through business, information systems, technology, opportunities, migration, implementation governance, and change, and how Requirements Management interacts with the cycle.

Draw the ADM from memory, then annotate each phase with purpose, typical inputs, outputs, stakeholder concerns, and governance implications. The visual structure is useful only when you can explain what decision each phase enables.

OGEA-102 tests applied architecture judgment

The OGEA-102 Part 2 exam is intentionally different from Part 1. It uses eight scenario-based questions, is open book through the integrated reference material, allows 90 minutes, and uses gradient scoring. Candidates are rewarded for selecting the best response rather than simply recognizing a definition.

This design changes preparation. Memorization alone has diminishing returns because the standard is available during the exam. The more important skill is diagnosing the scenario: who the stakeholders are, which phase or technique applies, what constraints exist, and which action best follows TOGAF guidance.

Practice defending your choice. If two options appear plausible, explain why one is better in the stated context. That exercise develops the applied reasoning the Practitioner qualification is intended to measure.

The combined and bridge routes serve different candidate histories

Candidates can pursue the current Practitioner qualification by passing Part 1 and Part 2 separately or through the OGEA-103 combined exam. Existing TOGAF 9 Certified holders have a different option: the OGEA-10B bridge exam recognizes their prior qualification and assesses the current knowledge needed to transition.

Do not choose the bridge simply because it sounds shorter. It is meant for candidates who already hold the qualifying TOGAF 9 credential. New learners should follow the standard current path.

The older OG0-091, OG0-092, and OG0-093 exams belong to the TOGAF 9 generation. They remain useful when interpreting historical credentials but should not be presented as the preferred modern Enterprise Architecture route.

Business Architecture has its own current foundation exam

The OGBA-101 TOGAF Business Architecture Foundation exam focuses on the business layer: business models, capabilities, value streams, business scenarios, information mapping, organization mapping, and how those techniques support the ADM. Current Open Group guidance describes a 40-question, 60-minute exam with a 60 percent pass requirement.

Business architecture is not simply “TOGAF with the technology removed.” Its purpose is to clarify how an enterprise creates value, what capabilities it needs, how work and information flow, and how organizational structures support strategic outcomes.

Build examples from an organization you know. Define a value stream, identify the capabilities that enable it, map key information concepts, and show which organizational units participate. Practical modeling makes the terminology easier to distinguish.

Architecture governance turns models into controlled decisions

Enterprise architecture adds value when decisions are governed over time. Candidates should understand principles, standards, compliance, architecture contracts, review mechanisms, repositories, and the role of an Architecture Board. Governance helps ensure that project decisions remain aligned with agreed architecture while still allowing justified exceptions.

The article on architecture and resilience provides broader context for why architectural choices have consequences beyond diagrams. TOGAF study should connect governance with actual implementation risk, stakeholder commitments, and lifecycle change.

Create a scenario in which a delivery team wants to diverge from a standard. Decide what evidence is needed, who approves the exception, how the risk is documented, and how the architecture repository should reflect the decision.

The Architecture Repository and Enterprise Continuum solve different information problems

Candidates often mix the Architecture Repository, Enterprise Continuum, Reference Library, Standards Information Base, Architecture Landscape, Solutions Landscape, and governance records. Instead of memorizing names, ask what information each structure helps architects organize or retrieve.

Use a classification exercise. Take artifacts such as a current-state application map, approved cloud standard, reusable reference model, target architecture, architecture contract, and external industry model. Decide where each belongs and why. Then explain how an architect would use it during an ADM cycle.

This is especially useful for OGEA-101 because many foundation questions test whether candidates understand where architectural information is organized and how it supports reuse and governance.

Stakeholder concerns should drive views and communication

Architecture exists for stakeholders who make decisions. A finance leader, security architect, application owner, regulator, product executive, and operations team can all care about the same transformation for different reasons. TOGAF's concepts of stakeholders, concerns, viewpoints, and views help architects communicate the right information to each audience.

Practice taking one architecture and producing different explanations. An executive view may emphasize strategic outcomes and investment; an engineering view may emphasize interfaces and standards; a security view may emphasize trust boundaries and controls. The underlying architecture is the same, but the communication changes.

This skill is more important than creating a large diagram that attempts to satisfy everyone simultaneously. A useful view answers a stakeholder's concern without drowning it in unrelated detail.

Use the current Open Group body of knowledge and exam plan as the preparation contract

The Open Group publishes current examination plans and qualification paths. Use those sources to verify the exam identifier, open-book status, duration, scoring, prerequisites, and qualification outcome immediately before scheduling. The portfolio continues to evolve, so an older TOGAF course can be conceptually useful while still being the wrong exam-preparation map.

For Foundation, emphasize accurate conceptual structure. For Practitioner, emphasize scenario application. For Business Architecture, work through capabilities, value streams, and business models. Existing TOGAF 9 holders should verify bridge eligibility rather than repeating material unnecessarily.

The purpose of the credential is not to recite the standard. It is to develop, maintain, govern, and use architecture in a way that supports enterprise change. Preparation becomes stronger when every concept is tied to a decision an architect might actually make.

ADM iteration is another important current concept. Enterprise architecture work is rarely a single pass from Phase A to Phase H. Teams may iterate within a phase, between phases, or across the full development cycle as new information appears. Candidates should understand why iteration is controlled rather than treating the ADM diagram as a rigid waterfall.

Capability-based planning helps connect architecture work to the enterprise’s ability to perform. Instead of starting with a preferred technology, architects identify the business capability that must improve, assess its current maturity, define the target state, and then determine which process, information, application, technology, people, or governance changes are needed. This keeps architecture anchored in outcomes.

Roadmaps and transition architectures are equally important because a target state is rarely delivered in one step. Constraints, funding, dependencies, risk, organizational capacity, and existing commitments determine which changes can happen first. Practice converting a target architecture into a sequenced roadmap with measurable transition states rather than one large future-state diagram.

For Part 2 scenario practice, build a decision log. Record the stakeholder concern, the relevant TOGAF concept or ADM phase, the strongest option, and why the other plausible choices are weaker in that context. Reviewing those decision patterns is more useful than memorizing the answer to one scenario because the real exam changes the story while testing the same architectural judgment.

Architecture content should also be traceable. A principle can influence a requirement, which influences a building block, which appears in a target architecture and later becomes an implementation decision. Candidates who can trace those relationships are better prepared for governance questions because they can explain why a project deviation matters rather than merely stating that it violates a standard.

Keep terminology precise during study. A deliverable, artifact, building block, view, viewpoint, and repository component are related but not interchangeable. When reviewing an example, identify which category it belongs to and what decision it supports. Precision is especially valuable on Part 1 questions where several answer choices may use familiar TOGAF words in subtly different ways.

Finally, rehearse the vocabulary inside complete architecture situations rather than isolated flashcards. Context makes similar TOGAF terms easier to distinguish and improves transfer from Foundation knowledge to Practitioner judgment. This approach also reveals whether a candidate can connect artifacts and governance decisions across phases instead of recognizing definitions only in isolation.