OGEA-101 The Open Group TOGAF Enterprise Architecture Part 1 Exam (English) Free Practice Exam Questions (2026 Updated)

The four dimensions used to scope an architecture are Breadth, Depth, Time Period, and Architecture Domains1, p. 8.

Breadth refers to the extent of the enterprise covered by the architecture, which can range from a specific business unit to the entire organization1, p. 8.

Depth refers to the level of detail and completeness of the architecture, which can vary depending on the purpose, scope, and stakeholders of the architecture1, p. 8.

Time Period refers to the temporal aspects of the architecture, such as the current state, the target state, and the transition plan1, p. 8.

Architecture Domains refers to the classification of the architecture into four domains: Business, Data, Application, and Technology1, p. 8.

These four dimensions help define the scope and boundaries of the architecture and ensure that it meets the needs and expectations of the stakeholders.

1: The Open Group (2018). The TOGAF® Standard, Version 9.2. 1

According to the TOGAF Standard, an architecture view is a representation of a system from the perspective of a related set of concerns1. An architecture viewpoint is a specification of the conventions for a particular kind of architecture view1. Presenting different architecture views and architecture viewpoints to stakeholders helps architects to extract hidden agendas, principles, and requirements that could impact the final target architecture. This is because different stakeholders may have different concerns and interests in the system, and by showing them how the system addresses their concerns from different perspectives, the architects can elicit more feedback and validation from them2. For example, a business stakeholder may be interested in the business architecture view, which focuses on the business processes, functions, and capabilities of the system3. A security stakeholder may be interested in the enterprise security view, which addresses the security aspects of the system, such as confidentiality, integrity, and availability3. By presenting these views to the respective stakeholders, the architects can ensure that the system meets their expectations and needs, and also identify any potential issues or gaps that may affect the target architecture. References: 1: The TOGAF Standard, Version 9.2 - Architectural Artifacts - The Open Group1; 2: Understanding TOGAF Views and Viewpoints in Enterprise Architecture2; 3: Developing Architecture Views - The Open Group4

When scoping an architecture in TOGAF, three key axes (dimensions) are used to frame the extent of the architecture work. The first is time period (how far into the future or over what timeframe to plan). The second is depth—how detailed or granular the architecture models will be (e.g., high level, mid level, very detailed). The third is breadth, which refers to which parts (domains, business units, functions) of the enterprise will be included, and which architecture domains (business, data, application, technology) will be in scope. This triple‐dimension model helps architects, stakeholders, and governance bodies understand how wide, deep, and forwardlooking the architecture effort will be. Thus “breadth, architecture domains” is the correct third dimension.

Statements 1 and 3 highlight the value and necessity for Architecture Governance to be adopted within organizations. Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level12. It ensures that architectural decisions are aligned with the organization’s strategy, objectives, and standards. Architecture Governance also involves establishing and maintaining processes, decision-making, and mechanisms to avoid or minimize potential conflicts of interest, such as between different stakeholders, business units, or projects34. Moreover, Architecture Governance requires transparency and accountability for all actions implemented and their decision support, so that they can be inspected and evaluated by authorized parties, such as auditors, regulators, or customers5 . References:

•The TOGAF Standard, Version 9.2 - Architecture Governance - The Open Group

•Architecture Governance - The Open Group

•Tutorial: Governance in TOGAF’s Architecture Development Method (ADM)

•Architecture Governance in TOGAF: Ensuring Effective Management and Compliance

•The TOGAF Standard, Version 9.2 - Definitions - The Open Group

•[Architecture Governance in TOGAF: Ensuring Alignment and Control]

Architecture partitioning is not the same as architecture levels (so 1 is incorrect).

It allows different teams of architects to work on different parts of the architecture in parallel (2 is correct).

TOGAF does not prescribe a fixed partitioning model; it provides guidance (so 3 is incorrect).

Partitioning is used to simplify management of Enterprise Architecture in large or complex organizations (4 is correct).

The TOGAF Architecture Development Method (ADM) is best described as a repeatable process for developing architectures. It provides the step-by-step method used to create, evolve, govern, and manage enterprise architectures in a consistent and structured way. The ADM is the core of TOGAF and defines how architecture work progresses from preparation and vision through business, data, application, and technology architecture, then into opportunities, migration planning, implementation governance, and change management.

