The Open Group OGEA-101 Practice Exams
Last updated on Oct 21,2026- Exam Code: OGEA-101
- Exam Name: TOGAF Enterprise Architecture Part 1 Exam (English)
- Certification Provider: The Open Group
- Latest update: Oct 21,2026
Question #10
What are the following activities part of?
• Initial risk assessment
• Risk mitigation and residual risk assessment
• Risk monitoring
- A . Risk Management
- B . Phase A
- C . Security Architecture
- D . Phase C
Correct Answer: A
A
Explanation:
The following activities are part of Risk Management:
– Initial risk assessment
– Risk mitigation and residual risk assessment
– Risk monitoring
Risk Management is the process of identifying, assessing, and responding to risks that may affect the achievement of the enterprise’s objectives. Risk Management involves balancing positive and negative outcomes resulting from the realization of either opportunities or threats.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.3 Risk Management.
A
Explanation:
The following activities are part of Risk Management:
– Initial risk assessment
– Risk mitigation and residual risk assessment
– Risk monitoring
Risk Management is the process of identifying, assessing, and responding to risks that may affect the achievement of the enterprise’s objectives. Risk Management involves balancing positive and negative outcomes resulting from the realization of either opportunities or threats.
Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.3 Risk Management.
Question #12
Which of the following describes a purpose of Architecture Principles?
- A . To describe likely impacts resulting from successful deployment of the target architecture.
- B . To establish a common understanding of how to control the business in pursuit of strategic objectives
- C . To provide a better understanding about the enterprise’s culture and values
- D . To form a contract between sponsoring organization and the enterprise architects
Correct Answer: B
B
Explanation:
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
Reference: 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
B
Explanation:
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
Reference: 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
Question #13
Which of the following describes the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level?
- A . Corporate governance
- B . Architecture governance
- C . IT governance
- D . Technology governance
Correct Answer: B
B
Explanation:
According to the TOGAF Standard, 10th Edition, architecture governance is “the practice by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level” 1. Architecture governance ensures that the architecture development and implementation are aligned with the strategic objectives, principles, standards, and requirements of the enterprise, and that they deliver the expected value and outcomes. Architecture governance also involves establishing and maintaining the architecture framework, repository, board, contracts, and compliance reviews 1. The other options are not correct, as they are not the term used by the TOGAF Standard to describe the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level. Corporate governance is “the system by which an organization is directed and controlled” 2, and it covers aspects such as leadership, strategy, performance, accountability, and ethics. IT governance is “the system by which the current and future use of IT is directed and controlled” 2, and it covers aspects such as IT strategy, policies, standards, and services. Technology governance is “the system by which the technology decisions and investments are directed and controlled” 3, and it covers aspects such as technology selection, acquisition, deployment, and maintenance.
Reference: 1: TOGAF Standard, 10th Edition, Part VI: Architecture Governance, Chapter 44: Introduction. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Series Guide: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Part II: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Chapter 5: Technology Governance.
B
Explanation:
According to the TOGAF Standard, 10th Edition, architecture governance is “the practice by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level” 1. Architecture governance ensures that the architecture development and implementation are aligned with the strategic objectives, principles, standards, and requirements of the enterprise, and that they deliver the expected value and outcomes. Architecture governance also involves establishing and maintaining the architecture framework, repository, board, contracts, and compliance reviews 1. The other options are not correct, as they are not the term used by the TOGAF Standard to describe the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level. Corporate governance is “the system by which an organization is directed and controlled” 2, and it covers aspects such as leadership, strategy, performance, accountability, and ethics. IT governance is “the system by which the current and future use of IT is directed and controlled” 2, and it covers aspects such as IT strategy, policies, standards, and services. Technology governance is “the system by which the technology decisions and investments are directed and controlled” 3, and it covers aspects such as technology selection, acquisition, deployment, and maintenance.
Reference: 1: TOGAF Standard, 10th Edition, Part VI: Architecture Governance, Chapter 44: Introduction. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Series Guide: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Part II: Using the TOGAF Framework to Define and Govern Service-Oriented Architectures, Chapter 5: Technology Governance.
Question #14
What can architects present to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture?
- A . Solutions and Applications
- B . Alternatives and Trade-offs
- C . Business Scenarios and Business Models
- D . Architecture Views and Architecture Viewpoints
Correct Answer: D
D
Explanation:
According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system from the perspective of a related set of concerns1. It consists of one or more architecture models that demonstrate how the system addresses the stakeholder concerns1.
An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1. It defines the perspective, scope, notation, and techniques for creating an architecture view of a system1.
Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture, because23:
o Architecture views and viewpoints help to communicate and visualize the architecture in a way that is meaningful and relevant to different stakeholders, addressing their specific interests and needs.
o Architecture views and viewpoints help to elicit and validate the stakeholder concerns and requirements, ensuring that they are aligned with the business goals and objectives, and that they are consistent and feasible within the architecture context.
o Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs among the stakeholder concerns and requirements,
ensuring that they are balanced and prioritized in the architecture design and decision-making.
o Architecture views and viewpoints help to demonstrate and verify the value and benefits of the architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture outcome and governance.
Reference:
1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders
2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an Architecture Framework?
3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section
D
Explanation:
According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system from the perspective of a related set of concerns1. It consists of one or more architecture models that demonstrate how the system addresses the stakeholder concerns1.
An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1. It defines the perspective, scope, notation, and techniques for creating an architecture view of a system1.
Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture, because23:
o Architecture views and viewpoints help to communicate and visualize the architecture in a way that is meaningful and relevant to different stakeholders, addressing their specific interests and needs.
o Architecture views and viewpoints help to elicit and validate the stakeholder concerns and requirements, ensuring that they are aligned with the business goals and objectives, and that they are consistent and feasible within the architecture context.
o Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs among the stakeholder concerns and requirements,
ensuring that they are balanced and prioritized in the architecture design and decision-making.
o Architecture views and viewpoints help to demonstrate and verify the value and benefits of the architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture outcome and governance.
Reference:
1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders
2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an Architecture Framework?
3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section
Question #14
What can architects present to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture?
- A . Solutions and Applications
- B . Alternatives and Trade-offs
- C . Business Scenarios and Business Models
- D . Architecture Views and Architecture Viewpoints
Correct Answer: D
D
Explanation:
According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system from the perspective of a related set of concerns1. It consists of one or more architecture models that demonstrate how the system addresses the stakeholder concerns1.
An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1. It defines the perspective, scope, notation, and techniques for creating an architecture view of a system1.
Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture, because23:
o Architecture views and viewpoints help to communicate and visualize the architecture in a way that is meaningful and relevant to different stakeholders, addressing their specific interests and needs.
o Architecture views and viewpoints help to elicit and validate the stakeholder concerns and requirements, ensuring that they are aligned with the business goals and objectives, and that they are consistent and feasible within the architecture context.
o Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs among the stakeholder concerns and requirements,
ensuring that they are balanced and prioritized in the architecture design and decision-making.
o Architecture views and viewpoints help to demonstrate and verify the value and benefits of the architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture outcome and governance.
Reference:
1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders
2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an Architecture Framework?
3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section
D
Explanation:
According to the TOGAF Standard, Version 9.2, an architecture view is a representation of a system from the perspective of a related set of concerns1. It consists of one or more architecture models that demonstrate how the system addresses the stakeholder concerns1.
An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1. It defines the perspective, scope, notation, and techniques for creating an architecture view of a system1.
Architects can present architecture views and viewpoints to stakeholders to extract hidden agendas, principles, and requirements that could impact the final Target Architecture, because23:
o Architecture views and viewpoints help to communicate and visualize the architecture in a way that is meaningful and relevant to different stakeholders, addressing their specific interests and needs.
o Architecture views and viewpoints help to elicit and validate the stakeholder concerns and requirements, ensuring that they are aligned with the business goals and objectives, and that they are consistent and feasible within the architecture context.
o Architecture views and viewpoints help to identify and resolve any conflicts, gaps, or trade-offs among the stakeholder concerns and requirements,
ensuring that they are balanced and prioritized in the architecture design and decision-making.
o Architecture views and viewpoints help to demonstrate and verify the value and benefits of the architecture to the stakeholders, ensuring that they are satisfied and committed to the architecture outcome and governance.
Reference:
1: The TOGAF Standard, Version 9.2, Chapter 22: Architecture Views, Viewpoints, and Stakeholders
2: The TOGAF Standard, Version 9.2, Chapter 4: Introduction to Part II, Section 4.2: What is an Architecture Framework?
3: The TOGAF Standard, Version 9.2, Chapter 31: Architectural Artifacts, Section
Question #16
Consider the following statements
1 A whole corporation or a division of a corporation
2 A government agency or a single government department
3 Partnerships and alliances of businesses working together such as a consortium or supply chain
What are those examples of according to the TOGAF Standard?
- A . Enterprises
- B . Business Units
- C . Organizations
- D . Architectures Scopes
Correct Answer: A
A
Explanation:
Enterprises are examples of the scope of an architecture according to the TOGAF Standard. An enterprise is defined as any collection of organizations that has a common set of goals and/or a single bottom line. Enterprises can be whole corporations or divisions of a corporation, government agencies or single government departments, partnerships and alliances of businesses working together, etc.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.1 Core Concepts.
A
Explanation:
Enterprises are examples of the scope of an architecture according to the TOGAF Standard. An enterprise is defined as any collection of organizations that has a common set of goals and/or a single bottom line. Enterprises can be whole corporations or divisions of a corporation, government agencies or single government departments, partnerships and alliances of businesses working together, etc.
Reference: The TOGAF® Standard | The Open Group Website, Section 2.1 Core Concepts.
Question #17
Complete the sentence. The architecture domains that are considered by the TOGAF standard as subsets of an overall enterprise architecture are Business, Technology,
- A . Logical and Physical
- B . Information and Data
- C . Capability and Segment
- D . Application and Data
Correct Answer: D
D
Explanation:
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.
Reference: 1: The TOGAF Standard, Version 9.2 – Definitions 2: TOGAF® Standard ― Introduction – Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 – Applying the ADM Across the Architecture Landscape]
D
Explanation:
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.
Reference: 1: The TOGAF Standard, Version 9.2 – Definitions 2: TOGAF® Standard ― Introduction – Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 – Applying the ADM Across the Architecture Landscape]
Question #17
Complete the sentence. The architecture domains that are considered by the TOGAF standard as subsets of an overall enterprise architecture are Business, Technology,
- A . Logical and Physical
- B . Information and Data
- C . Capability and Segment
- D . Application and Data
Correct Answer: D
D
Explanation:
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.
Reference: 1: The TOGAF Standard, Version 9.2 – Definitions 2: TOGAF® Standard ― Introduction – Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 – Applying the ADM Across the Architecture Landscape]
D
Explanation:
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.
Reference: 1: The TOGAF Standard, Version 9.2 – Definitions 2: TOGAF® Standard ― Introduction – Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 – Applying the ADM Across the Architecture Landscape]
Question #17
Complete the sentence. The architecture domains that are considered by the TOGAF standard as subsets of an overall enterprise architecture are Business, Technology,
- A . Logical and Physical
- B . Information and Data
- C . Capability and Segment
- D . Application and Data
Correct Answer: D
D
Explanation:
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.
Reference: 1: The TOGAF Standard, Version 9.2 – Definitions 2: TOGAF® Standard ― Introduction – Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 – Applying the ADM Across the Architecture Landscape]
D
Explanation:
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.
Reference: 1: The TOGAF Standard, Version 9.2 – Definitions 2: TOGAF® Standard ― Introduction – Definitions 3: [Logical vs Physical Architecture] 4: [Information Architecture vs Data Architecture] 5: [The TOGAF Standard, Version 9.2 – Applying the ADM Across the Architecture Landscape]
Question #20
What is the purpose of the Preliminary Phase?
- A . Developing an Enterprise Architecture Capability.
- B . Describing the target architecture.
- C . Defining the Enterprise Strategy.
- D . Identifying the stakeholders and their requirements.
Correct Answer: A
A
Explanation:
An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2.
The Preliminary Phase involves the following activities1:
• Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture
• Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools
• Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise
• Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work
• Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools
• Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization
• Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization
The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1.
Reference: 1: Preliminary Phase 2: Enterprise Architecture Capability
A
Explanation:
An Enterprise Architecture Capability is the ability of the organization to perform effective and efficient architecture work, including the definition, governance, and management of its architectures2.
The Preliminary Phase involves the following activities1:
• Reviewing the organizational context, scope, and drivers for conducting Enterprise Architecture
• Establishing the Architecture Capability desired by the organization, including the maturity level, roles, responsibilities, processes, and tools
• Defining and establishing the Organizational Model for Enterprise Architecture, which describes how the architecture function is organized and integrated within the enterprise
• Defining and establishing the Architecture Governance framework, which provides the mechanisms for ensuring the quality, consistency, and compliance of the architecture work
• Selecting and implementing the tools that support the Architecture Capability, such as repositories, modeling tools, and communication tools
• Defining the Architecture Principles that will guide and constrain the architecture work, based on the business principles, goals, and drivers of the organization
• Defining the Organization-Specific Architecture Framework, which is an adaptation of the generic TOGAF ADM to suit the specific requirements, standards, and practices of the organization
The Preliminary Phase is essential for preparing the organization for the successful development and implementation of its architectures, as well as for ensuring the alignment of the architecture work with the business strategy and objectives1.
Reference: 1: Preliminary Phase 2: Enterprise Architecture Capability