The Open Group OGEA-101 TOGAF Enterprise Architecture Part 1 Exam Practice Test

Answer : B

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 . Reference:

* 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]

Answer : C

In the context of TOGAF, a stakeholder is any individual, team, or organization who has interests in, or concerns relative to, the outcome of the architecture. Concerns are those interests which pertain to any aspect of the system's functioning, development or operation, including considerations such as performance, reliability, and security1. Reference:

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

Answer : D

Answer : A

The TOGAF standard divides Enterprise Architecture into four primary architecture domains: business, data, application, and technology. These domains represent different aspects of an enterprise and how they relate to each other. The business domain defines the business strategy, governance, organization, and key business processes. The data domain describes the structure of the logical and physical data assets and data management resources. The application domain provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes. The technology domain describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. Other domains, such as motivation, security, or governance, may span across these four primary domains.Reference:

The TOGAF Standard, Version 9.2 - Core Concepts

Domains - The Open Group

TOGAF Standard --- Introduction - Definitions - The Open Group

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

TOGAF and the history of enterprise architecture | Enable Architect

Answer : D

Risk management is a generic technique that can be applied across all phases of the Architecture Development Method (ADM), as well as in the Preliminary Phase and the Requirements Management Phase2. Risk management involves the following steps1:

* Risk identification: This step involves identifying the potential risks that may affect the architecture project, such as technical, business, organizational, environmental, or legal risks. The risks can be identified through various sources, such as stakeholder interviews, workshops, surveys, checklists, historical data, or expert judgment.

* Risk classification: This step involves categorizing the risks based on their nature, source, impact, and priority. The risks can be classified according to different criteria, such as time, cost, scope, quality, security, or compliance. The classification helps in prioritizing the risks and allocating resources and efforts to address them effectively.

* Initial risk assessment: This step involves assessing the likelihood and impact of each risk, and determining the initial level of risk. The likelihood is the probability of the risk occurring, and the impact is the severity of the consequences if the risk occurs. The initial level of risk is the product of the likelihood and impact, and it indicates the urgency and importance of the risk. The initial risk assessment helps in identifying the most critical risks that need immediate attention and mitigation.

Answer : C

The Architecture Landscape is a class of information within the Architecture Repository that shows an architectural view of the building blocks that are in use within the organization today (the Baseline Architecture), as well as those that are planned for the future (the Target Architecture). The Architecture Landscape typically contains a list of the applications in use within the enterprise, along with their relationships and dependencies, as well as other relevant architectural information. The Architecture Landscape helps to identify opportunities for re-use, consolidation, or retirement of existing applications, as well as gaps or overlaps in the current or future architecture. Reference: : The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 34: Architecture Landscape : The TOGAF Standard, Version 9.2, Part VI: Architecture Capability Framework, Chapter 47: Architecture Repository

Answer : B

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 architecture3Reference: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