OGEA-101 Sample Questions & Answers

Phase A is focused on establishing the vision and getting buy-in. Given the diverse and potentially conflicting interests of the CMO (customer experience) and COO (efficiency), a Stakeholder Map is essential for identifying their concerns and influence. Business Scenarios are a powerful technique used in Phase A to articulate the business requirements and value proposition in a way that resonates with different stakeholders, ensuring everyone understands and supports the vision.

This is the core distinction. Architecture Building Blocks (ABBs) are conceptual and describe the required functionality and inter-relationships (e.g., 'a customer data service'). Solution Building Blocks (SBBs) are concrete and represent the actual products, components, or systems that will be used to implement the ABBs (e.g., 'Salesforce CRM version X' or 'a custom-built microservice'). SBBs are tangible implementations of the conceptual ABBs.

Architecture Governance is not about rigidly enforcing rules but about managing the architecture in a controlled way. The correct procedure is to have a formal process to handle deviations. This involves assessing the impact of the proposed change, understanding the rationale, and making a formal decision. This could result in granting a time-limited dispensation, updating the standard, or rejecting the change.

The three types of artifacts defined by the TOGAF Architecture Content Framework are Catalogs (lists of items), Matrices (showing relationships between items), and Diagrams (graphical representations of items and their relationships).

An Architecture Viewpoint defines the perspective from which a view is created. It specifies the set of concerns and the conventions (e.g., notations, models) to be used to address those concerns. For the CFO, a 'Cost' or 'Financial' viewpoint would be selected to generate a view that highlights costs, ROI, and other financial metrics, filtering out irrelevant technical details.

The Standards Information Base (SIB) is a component of the Architecture Repository that holds the collection of standards with which new architectures must comply. This includes product standards, technical standards, and business standards. It serves as a central reference for ensuring consistency and compliance across projects.

For large, complex programs, TOGAF recommends multiple iterations across the Architecture Landscape. This involves a high-level ADM cycle to set the overall context and vision for the program, with individual projects or workstreams executing their own, more detailed ADM cycles within that context. This approach allows for effective management of complexity and interdependencies.

The statement is false. The purpose of Phase H is to establish a process for managing changes to the architecture after it has been implemented. It ensures the architecture remains fit-for-purpose over its lifecycle. The initial target architecture is defined in Phases B, C, and D.

Accessibility is a key concern for stakeholders such as students, disability services, and the university's legal department. The Stakeholder Management technique involves identifying these stakeholders, capturing their concerns (which become requirements), and ensuring the architecture addresses them. This ensures that critical non-functional requirements like accessibility are incorporated into the design from the beginning.

Organizations often use multiple frameworks. Adapting the ADM to align its processes, terminology, and deliverables with other frameworks like ITIL is a common and valid practice.

A small, agile organization might use a 'lighter' version of the ADM, while a large, highly regulated enterprise will require more formal and detailed outputs. Tailoring the ADM to the context is a key principle.

The ADM should work with, not against, an organization's existing culture and processes. It can be adapted to fit into established project lifecycle gates, funding models, and organizational structures.