OGEA-103 preparation should be deliberately split into Foundation recall and Practitioner application because the combined exam changes format halfway through. Section 1 is 40 closed-book multiple-choice questions in 60 minutes. Section 2 is 8 open-book, gradient-scored scenario questions in 90 minutes. Both sections require a 60% pass.
The best study order therefore builds precise TOGAF language first, then turns that knowledge into scenario judgment. Use the current OGEA-103 Body of Knowledge based on the TOGAF Standard, 10th Edition rather than a TOGAF 9 syllabus.
Phase one: learn the structure and core concepts
Start with what Enterprise Architecture is, why organizations use it, the structure of the TOGAF Standard, Fundamental Content versus Series Guides, stakeholder/concern/view concepts, building blocks, architecture capability, governance, repository, landscape, and continuity concepts.
Create a compact glossary in your own words. Foundation questions can turn on precise distinctions, so conceptual sloppiness creates avoidable errors later.
Phase two: memorize the ADM by purpose, not by letter
Learn Preliminary, A through H, and Requirements Management. For each phase, state the business purpose, major questions answered, and what work should exist when the phase is complete.
Use a TOGAF concepts only as a starting point, then align every phase to the current 10th Edition study materials.
Phase three: add the Part 1 question-weight priorities
The largest Foundation block is Introduction to the ADM with 14 questions. Concepts has 8, ADM Techniques 6, Architecture Content 5, Applying the ADM 4, and Architecture Governance 3.
Those counts should influence final review: candidates who spend half their Foundation time on governance but cannot explain the ADM are misallocating effort.
Phase four: learn techniques alongside the phase that uses them
Attach stakeholder management to Architecture Vision, gap analysis to architecture development, migration planning to implementation planning, risk/security to the work it informs, and requirements techniques across the entire cycle.
This prevents the technique list from becoming disconnected flashcards and prepares directly for scenario questions.
Phase five: master architecture content and governance
Review deliverables, artifacts, building blocks, repository concepts, views/viewpoints, governance, compliance, decision rights, and architecture capability. Then practice identifying which output would help a stakeholder or implementation team.
Practitioner success depends on using architecture content, not merely naming it.
Phase six: move into Practitioner context and stakeholder work
Study the role of the practitioner, organizational constraints, Architecture Vision, stakeholder mapping, communications, concerns, and how the architecture effort is scoped and positioned.
The TOGAF Enterprise Architecture Practitioner level expects application and analysis, so start comparing possible actions instead of asking only “which phase is this?”
Phase seven: rehearse Phases B through D as one development stream
Choose a simple transformation and develop baseline/target thinking across Business, Data/Application, and Technology Architecture. Identify gaps, requirements, building blocks, and views for relevant stakeholders.
Then ask how a decision in one domain changes another. This cross-domain reasoning is closer to enterprise architecture than three isolated phase summaries.
Phase eight: connect E, F, and G to delivery
Practice turning architecture gaps into work packages, transition architectures, roadmap and migration priorities. Then add Implementation Governance and architecture compliance.
Scenario answers should preserve architecture intent while recognizing practical delivery constraints, dependencies, value, and risk.
Phase nine: add Phase H and Requirements Management
Review how architecture is monitored after implementation, how change requests are assessed, when incremental change is enough, and when a new ADM cycle is justified. Keep requirements visible throughout every scenario.
This prevents preparation from ending at implementation as though architecture were a one-time project.
Finish with format-specific exam practice
For Part 1, practice quick, precise closed-book recognition and keep timing near 90 seconds per question. For Part 2, practice ranking scenario options by TOGAF appropriateness and locating relevant open-book material efficiently.
Keep one transformation case throughout the entire plan—for example, modernizing a customer-service platform across business process, data, applications, technology, and operating model. Use the same case when learning stakeholder management, baseline/target architectures, gaps, migration, governance, and change. Reuse makes the ADM feel like one method rather than ten chapters.
During concept study, create contrast pairs: stakeholder vs concern, view vs viewpoint, deliverable vs artifact, Architecture Building Block vs Solution Building Block, baseline vs target, requirement vs principle, governance vs management. TOGAF questions often become easier when candidates know not only a definition but its nearest confusing neighbor.
During ADM study, write one verb for each phase. Preliminary: prepare. A: envision. B/C/D: develop. E: structure solutions. F: plan migration. G: govern implementation. H: manage change. Requirements: manage continuously. This compressed map improves recall while preserving the deeper objectives underneath.
During techniques study, do not memorize techniques without an input and output. Stakeholder analysis should change communication or involvement; gap analysis should reveal required change; migration planning should change sequencing; risk analysis should change treatment or design. If a technique produces no decision, you probably do not understand why it is being used.
During Architecture Content study, build one small set of deliverables for the reference case: an Architecture Vision, a stakeholder view, a capability or process artifact, a data/application artifact, a technology view, and a roadmap. The exact format matters less than understanding why each artifact exists.
During governance study, add a deliberately nonconforming implementation request. Decide whether it should be rejected, accepted as an approved exception, or trigger architecture change. This exercise makes compliance and change governance much more concrete than memorizing governance-body names.
Before moving to Part 2 practice, complete several Part 1 sessions at exam pace. Forty questions in 60 minutes leaves enough time if terminology is fluent, but not if every ADM concept requires reopening notes. Closed-book accuracy should be stable before heavy scenario work begins.
When Part 2 practice starts, answer once without the reference, then use the open book to verify. This separates your reasoning weakness from navigation weakness. If the answer changes only because you found a specific passage, improve reference navigation; if the scenario itself was misread, improve method understanding.
Train gradient-scoring judgment by ranking all four choices rather than selecting one. Ask why the best response is more complete, why the second is partially valid, and which assumption makes the worst answer inappropriate. This mirrors the exam’s scoring model and produces stronger architecture judgment.
Use the official reference interface strategically. Search for distinctive terminology or navigate to the relevant Fundamental Content or Series Guide. Do not spend several minutes reading broad sections. Good open-book use is targeted confirmation after you have already classified the scenario.
During stakeholder/Phase A study, practice changing the message for different audiences. Explain the same architecture initiative to an executive sponsor, business owner, solution architect, operations lead, and governance board. The Architecture Vision succeeds only when stakeholders understand the value and implications that matter to them.
During B/C/D study, explicitly trace cross-domain dependencies. A new business capability may require new application services, data ownership changes, and technology infrastructure. Enterprise architecture value comes from seeing those relationships rather than producing isolated domain diagrams.
During E/F/G study, force prioritization. If the organization cannot implement every target change at once, decide which work packages form transition architectures and how value, dependency, risk, cost, and readiness influence the migration sequence. Then define how implementation will be governed.
During Phase H study, add an external shock after implementation—a regulation, acquisition, technology shift, or strategy change. Decide whether the architecture can absorb it as maintenance or requires a new ADM cycle. This is a better test of change management than reciting the Phase H objective.
In the final days, use TOGAF 10th Edition to verify terminology and practice navigating the same type of material available in the open-book section. Avoid switching to older TOGAF 9 summaries unless you are deliberately comparing terminology.
Your final readiness test should be one spoken end-to-end story: prepare the architecture capability, establish vision and stakeholders, develop business/data/application/technology targets, identify gaps, shape transition work, plan migration, govern implementation, monitor change, and manage requirements throughout. If that narrative is fluent, the exam’s two sections are connected in your mind.
Add one short daily navigation drill for the open-book material. Choose a practitioner topic—stakeholders, gap analysis, migration planning, requirements, governance—and locate the relevant section without reading broadly. The goal is to make the reference interface a fast confirmation tool rather than a last-minute search engine.
Add one “best versus merely valid” exercise for every Part 2 practice question. Write the strongest reason the best answer fits the current phase and the strongest reason the second-best answer is incomplete. Gradient scoring rewards this comparative judgment.
During requirements study, deliberately introduce a new requirement halfway through the reference transformation. Trace which current artifacts, stakeholder agreements, target components, or migration work need review. This reinforces the continuous nature of Requirements Management better than a static requirements list.
During repository/content study, review how previous architecture assets can be reused. Ask whether an existing building block, standard, pattern, or reference architecture fits the new context. Reuse is valuable only when requirements and constraints still match.
During Agile/digital-enterprise study, compress the architecture cycle. Decide what architecture must be known now, what can be elaborated later, and how governance remains effective while delivery iterates. This prevents the common misconception that TOGAF requires one large sequential design effort before any implementation begins.
In the final mock session, simulate the real format switch: complete a timed closed-book Foundation block, then immediately move into open-book scenarios. The content transition is also a thinking transition—from recall to application—so practicing it reduces fatigue and pacing surprises.
The Open Group provides official Foundation and Practitioner study guides and practice tests, and TOGAF exam preparation benefits from using them after the syllabus map is stable. The last week should alternate one closed-book block with one open-book scenario block so the format switch feels normal on exam day.