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

An Enterprise Architecture Capability is the organizational ability to develop, maintain, govern, and sustain Enterprise Architecture as an ongoing business capability. It includes governance structures, roles, responsibilities, processes, methods, skills, tools, repositories, and supporting resources necessary to enable architecture-driven change across the enterprise.

TOGAF explains that an Architecture Capability allows an organization to use architecture effectively to govern transformation and support strategic business objectives. It is much broader than simply maintaining architecture artifacts or following principles.

Option A describes the Enterprise Continuum. Option B relates to Architecture Principles. Option C describes risk management concepts.

Therefore, the correct answer is D .

===========

Gap Analysis in TOGAF is a technique used to compare the baseline architecture (current state) with the target architecture (future desired state). The output is a set of gaps, representing what is missing or what must change to move from baseline to target. These gaps help validate that the target architecture is adequate: by identifying what is not addressed, architects can ensure that all required functionality, constraints, and transformation paths are captured. In effect, Gap Analysis validates the architecture by exposing omissions, inconsistencies, or unmet requirements between what is and what should be. It is not primarily about defining service levels, nonfunctional requirements, or quality metrics (though it helps inform those). Rather, its main role is in validating and guiding closure of architectural gaps.

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

TOGAF adopts a formal risk management perspective aligned with widely accepted enterprise risk management practices. Within the ADM, risks are identified, analyzed, treated, and monitored throughout all phases, particularly during Architecture Governance and Implementation Governance.

TOGAF explicitly distinguishes between:

Initial Risk:The level of risk identified before any mitigation actions are applied. This represents the inherent exposure associated with an architecture decision, solution, or implementation approach.

Residual Risk:The level of risk that remains after mitigation measures have been applied. This residual risk must be explicitly accepted, monitored, or further treated by governance bodies.

Why Option D is correct:

TOGAF requires both Initial and Residual risks to be documented and monitored to ensure informed decision-making and effective governance throughout the ADM lifecycle.

Why the other options are incorrect:

A. Technical and Financial level: These are categories of risk, not the two monitoring levels defined by TOGAF.

B. Mitigated and Revised level: These terms are not used as formal risk levels in TOGAF.

C. Operational and Strategic level: These describe business risk domains, not TOGAF-defined monitoring levels.

Authoritative TOGAF References:

TOGAF Risk Management

TOGAF Architecture Governance

TOGAF ADM Guidelines and Techniques – Risk Management

============

 In the ADM documents which are under development and have not undergone any formal review and approval process are called “draft”. This indicates that they are subject to change and refinement as the architecture development progresses. Reference: The TOGAF® Standard | The Open Group Website, Section 4.2.5 Architecture Deliverables.