OGEA-102 Exam Information and Outline
TOGAF Enterprise Architecture Part 2
OGEA-102 Exam Syllabus & Study Guide
Before you start practicing with our exam simulator, it is essential to understand the official OGEA-102 exam objectives. This course outline serves as your roadmap, breaking down exactly which technical domains and skills will be tested. By reviewing the syllabus, you can identify your strengths and focus your study time on the areas where you need the most improvement.
The information below reflects the latest 2026 course contents as defined by The-Open-Group. We provide this detailed breakdown to help you align your preparation with the actual exam format, ensuring there are no surprises on test day. Use this outline as a checklist to track your progress as you move through our practice question banks.
Below are complete topics detail with latest syllabus and course outline, that will help you good knowledge about exam objectives and topics that you have to prepare. These contents are covered in questions and answers pool of exam.
Exam Code: OGEA-102
Exam Name: TOGAF Enterprise Architecture Part 2
Number of Questions: 8 scenario-based questions.
Duration: 90 minutes
Passing Score: 24 out of 40 (60%)
1. The Architecture Development Method (ADM)
Phases and their objectives:
- Preliminary (establishing architecture capability)-
- Phase A (vision)-
- Phase B (business architecture)-
- Phase C (information systems architectures: data and application)-
- Phase D (technology architecture)-
- Phase E (opportunities and solutions)-
- Phase F (migration planning)-
- Phase G (implementation governance)-
- Phase H (architecture change management)- Requirements Management (central process).
- Iteration and levels: Applying ADM across architecture landscapes (strategic- segment- capability) and using iteration cycles for refinement.
- Tailoring ADM: Adapting for organizational context- such as agile/DevOps integration or regulatory compliance.
- Guidelines and techniques: Iteration- demarcation- and partitioning to scope architecture efforts.
2. Architecture Content Framework
- Deliverables: Formal outputs like Architecture Definition Documents or Transition Architectures.
- Artifacts: Components of deliverables- categorized as catalogs (lists)- matrices (relationships)- and diagrams (visuals).
- Building Blocks: Reusable elements (e.g.- business capabilities or technology standards) classified as Architecture Building Blocks (ABBs) or Solution Building Blocks (SBBs).
- Content metamodel: Core entities (e.g.- actors- business services) and extensions for specific domains.
3. Enterprise Continuum and Tools
- Structure: From generic (Foundation Architectures like TOGAF reference models) to specific (Organization-Specific Architectures).
- Purpose: Promoting asset reuse- reducing duplication- and supporting migration from common to tailored solutions.
- Tools: Repository management for storing building blocks and ensuring interoperability.
4. TOGAF Reference Models
- Technical Reference Model (TRM): Layers for applications- information- and technology.
- Integrated Information Infrastructure Reference Model (II-RM): Focuses on boundaryless information flow.
- Boundaryless Information Flow: Enabling seamless data exchange across the enterprise.
5. Architecture Capability Framework
- Architecture Board: Oversight body for decisions.
- Maturity models: Assessing EA capability levels.
- Skills framework: Roles like Architecture Board- Enterprise Architect.
6. Stakeholder Management and Requirements Management
- Stakeholder mapping: Identifying concerns and influence.
- Requirements handling: Tracing from business to solution levels.
- Business scenarios: Technique for validating requirements.
7. Architecture Domains and Integration
- Domain-specific content: E.g.- Business Capability Map in Phase B.
- Integration: Ensuring cohesion across domains via metamodel.
8. Governance and Compliance
- Compliance reviews: Assessing adherence to principles.
- Risk management: Identifying residual risks post-mitigation.
- Dispensation: Approval for deviations from architecture.