The Open Group OGEA-103 Practice Test - Questions Answers, Page 4

The class of information known as the Reference Library within the Architecture Repository contains guidelines and templates used to create new architectures. The Reference Library provides a set of resources that can be leveraged or customized for specific architecture development purposes. It includes generic building blocks, patterns, models, standards, frameworks, methods, techniques, best practices, etc. Reference: The TOGAF® Standard | The Open Group Website, Section 2.4 Architecture Repository.

A set of architecture principles that cover every situation perceived meets the recommended criteria of completeness. Completeness is one of the six criteria that should be applied when developing or assessing architecture principles. Completeness means that there are no gaps or overlaps in the coverage of principles across all relevant aspects of the enterprise’s architecture. Reference: The TOGAF® Standard | The Open Group Website, Section 3.3.7 Architecture Principles.

A content metamodel is a formal structure that defines the types of entities and relationshipsthat are used to capture, store, filter, query, and represent architectural information in a waythat 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 structurearchitectural information, but rather to understand the stakeholder needs and concerns.An architecture framework is a set of principles, guidelines, standards, and tools that provide acommon structure and methodology for developing architectures4. It is not used to structurearchitectural information, but rather to guide the architecture development process and ensurealignment 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 developmentand governance. It is not used to structure architectural information, but rather to provideaccess, security, and version control for the architecture content.

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.

The purpose of the Architecture Roadmap is to provide a high-level view of how the Baseline Architecture will transition to the Target Architecture over time. It lists work packages on a timeline showing progress towards the Target Architecture, as well as dependencies, risks, and benefits. The Architecture Roadmap forms part of the Implementation and Migration Plan and guides the execution of the architecture projects. Reference: https://pubs.opengroup.org/architecture/togaf9- doc/arch/chap20.html

The Request for Architecture Work is a deliverable that is sent from the sponsor and triggers the start of an architecture development cycle. It defines the scope, budget, schedule, and deliverables for a specific architecture project. The Statement of Architecture Work is a deliverable that is produced by the architect and defines the approach and resources needed to complete an architecture project. It forms the basis of a contractual agreement between the sponsor and the architecture organization.

The Architecture Principles are a deliverable that is produced by the architect and defines the general rules and guidelines for the architecture work. They reflect the business principles, business goals, and business drivers of the organization. The Architecture Requirements Specification is a deliverable that is produced by the architect and defines the requirements that govern the architecture work. It covers both functional and non-functional requirements as well as constraints and assumptions.

An Architecture Board is an executive-level group responsible for the review and maintenanceof the strategic architecture and all of its sub-architectures1.It is a key element in a successfulArchitecture Governance strategy2.An Architecture Board is typically made responsible, and accountable, for achieving some or allof the following goals2:Providing the basis for all decision-making with regard to the architecturesConsistency between sub-architecturesEstablishing targets for re-use of componentsFlexibility of the Enterprise Architecture: To meet changing business needs To leverage newtechnologiesEnforcement of Architecture ComplianceImproving the maturity level of architecture discipline within the organizationEnsuring that the discipline of architecture-based development is adoptedSupporting a visible escalation capability for out-of-bounds decisions.

Therefore, the correct answer is option D, which captures one of the goals of an ArchitectureBoard as stated in the TOGAF Standard, Version 9.22.Option A is incorrect, because conducting assessments of the maturity level of architecturediscipline within the organization is not a direct responsibility of an Architecture Board, butrather a part of the Architecture Capability Framework3.Option B is incorrect, because allocating resources for architecture projects is not a directresponsibility of an Architecture Board, but rather a part of the Architecture GovernanceFramework4.Option C is incorrect, because creating the Statement of Architecture Work is not a directresponsibility of an Architecture Board, but rather a part of the Architecture DevelopmentMethod5.Reference:1: Architecture Board - The Open Group32: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - ArchitectureBoard3: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - ArchitectureCapability Framework4: TOGAF Standard, Version 9.2 - Part VI: Architecture Governance Framework - ArchitectureGovernance Framework5: TOGAF Standard, Version 9.2 - Part II: Architecture Development Method - Phase A:Architecture Vision