All 8 domains
68 official learning outcomes
45–59 hrs suggested study
-
Domain 01
The operating context every OGEA-102 scenario assumes: why EA exists, what a working Architecture Capability looks like, how governance and compliance keep it honest, and how security, agility and uncertainty shape the work.
Inside this domain
- Explain why guiding effective change is the purpose of Enterprise Architecture
- Explain what an Enterprise Architecture looks like
- Explain what an Architecture Capability is
- Explain the role of Architecture Governance and of the Enterprise Architect
- and 7 more learning outcomes
Watch for Big up-front design
- Learning outcomes
- 11
- Questions est.
- ~1 of 8 (often blended) scenario questions
Read the domain guide →
-
Domain 02
Applying-level skills tested through scenarios: find the right stakeholders, understand their concerns, show them the right views, keep them engaged as requirements change, and make trade-offs visible instead of hidden.
Inside this domain
- Apply stakeholder management: identify stakeholders, their concerns, views and communication needs
- Explain how to use architecture views
- Apply stakeholder engagement and requirements management
- Apply trade-offs in architecture development
Watch for One deck for all
- Learning outcomes
- 4
- Questions est.
- ~1 of 8 scenario questions
Read the domain guide →
-
Domain 03
How to start an architecture engagement well: gather the right inputs, set scope and constraints, confirm goals and principles, cover security early, and secure approval of the Statement of Architecture Work.
Inside this domain
- Apply the information needed to start the Architecture Vision phase
- Apply Phase A: scope, stakeholders, goals and constraints
- Describe a sufficient security-specific architecture design for Phase A
- Apply the outputs needed to proceed from Phase A
Watch for Model first
- Learning outcomes
- 4
- Questions est.
- ~1 of 8 scenario questions
Read the domain guide →
-
Domain 04
The core design phases of the ADM applied to scenarios: the common steps in Phases B, C and D, risk and security, business principles and drivers, and the inputs and outputs of Business, Information Systems and Technology Architecture work.
Inside this domain
- Understand the steps applicable to all phases of architecture development
- Understand risk and security considerations in architecture development
- Apply the information needed to develop business principles, goals and drivers
- Apply Phase B: Business Architecture
- and 5 more learning outcomes
Watch for Full baseline first
- Learning outcomes
- 9
- Questions est.
- ~1–2 of 8 scenario questions
Read the domain guide →
-
Domain 05
Turning an agreed architecture into change: Phase E opportunities and solutions, Phase F migration planning, and Phase G Implementation Governance, with the risk, value and contract decisions scenarios test.
Inside this domain
- Understand risk and security considerations for Phases E, F and G
- Describe the steps to create the Implementation and Migration Strategy
- Apply the three basic approaches to implementation
- Apply identifying and grouping work packages
- and 11 more learning outcomes
Watch for Big bang for speed
- Learning outcomes
- 15
- Questions est.
- ~1–2 of 8 scenario questions
Read the domain guide →
-
Domain 06
Phase H keeps the architecture useful after delivery: spotting change triggers, monitoring value and risk, deciding whether a change is a simple update or needs a new ADM cycle, and producing the right outputs.
Inside this domain
- Understand the inputs that trigger architecture change management
- Understand the activities needed for effective architecture change management
- Understand the outputs needed to proceed from Phase H
Watch for Quiet update
- Learning outcomes
- 3
- Questions est.
- ~0–1 of 8 (often blended) scenario questions
Read the domain guide →
-
Domain 07
The process at the centre of the ADM: how requirements are captured, baselined, monitored and changed across every phase, and how the Requirements Impact Assessment keeps the architecture consistent.
Inside this domain
- Understand the inputs that feed Requirements Management
- Understand how Requirements Management steps map to ADM phase steps
- Understand the purpose of the Requirements Management outputs
Watch for Direct implementation
- Learning outcomes
- 3
- Questions est.
- ~0–1 of 8 (often blended) scenario questions
Read the domain guide →
-
Domain 08
The techniques and structures that make the ADM work in practice: business scenarios, gap analysis, compliance and migration techniques, the repository and architecture levels, building blocks, the metamodel, taxonomy and risk assessment.
Inside this domain
- Understand how to use The Open Group TOGAF Library
- Understand the business scenario technique
- Understand the purpose of compliance assessments
- Understand migration planning techniques for gap analysis results
- and 15 more learning outcomes
Watch for More inventory
- Learning outcomes
- 19
- Questions est.
- ~1 of 8 (often blended) scenario questions
Read the domain guide →
Domain names, weights and learning outcomes come from The Open Group's official outline (TOGAF Certification Program Conformance Requirements X2202 v4.0 (April 2022), Level 2 Syllabus, with the current OGEA-102 exam plan (TOGAF Standard, 10th Edition)). Question counts and study hours are editorial planning estimates, not official figures. Last reviewed October 2026.