The Open Group Updated OGEA-103 Exam Questions and Answers by angela

These domains provide a consistent way to describe and understand the architecture from different perspectives, such as business, information, and technology12. Each domain has its own set of concepts, models, views, and artifacts that define the structure and behavior of the architecture within that domain12.

The other options are incorrect because:

•Logical and Physical are not architecture domains, but rather levels of abstraction that can be applied to any domain. Logical architecture describes the functionality and behavior of the system, while physical architecture describes the implementation and deployment of the system3.

•Information and Data are not distinct architecture domains, but rather aspects of the same domain. Information architecture describes the meaning and context of the data, while data architecture describes the structure and format of the data4.

•Capability and Segment are not architecture domains, but rather levels of granularity that can be applied to any domain. Capability architecture describes the current and desired states of a specific business capability, while segment architecture describes a subdivision of the enterprise that has a clear business focus5.

Comprehensive and Detailed In-Depth Explanation from Expert in Enterprise Architecture, guiding in TOGAF and ArchiMate:

In the TOGAF Architecture Development Method (ADM), the Preliminary Phase is a foundational phase whose primary purpose is to establish and prepare the Architecture Capability within the enterprise. This phase ensures that the organization is structurally, procedurally, and culturally ready to undertake architecture work in a consistent and governed manner.

A core outcome of this phase is the Organization Model for Enterprise Architecture, which defines:

Architecture roles and responsibilities (e.g., Chief Architect, Domain Architects)

Reporting and decision-making structures

Architecture governance bodies (such as Architecture Boards)

Interaction with other governance and management processes

Accountability and ownership for architecture activities

The Organization Model enables repeatable, controlled, and effective execution of the ADM across initiatives. Without this model, architecture work would lack authority, consistency, and governance alignment.

Why Option A is correct:

The Preliminary Phase explicitly focuses on defining and establishing the Organizational Model for Enterprise Architecture as part of building the enterprise’s Architecture Capability.

Why the other options are incorrect:

B. Architecture Roadmap: This is developed later in the ADM when solution options, work packages, and migration paths are defined, mainly in Phases E (Opportunities & Solutions) and F (Migration Planning).

C. Implementation Governance Model: This is primarily addressed in Phase G (Implementation Governance), where architecture compliance and realization are governed.

D. Architecture Vision for the project: The Architecture Vision is the main deliverable of Phase A (Architecture Vision), which follows the Preliminary Phase.

Authoritative References (TOGAF Standard):

TOGAF ADM – Preliminary Phase: Objectives and Key Activities

TOGAF Architecture Capability Framework

TOGAF Architecture Governance concepts

These sources clearly state that the Preliminary Phase exists to define and establish the Organizational Model for Enterprise Architecture, making Option A the correct and fully aligned answer.

A content metamodel is a formal structure that defines the types of entities and relationships that are used to capture, store, filter, query, and represent architectural information in a way that supports consistency, completeness, and traceability12.

A stakeholder map is a tool that identifies and analyzes the key stakeholders and their interests, influence, and expectations in relation to the architecture3. It is not used to structure architectural information, but rather to understand the stakeholder needs and concerns.

An architecture framework is a set of principles, guidelines, standards, and tools that provide a common structure and methodology for developing architectures4. It is not used to structure architectural information, but rather to guide the architecture development process and ensure alignment with the business strategy and objectives.

An EA library is a repository that stores and manages the architecture artifacts, deliverables, and other relevant information produced and consumed during the architecture development and governance. It is not used to structure architectural information, but rather to provide access, security, and version control for the architecture content.

 1: The TOGAF Standard, Version 9.2 - Content Metamodel 2: TOGAF 9.2 Content Metamodel Framework - A Quick Guide - KnowledgeHut 3: The TOGAF Standard, Version 9.2 - Stakeholder Management 4: The TOGAF Standard, Version 9.2 - Architecture Framework : The TOGAF Standard, Version 9.2 - Architecture Repository

Phase G: Implementation Governance provides architectural oversight of the implementation. It ensures that the implementation conforms to the Target Architecture using Architecture Contracts and governance frameworks.

Phase H: Architecture Change Management is about maintaining the architecture lifecycle and handling new requirements, not direct implementation oversight.

Preliminary Phase is about setting up the architecture capability.

Phase A is about developing the Architecture Vision.