How to Earn TOGAF Enterprise Architecture Certification

TOGAF certification is easier to plan when you separate the standard from the qualification names. The current 10th Edition body of knowledge supports qualifications called TOGAF Enterprise Architecture Foundation and TOGAF Enterprise Architecture Practitioner. Calling them simply “TOGAF 10 Foundation” and “TOGAF 10 Practitioner” can blur the official naming and create confusion with older TOGAF 9 material.

Foundation validates knowledge and understanding of the core framework. Practitioner validates the ability to analyze and apply that knowledge in enterprise-architecture scenarios. Candidates can earn the qualifications through separate exams or, where appropriate, a combined path.

The right preparation method therefore depends on whether you are learning the vocabulary and structure or practicing architecture judgment. Start by choosing the qualification, then build study around the corresponding exam.

Choose Foundation or Practitioner based on the capability you need

TOGAF Enterprise Architecture Foundation is the entry point. It is appropriate when you need a structured understanding of concepts, the Architecture Development Method, governance, architecture content, and the way the framework organizes enterprise-architecture work.

TOGAF Enterprise Architecture Practitioner goes further. It expects candidates to apply concepts to stakeholder, architecture-development, implementation, change, and requirements scenarios.

If you are new to enterprise architecture, build the Foundation understanding first even if your long-term goal is Practitioner. Memorizing applied answers without a stable mental model of the framework is fragile.

Role context matters too. A solution architect may use TOGAF terminology differently from an enterprise architect responsible for cross-domain governance, operating models, and transformation roadmaps. Certification gives a shared framework, but experience determines how deeply you can connect it to organization-wide decisions.

Before studying, write down why you need the credential: common architecture vocabulary, formal enterprise-architecture responsibilities, consulting credibility, or a requirement in your employer’s capability model. That reason helps determine whether Foundation alone is sufficient.

Understand OGEA-101 before building the Foundation study plan

The OGEA-101 Part 1 exam contains 40 multiple-choice questions, allows 60 minutes, and requires 60% to pass. The syllabus covers core concepts, introduction to the ADM, ADM techniques, applying the ADM, architecture governance, and architecture content.

This format rewards accurate recall and conceptual distinction. You should be able to explain the purpose of an ADM phase, recognize architecture governance concepts, understand how requirements interact with the cycle, and distinguish artifacts and content without searching for every term.

Create a compact framework map, but do not reduce study to a phase acronym. For every phase, know the problem it addresses, the major inputs and outcomes, and how it connects with stakeholders and requirements.

OGEA-102 tests application rather than simple recall

The OGEA-102 Part 2 exam uses eight scenario-based case studies, allows 90 minutes, and uses gradient scoring. The best response receives the most credit, while partially appropriate answers can receive partial credit. The exam provides an integrated open-book reference to the relevant body of knowledge.

That changes preparation. The challenge is not locating a definition; it is choosing the most appropriate action in context. A scenario may involve stakeholder concerns, architecture development, migration, governance, implementation, or change. Several answers can contain something reasonable, but one aligns best with the framework and the stated problem.

Practice summarizing each scenario before looking at the answers: What is the architecture objective? Which part of the ADM or governance system is relevant? What decision must be made now? That prevents keywords from pulling you toward an attractive but incomplete option.

Learn the ADM as a decision system

The ADM is central to TOGAF, but rote phase memorization creates weak architecture judgment. Understand what each phase is trying to achieve and how requirements management interacts with the cycle.

Preliminary work establishes architecture capability and context. Phase A frames the vision. Phases B, C, and D develop business, information-systems, and technology architecture perspectives. Phases E and F move toward opportunities, solutions, and migration. Phase G governs implementation. Phase H manages architecture change.

When you understand those purposes, exam scenarios become easier because you can identify the architecture problem before trying to remember a letter.

Connect stakeholders, governance, and architecture content

Enterprise architecture is not produced for an abstract organization. It responds to stakeholders with concerns, decision rights, constraints, and different definitions of value. Study stakeholder management as part of architecture work, not as a separate communication chapter.