Option A is incorrect because a classification mechanism is not the purpose of the ADM. Option B is too narrow, since requirements management is only one supporting aspect of the ADM, not its full definition. Option C is also incorrect because readiness assessment may be used as a technique within architecture practice, but it is not what the ADM itself is.

The strength of the ADM is that it is iterative, adaptable, and repeatable. It can be tailored for different enterprises and change scenarios while still preserving a consistent method. This makes it suitable for both large transformation efforts and more focused architecture initiatives. Therefore, the best description is option D, a repeatable process for developing architectures.

A business scenario describes business and technology environment in which those problems occur. It provides a realistic context for identifying and addressing business problems and opportunities, as well as their impact on the enterprise’s architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.1 Business Scenarios.

business and technology environment in which those problems occur https://pubs.opengroup.org/togaf-standard/business-architecture/business-scenarios.html#_Toc68617078 "

A Business Scenario is a uniform description of: - Real business problems - The business and technology environment in which those problems occur - Value streams enabled by capabilities - The desired outcome(s) of proper execution - The human and computing components (the “actors”) who provide the capabilities "

The Enterprise Continuum provides a classification mechanism for artifacts, showing how they evolve from generic Foundation Architectures and Reference Models to organization-specific architectures.

Option A is about tools, not the Continuum.

Option B describes the Architecture Principles.

Option C describes the Architecture Repository.

In TOGAF, the Architecture Board is the key governance body responsible for ensuring that architecture practice is directed, controlled, and applied consistently across the enterprise. Its role is not to author project deliverables such as the Statement of Architecture Work, and it is not primarily a maturity assessment team. It also does not merely define the scope of individual compliance reviews. Its broader and more important purpose is to oversee the implementation of the Architecture Governance strategy.

This means the Architecture Board provides governance oversight, ensures adherence to architecture principles, resolves escalated architecture issues, reviews compliance with approved architectures, and supports decision-making where exceptions, dispensations, or governance judgments are needed. It acts as the authority that maintains consistency between business strategy, architecture intent, and implementation activity. In practice, the board ensures architecture work is aligned with enterprise goals and that governance processes are being followed properly across change initiatives.

Option B best matches this TOGAF role because it captures the Architecture Board’s enterprise-wide governance responsibility. The other options describe narrower activities that may occur within the governance environment, but they do not define the primary role of the Architecture Board itself. Therefore, B is the correct answer.

===========

“TOGAF defines **‘enterprise’ as any collection of organizations that has a common set of goals. For example, an enterprise could be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organizations linked together by common ownership.” www.opengroup.org

Architecture Principles are general rules and guidelines that inform and support the way in which an organization sets about fulfilling its mission. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions. One of the purposes of Architecture Principles is to establish a common understanding of how to control the business in pursuit of strategic objectives, by providing a framework for evaluating and agreeing on the changes that affect the enterprise’s architecture3 References: 3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles : The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 31: Architecture Principles

Comprehensive and Detailed Explanation

In the TOGAF ADM, deliverables go through a lifecycle of development, review, approval, and usage. TOGAF distinguishes between draft deliverables (work-in-progress) and final deliverables (those that have been formally reviewed and signed off).

Draft deliverables are produced as working versions of the required outputs in each ADM phase. These may carry version labels such as 0.1, 0.5, 0.9, etc., and are subject to stakeholder review and refinement.

Once the document has been reviewed and approved by the relevant stakeholders (e.g., Architecture Board, governance bodies), it becomes a final deliverable.

Final deliverables are baseline-controlled items and are formally stored in the Architecture Repository as an approved architecture artifact.

Thus, the correct term for a deliverable that has completed review and is approved is “final”.

Why the other options are incorrect

B. Approved: While true in general language, TOGAF uses the formal term “final deliverable”, not “approved deliverable.”

C. Ratified: This term is not used in TOGAF to describe the state of a deliverable.

D. Version 0.9: This is a draft numbering convention, not the status of an approved deliverable.

References

The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — description of deliverables, artifacts, and building blocks.

The Open Group, TOGAF® 9 Certified Study Guide — explanation of draft vs. final deliverables in the ADM lifecycle.

The Preliminary Phase is the phase in TOGAF where an organization establishes or enhances its Enterprise Architecture Capability. This includes defining governance structures, roles, responsibilities, processes, tools, and architectural principles. The objective is to prepare the organization to successfully execute the ADM.

