OGEA-103 Sample Questions & Answers

A well-formed Architecture Principle includes a clear statement, a rationale explaining the business driver, and implications outlining the consequences and required actions. This option provides all three components. It states the principle ('Data is protected'), the reason ('comply with HIPAA'), and the practical impact ('implement RBAC and encryption'). The other options are either too vague ('Secure the data'), state a requirement without context ('HIPAA compliant'), or are too prescriptive for a principle ('Use encryption').

The Enterprise Continuum classifies assets from generic to specific. Foundation Architectures are the most generic level and include industry-standard frameworks and models like ITIL, COBIT, and the TOGAF Technical Reference Model (TRM). These assets provide a generic foundation that can be specialized for industries, common systems, and finally, the specific organization.

The Conceptual Data Model identifies the high-level data entities and their relationships, which is a key starting point for Data Architecture. The Logical Data Model then elaborates on this by adding attributes to the entities and defining the relationships more formally, independent of any specific database technology. These two artifacts are fundamental to developing the Data Architecture in Phase C.

The Conceptual Data Model identifies the high-level data entities and their relationships, which is a key starting point for Data Architecture. The Logical Data Model then elaborates on this by adding attributes to the entities and defining the relationships more formally, independent of any specific database technology. These two artifacts are fundamental to developing the Data Architecture in Phase C.

The primary role of governance is not to rigidly enforce rules, but to manage change in a controlled manner. The first step is to perform an impact assessment. This involves understanding the reasons for the change, evaluating its effect on the Target Architecture, business goals, costs, risks, and other projects. Based on this assessment, an informed decision can be made to approve, reject, or modify the request, possibly through a formal dispensation process.

For a new EA capability, especially one with a technical bias, the most critical initial goal is to establish credibility and demonstrate value in business terms. Engaging with stakeholders to understand their goals and then delivering a tangible result on a high-impact project proves the worth of EA. This builds political capital and secures buy-in for future, more comprehensive architecture work. Focusing solely on technical artifacts like a TRM or an overly ambitious maturity assessment without first delivering business value risks the capability being seen as an irrelevant 'ivory tower'.

The stakeholder map is a crucial artifact for stakeholder management. Its purpose is to identify all relevant stakeholders, analyze their level of influence and interest in the project, and understand their key concerns and expectations. This analysis informs the communication plan and helps ensure the architecture addresses the right problems and gains the necessary support for success.

Transition Architectures, often referred to as plateaus, are formal descriptions of the enterprise at intermediate points in time between the Baseline and Target Architectures. They are created in Phase E (Opportunities & Solutions) and used in Phase F (Migration Planning) to group work packages into manageable stages that deliver incremental value. This allows for a phased migration approach.

This statement is false. The TOGAF standard defines the logical structure of the Architecture Repository, but it does not mandate a specific implementation. An organization's repository can be a federation of different tools and repositories, such as modeling tools, document management systems, and configuration management databases (CMDBs). The key is that the components are linked and managed coherently.

In most maturity models (like CMMI), 'Defined' (often Level 2 or 3 depending on the model) is characterized by having standardized, documented processes. However, the key differentiator is that at this level, adherence to these processes may be inconsistent, and they are not yet quantitatively managed or optimized. The scenario describes documented processes that are not followed consistently, which aligns perfectly with the 'Defined' level, where the process is established but not yet institutionalized across the organization.

The TOGAF ADM separates these phases to ensure a logical progression. The Information Systems Architectures (Data and Application) define the 'what' and 'how' from a logical perspective. The Technology Architecture then defines the underlying 'where'—the technology platforms that will host them. Combining them risks having application-specific technology choices (e.g., a database favored by one application vendor) dictate the technology landscape, undermining the goal of creating a standardized, strategic technology platform for the entire enterprise.