OGEA-103 Exam Questions Tutorials

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. 

According to the TOGAF Standard, 10th Edition, documents which are under development and have not undergone any formal review and approval process are called draft documents, while documents which have been reviewed and approved are called approved documents 1. Draft documents are typically marked with a version number of 0.x, indicating that they are incomplete or provisional. Approved documents are typically marked with a version number of 1.0 or higher, indicating that they have been finalized and authorized. The other options are not correct, as they are not the terms used by the TOGAF Standard to distinguish between documents under development and documents that have been reviewed and approved. The terms “finalized”, “concept”, “deliverable”, and “Version 0.1” and “Version 1.0” are not specific to the TOGAF Standard, and they may have different meanings or interpretations in different contexts. References: 1: TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 7: Applying Iteration to the ADM, Section 7.2.3 Document Categorization.

One of the key responsibilities of an Architecture Board within the context of TOGAF is to achieve consistency between sub-architectures. This board is typically responsible for overseeing the development and maintenance of the enterprise architecture, ensuring that it aligns with the organization's overall strategy and objectives. They play a critical role in ensuring that all sub-architectures (like Business Architecture, Data Architecture, Application Architecture, and Technology Architecture) work together cohesively and support the overall enterprise architecture vision and strategy.

According to the TOGAF Standard, 10th Edition, the rationale section of the architecture principles template should highlight the business benefits of adhering to the principle, as well as the business risks of not adhering to it 1. The rationale section should explain the reasoning behind the principle, and provide evidence or arguments to support it. The rationale section should also link the principle to the business drivers, goals, and objectives of the enterprise, and show how the principle contributes to the value and success of the enterprise. The other optionsare not correct, as they have different purposes in the architecture principles template. The name section should provide a short and memorable name for the principle, such as “Information is an Asset” or “Business Continuity” 1. The statement section should provide a concise and formal statement of the principle, such as “The enterprise’s information is recognized as a core asset, and is managed accordingly” or “The enterprise’s ability to provide critical services and products must be maintained in the event of a disaster” 1. The implications section should identify the impact of the principle on the enterprise, such as the changes, costs, benefits, and risks that may result from applying or violating the principle 1. References: 1: TOGAF Standard, 10th Edition, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles, Section 23.3 Developing Architecture Principles.