Phase A focuses on Architecture Vision for a specific initiative, not on creating the overall EA capability. Phase G deals with implementation governance, and Phase H focuses on architecture change management. None of these phases are responsible for establishing the EA practice itself.

The Preliminary Phase answers foundational questions such as how architecture will be governed, who owns architecture decisions, how compliance will be enforced, and how architecture work will be integrated with other organizational processes. Therefore, creation of an Enterprise Architecture Capability clearly belongs to the Preliminary Phase.

The Implications section describes the impact of adhering to the principle on the organization, the processes, the information systems, and the technology23. It also identifies the changes, costs, and risks that may result from applying the principle23. The Implications section helps to communicate the benefits and consequences of the principle to the stakeholders and to guide the implementation and governance of the architecture23.

The other sections of the TOGAF template for Architecture Principles are1:

•Name: This section provides a short and memorable name for the principle that represents its essence and purpose23. The name should not mention any specific technology or solution23.

•Statement: This section provides a concise and formal definition of the principle that expresses the fundamental rule or constraint that the principle imposes23. The statement should be clear, unambiguous, and testable23.

•Rationale: This section provides the reasoning and justification for the principle, explaining why it is important and how it supports the business goals and drivers23. The rationale should also link the principle to the higher-level enterprise or IT principles that it elaborates on23.

Phase B of the ADM cycle is the Business Architecture phase. It describes the development of a Business Architecture to support an agreed Architecture Vision. The objectives of this phase are to describe the baseline and target Business Architecture, identify candidate Architecture Roadmap components based on gaps between the baseline and target, and determine whether an incremental approach is required. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2.2 Phase B: Business Architecture.

In TOGAF, each deliverable within the Architecture Development Method (ADM) has a specific role within the architecture lifecycle. Deliverable 3 in the question refers to the Request for Architecture Work, which is the formal document sent from the sponsoring organization to the architecture team to initiate an architecture development cycle. In practice, this request is associated with the organization’s established architecture capability and governance framework, which are created during the Preliminary Phase. The Preliminary Phase establishes how architecture work is requested, initiated, and governed across the enterprise. Therefore, the Request for Architecture Work is closely tied to outputs of the Preliminary Phase.

Deliverable 4 refers to the Architecture Requirements Specification, which contains quantitative and measurable statements that define what implementation projects must do to comply with the approved architecture. This specification becomes a key reference during implementation governance and serves as a major component guiding implementation projects, ensuring that solution delivery aligns with the architecture.

Thus, the correct completion of the sentence is that deliverable 3 originates from the Preliminary Phase, and deliverable 4 becomes a major component of an implementation project used to enforce architectural compliance during execution.

According to the TOGAF Standard, 10th Edition, a stakeholder is “an individual with an interest in a system” 1. A stakeholder can be anyone who is affected by the system, or who can influence or be influenced by the system. Stakeholders can have different roles, perspectives, and concerns regarding the system, and they can be internal or external to the organization. Stakeholder management is a technique that helps to identify, analyze, and engage the stakeholders of an architecture project, and to address their needs and expectations 2. The other options are not correct, as they are not the term used by the TOGAF Standard to describe an individual with an interest in a system. A consumer is “an individual or group that uses a product or service” 1. A lead architect is “an individual who is responsible for leading the development of an architecture” 1. A sponsor is “an individual who provides funding and support for an architecture project” 1. References: 1: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 2: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 24: Stakeholder Management.

In TOGAF, the Standards Library is the part of the Architecture Repository that contains the standards, specifications, and reference materials with which architectures must comply. Its role is to provide the authoritative set of technical, operational, and architectural standards that guide architecture development and governance. Therefore, the correct answer is B.

Option A refers more closely to the Architecture Capability, where the organization’s framework, governance approach, structures, and methods are defined. Option C also belongs to the governance and capability side of the repository, not to the Standards Library itself. Option D is closer to what would be found in a Reference Library or reusable architecture support materials, such as guidelines, patterns, and templates, rather than the Standards Library.

The Standards Library is important because it provides the compliance basis for new architectures and implementation work. Architects use it to ensure that designs align with approved enterprise, industry, legal, and technical standards. This supports consistency, interoperability, governance, and reusability across architecture efforts. Since the question asks specifically what the Standards Library does within the Architecture Repository, the most accurate completion is that it lists the set of specifications to which architectures must comply. Hence, Option B is the correct answer.