Governance matters because architecture intent must survive implementation. Compliance reviews, architecture contracts, decision structures, and change processes help an organization keep projects aligned with agreed architecture while still handling legitimate exceptions.

Architecture content gives the work a consistent form. Candidates should understand how deliverables, artifacts, and building blocks relate without trying to memorize every possible document as a checklist.

Use official material to control version drift

TOGAF has a long history, so older books and articles remain widely available. A resource can accurately describe TOGAF 9 and still be the wrong primary source for a current OGEA-101 or OGEA-102 candidate.

Use official TOGAF study resources to establish current syllabus and terminology. The Open Group provides Foundation and Practitioner study materials and practice tests aligned to the current certification structure.

Label legacy notes explicitly. Do not mix old exam codes or qualification names into current study material without explaining their status.

The 10th Edition also introduced a more modular way of presenting the standard, with fundamental content separated from a larger set of series guides. That is useful in practice because organizations can draw on guidance relevant to their architecture context rather than treating the standard as one rigid implementation manual.

For exam study, however, follow the syllabus. The existence of additional TOGAF publications does not mean every guide is equally important for OGEA-101 or OGEA-102.

Decide whether separate or combined testing fits your preparation

The Open Group also offers a combined Part 1 and Part 2 exam route. The combined path can be efficient for candidates prepared to sit both levels together, but it does not remove the need to pass both sections.

Separate exams can be better when you want to validate Foundation first, gain experience, and then return for Practitioner. The best route depends on prior architecture experience and how comfortable you are moving from recall into applied scenarios in one study cycle.

Existing TOGAF 9 Certified holders should also check the current bridge option instead of assuming they must restart from the beginning. Certification history can change the most efficient route.

Practice differently for the two exam styles

For Foundation, use retrieval practice. Explain concepts from memory, reconstruct the ADM, distinguish governance terms, and test yourself on why each concept exists. Short frequent review is more useful than repeatedly rereading the standard.

For Practitioner, build cases. Give yourself a stakeholder conflict, an architecture transition, an implementation deviation, or a change-management problem and decide which TOGAF concepts should guide the response. Then compare the reasoning with the official body of knowledge.

The open-book reference should confirm detail, not replace familiarity. With only 90 minutes for eight scenarios, candidates need enough conceptual fluency to know where to look and what question they are trying to answer.

When reviewing a practice scenario, rank the options rather than stopping after the correct one. Explain why one answer is best, why another is only partially appropriate, and what makes the weakest response inconsistent with the situation. That mirrors the gradient-scoring logic and strengthens architecture judgment.

Also practice moving between stakeholder concerns and architecture actions. A technically sound architecture response can still be wrong if it ignores who has authority, which concern is unresolved, or which phase of the work the organization has reached.

Certification is useful when it improves architecture reasoning

The strongest outcome is not being able to recite the TOGAF vocabulary. It is being able to connect business concerns, architecture decisions, transition planning, governance, and implementation in a repeatable way.

Foundation gives you the language and structure. Practitioner asks whether you can use it. Choose the level that fits your role, study from current material, and practice the type of thinking the exam actually tests.

If preparation makes you better at explaining why an architecture decision exists, whose concern it addresses, how it will be governed, and how the organization can move toward it, the certification is doing more than preparing you for an exam.

Build one end-to-end case as a study anchor. Choose an organization facing a transformation, identify stakeholders and concerns, outline baseline and target states, consider gaps and transition work, and describe how implementation would be governed. You do not need a huge document set; the point is to see how the framework connects.

That case also helps with Practitioner preparation because it gives abstract phases a concrete context. When a question asks what should happen next, you can reason from the purpose of the phase and the decision needed rather than searching memory for a phrase.

Keep the case deliberately imperfect. Add a stakeholder who resists the target state, a regulatory constraint, an implementation deviation, and a change in business priority. Enterprise architecture exists because organizations change under constraint; practice should reflect that.

When you can explain the trade-off rather than recite the framework, you are closer to Practitioner-level reasoning. The standard supplies structure; the architect still has to interpret the organization, evidence, stakeholders, and consequences.