Question 1

Which phase of the ADM has the purpose to develop an Enterprise Architecture Capability?

Accepted Answer

According to the TOGAF Standard, 10th Edition, the Preliminary Phase of
the Architecture Development Method (ADM) has the purpose to develop an Enterprise Architecture Capability 1. An Enterprise Architecture Capability is the ability
of the organization to perform the activities and tasks related to Enterprise Architecture, such as defining the scope, principles, vision, governance, and
stakeholders of the architecture. The Preliminary Phase also establishes the architecture framework, the architecture repository, the architecture tools, and the
architecture team 1. The other options are not correct, as they have different purposes in the ADM. Phase G: Implementation Governance has the purpose to
ensure that the implementation projects conform to the target architecture 2. Phase A: Architecture Vision has the purpose to define the scope, stakeholders,
business drivers, and objectives of the architecture project 3. Phase B: Business Architecture has the purpose to describe the baseline and target business
architecture, and to identify the gaps between them . References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6:
Preliminary Phase. 2: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 18: Phase G: Implementation Governance. 3: TOGAF
Standard, 10th Edition, Part II: Architecture Development Method, Chapter 12: Phase A: Architecture Vision. : TOGAF Standard, 10th Edition, Part II: Architecture
Development Method, Chapter 13: Phase B: Business Architecture.

Question 2

Which of the following best describes a purpose of the Gap Analysis technique?

Accepted Answer

Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One
of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out,or not yet defined in the Target Architecture.
Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks.

Question 3

What is present in all phases within the ADM and should be identified, classified and mitigated before starting a transformation effort?

Accepted Answer

According to the TOGAF Standard, 10th Edition, risk is present in all phases within the Architecture Development Method (ADM), and it should be identified,
classified, and mitigated before starting a transformation effort 1. Risk is defined as ??the effect of uncertainty on objectives?? 2, and it can have positive or
negative impacts on the architecture project. Risk management is a technique that helps to assess and address the potential risks that may affect the achievement
of the architecture objectives, and to balance the trade-offs between opportunities and threats. Risk management is applied throughout the ADM cycle, from the
Preliminary Phase to the Requirements Management Phase, and it is integrated with other techniques, such as stakeholder management, business transformation
readiness assessment, gap analysis, and migration planning 1. The other options are not correct, as they are not present in all phases within the ADM, and they
are not necessarily identified, classified, and mitigated before starting a transformation effort. Budgetary constraints are the limitations on the financial resources
available for the architecture project, and they are usually considered in Phase E: Opportunities and Solutions, and Phase F: Migration Planning 3. Schedule
constraints are the limitations on the time available for the architecture project, and they are also usually considered in Phase E and F 3. Information gaps are the
missing or incomplete data or knowledge that may affect the architecture project, and they are usually identified in Phase B: Business Architecture, Phase C:
Information Systems Architecture, and Phase D: Technology Architecture . References: 1: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and
Techniques, Chapter 32: Risk Management. 2: TOGAF Standard, 10th Edition, Part I: Introduction, Chapter 3: Definitions. 3: TOGAF Standard, 10th Edition, Part
II: Architecture Development Method, Chapter 16: Phase E: Opportunities and Solutions, and Chapter 17: PhaseF: Migration Planning. : TOGAF Standard, 10th
Edition, Part II: Architecture Development Method, Chapter 13: Phase B: Business Architecture, Chapter 14: Phase C: Information Systems Architecture, and
Chapter 15: Phase D: Technology Architecture.

Question 4

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?

Accepted Answer

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 5

Consider the illustration.
What are the items labelled A, B and C?

Accepted Answer

The illustration shows the relationship between the Enterprise Continuum, the Architecture Continuum, and the Solutions Continuum, which are key concepts in
the TOGAF framework. TheEnterprise Continuum is a view of the Architecture Repository that shows how generic foundation architectures can be leveraged and
specialized to support the requirements of an individual organization. The Architecture Continuum specifies a structured classification for architectural artifacts,
such as models, patterns, and descriptions, that can be reused and adapted across different domains and levels of abstraction. The Solutions Continuum identifies
implemented solutions that support various stages of business and IT capability evolution, such as common systems, industry solutions, and organization-specific
solutions. The illustration also shows how the architecture context and requirements are influenced by external factors, such as business drivers, stakeholders, and
standards, and how they shape the generic and specific architectures and solutions. The illustration also shows how the deployed solutions become part of the
architecture context for future iterations of the architecture development cycle. References:
•TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Architecture Repository, Section 6.2 Enterprise Continuum.
•TOGAF Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 35: Enterprise Continuum and Tools, Section 35.1 Introduction.

Question 6

Which section of the TOGAF template for Architecture Principles should highlight the requirements for carrying out the principle?

Accepted Answer

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.

/OGEA-101-exam/ (92 Q&As)
References: 2: The TOGAF Standard, Version 9.2 - Architecture Principles 3: TOGAF 8.1.1 Online - Architecture Principles 1: Architecture Principles Template

Question 7

Consider the following ADM phases objectives.
Which phase does each objective match?

Accepted Answer

? The objectives listed in the question correspond to the objectives of different phases of the TOGAF ADM (Architecture Development Method), which is a method
for developing and managing an enterprise architecture1.
? The ADM consists of nine phases, each with a specific purpose and output. The phases are1:
? Based on the above definitions, we can match each objective with the corresponding phase as follows:
References:
? 1: The TOGAF Standard, Version 9.2, Chapter 5: Architecture Development Method (ADM)
? 2: The TOGAF Standard, Version 9.2, Chapter 9: Phase C: Information Systems
Architectures
? 3: The TOGAF Standard, Version 9.2, Chapter 8: Phase B: Business Architecture
? 4: The TOGAF Standard, Version 9.2, Chapter 7: Phase A: Architecture Vision

Question 8

What are the following activities part of?
• Initial risk assessment
• Risk mitigation and residual risk assessment
• Risk monitoring

Accepted Answer

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 9

Complete the sentence The purpose of the Preliminary Phase is to ________.

Accepted Answer

The purpose of the Preliminary Phase is to architect an Enterprise Architecture Capability that meets the needs and expectations of the enterprise??s
stakeholders and supports and enables subsequent phases of architecture development and transition. This phase involves defining the scope, principles,
framework, and governance for the Enterprise Architecture Capability. Reference: The TOGAF® Standard | The Open Group Website, Section 3.2 Preliminary
Phase.

Question 10

What is used to structure architectural information in an orderly way so that it can be processed to meet stakeholder needs?

Accepted 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.
References: 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