OGEA-103 Exam Information and Outline
TOGAF Enterprise Architecture Combined Part 1 and Part 2
OGEA-103 Exam Syllabus & Study Guide
Before you start practicing with our exam simulator, it is essential to understand the official OGEA-103 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-103
Exam Name: TOGAF Enterprise Architecture Combined Part 1 and Part 2
Part 1: TOGAF Enterprise Architecture Foundation
Format: Multiple-choice questions
Number of Questions: 40
Duration: 60 minutes (maximum)
Passing Score: 60% (24/40 correct)
Open Book: Closed book (no reference materials allowed)
Part 2: TOGAF Enterprise Architecture Certified
Format: 8 scenario-based- open-response questions (candidates select and apply relevant TOGAF concepts to real-world situations)
Duration: 90 minutes (maximum)
Passing Score: 60% (approximately 24/40 scored points- as each question is worth 5 points)
Open Book: Open book (access to the TOGAF Standard- 10th Edition electronic reference is permitted)
Total Duration: 150 minutes
Part 1: TOGAF Enterprise Architecture Foundation (Level 1)
1. Concepts-"- Understand the purpose and benefits of enterprise architecture (e.g.- aligning business strategy with IT- reducing complexity- enabling agility).
- Core principles: Architecture as a discipline- enterprise vs. solution architecture- and the role of TOGAF in holistic EA.
- Key concepts: Architecture domains (Business- Data- Application- Technology)- interoperability- and sustainability."
2. Definitions-"- Master TOGAF terminology: e.g.- artifact- deliverable- building block- viewpoint- view- stakeholder- concern.
- Definitions related to the ADM: Iteration- partition- and conformance.
- Distinguish between baseline/current architecture and target/future architecture states."
3. Introduction to the ADM-"- Overview of the ADM as a high-level process for developing enterprise architecture.
- ADM phases: Preliminary- A (Architecture Vision)- B (Business Architecture)- C (Information Systems Architectures)- D (Technology Architecture)- E (Opportunities & Solutions)- F (Migration Planning)- G (Implementation Governance)- H (Architecture Change Management)- and Requirements Management (central process).
- ADM guidelines: Iteration- levels (strategic- segment- capability)- and security considerations."
4. Introduction to ADM Techniques-"- Stakeholder management basics: Identifying concerns and developing tailored views.
- Architecture partitioning: Dividing architectures into manageable segments.
- Gap analysis: Comparing baseline and target architectures to identify gaps."
5. Introduction to Applying the ADM-"- Scoping the architecture effort: Defining boundaries- time horizons- and priorities.
- Integration with enterprise architecture maturity models.
- Applying ADM in different contexts: e.g.- agile environments- digital transformation- or hybrid integrations."
6. Introduction to Architecture Governance-"- Purpose of governance: Ensuring compliance- managing risk- and supporting decision-making.
- Key elements: Architecture Board- compliance reviews- and governance framework.
- Relationship to enterprise governance and IT governance."
7. Architecture Content-"- Framework for content: Metamodel- content metamodel- and deliverables.
- Building blocks: Reusable components (e.g.- catalogs- matrices- diagrams).
- Architecture views and viewpoints: Tailoring content for stakeholders."
8. TOGAF Content Framework-"- Structure of the TOGAF Content Framework: Entities- relationships- and taxonomy.
- Use of the framework to organize architecture outputs across domains."
9. TOGAF Reference Models-"- Technical Reference Model (TRM): Core services- interfaces- and communications infrastructure.
- Integrated Information Infrastructure Reference Model (III-RM): Focus on boundaryless information flow.
- Boundaryless Information Flow: Enabling seamless data exchange."
10. TOGAF Certification Program-"- Overview of TOGAF certifications: Levels- conformance requirements- and recertification.
- Relationship to the broader Open Group ecosystem."
Part 2: TOGAF Enterprise Architecture Practitioner (Level 2)
1. The Context for Enterprise Architecture-"- Role and scope of EA: Initiating architecture projects- establishing the EA team- and defining architecture principles.
- Establishing the architecture capability: Skills framework- tools- and organizational structure.
- Applying TOGAF in diverse environments (e.g.- integrating with Zachman- ArchiMate- or agile/DevOps)."
2. Stakeholder Management-"- Stakeholder identification and mapping: Concerns- attitudes- and engagement strategies.
- Developing architecture views: Customizing outputs to address stakeholder needs.
- Techniques: Influence/interest grids- tailored communications- and managing expectations."
3. Phase A: The Starting Point (Architecture Vision)-"- Developing the vision: Business scenarios- stakeholder buy-in- and high-level requirements.
- Risk assessment and opportunity identification.
- Outputs: Vision document- approved statement of architecture work- and initial business case."
4. Architecture Development (Phases B- C- D)"-"- Phase B (Business Architecture): Developing baseline/target business models- gap analysis- and business principles.
- Phase C (Information Systems Architectures): Data and application architectures; logical/physical modeling; integration strategies.
- Phase D (Technology Architecture): Technology standards- infrastructure selection- and migration considerations.
- Common techniques: Gap analysis- use-case modeling- and architecture definition increments."
5. Implementing the Architecture (Phases E- F- G)"-"- Phase E (Opportunities & Solutions): Consolidating gaps- evaluating implementation options- and roadmap development.
- Phase F (Migration Planning): Prioritizing projects- developing migration plans- and resolving conflicts.
- Phase G (Implementation Governance): Compliance reviews- architecture contracts- and deployment management.
- Interoperability and migration roadmaps."
6. Architecture Change Management (Phase H)-"- Monitoring change: Detecting events- assessing impact- and prioritizing changes.
- Change process: Repetition of ADM phases- updating the architecture repository.
- Managing disruptions: Risk mitigation and change requests."
7. Requirements Management-"- Central role in ADM: Capturing- prioritizing- and tracing requirements.
- Techniques: Requirements repositories- traceability matrices- and baselining.
- Integration across phases: Ensuring requirements drive architecture evolution."
8. Supporting the ADM Work-"- Architecture Content Framework Application: Using metamodels for deliverables across phases.
- Partitioning: Segmenting architectures for scale and focus.
- Guidelines & Techniques: Iteration (across phases)- levels (strategic/segment/capability)- security architecture- and applying iteration to the ADM.
- Migrating from TOGAF 9 to TOGAF 10: Key changes- such as enhanced agile support and digital focus."