TOGAF Practitioner Rewards the Governed, Just-Enough Next Step — Not Reciting the ADM
OGEA-102 gives you eight open-book scenarios scored 5, 3, 1 or 0. The skill tested is ranking four plausible options by how well each applies the ADM to that organisation's situation.
Check Your Readiness →Most candidates understand TOGAF Enterprise Architecture Practitioner (TOGAF Standard, 10th Edition), Part 2 exam OGEA-102 concepts — and still fail. This exam tests how you apply knowledge under pressure.
The Open Group publishes no area weights, and one scenario can draw on several areas. Each question describes an organisation and offers four options: the best earns 5 points, the next 3, then 1 and 0. The TOGAF library is provided in the exam, so judgement decides the score, not lookup.
Ask the sponsor to override her objection and continue
Update the Stakeholder Map and Communications Plan: she is now high power and high interest, a key player. Address her concerns with tailored views and route any new requirements through Requirements Management before finalising Phase B.
Finalise the design because the project's stakeholders signed it off
Resolve impacts across the Architecture Landscape before finalising: engage the other programme, assess overlap and reuse, and take conflicts to Architecture Governance. Approval by one project's stakeholders does not cover effects on other architectures.
Start detailed baseline modelling of every business process
Complete Phase A first: set scope across breadth, depth, time period and domains, include unions and data protection stakeholders, run a Business Transformation Readiness Assessment, frame security, and get the Statement of Architecture Work approved.
Update the existing architecture documents under change management
Phase H classifies change as simplification, incremental or re-architecting. Re-architecting needs a new Request for Architecture Work and a fresh ADM cycle starting at Phase A; document updates suit only simplification or some incremental changes.
The purpose of EA is guiding effective change. When teams are already delivering, the top answer usually sets up just-enough governance or targets the specific change, rather than pausing delivery for a detailed enterprise-wide target architecture.
Exceptions, dispensations and conflicts between projects go to the Architecture Board so the decision carries authority and lands in the Governance Log. An option where the architect decides alone and simply informs teams rarely scores 5.
The Request for Architecture Work is a Phase A input from the sponsor. The sponsor approves the Statement of Architecture Work at the end of Phase A to authorise the project. Architecture Contracts govern implementation in Phase G.
Changed requirements go through Requirements Management: record, reprioritise and run a Requirements Impact Assessment, which may revisit gap analysis in earlier phases. Direct insertion skips prioritisation and hides the effect on work already approved.
Security runs through every phase: security stakeholders, regulation and risk appetite are framed in Phase A, and data classification arises in Phases B and C. Options that schedule a security assessment after design completes cause rework and rank low.
Strengthen weak areas with exam-style practice questions and detailed explanations.
Simulate the real exam experience and assess your readiness under timed conditions.
Review key concepts, objectives, and exam topics in one place.
Get personalized explanations, learning recommendations, and instant answers.
Follow a structured learning path designed to help you prepare efficiently.
Eight gradient-scored scenarios: test whether you reliably pick the best TOGAF option, not the second best.