OGEA-103 TOGAF 10 EA Combined Part 1 & 2 Practice Questions

A Technology Architecture Reference Model (or a set of architecture patterns) is the ideal artifact for this purpose. It is used to define standardized approaches, patterns, and technologies for solving recurring problems. In this case, it would define the standard patterns for service-to-service communication (e.g., REST vs. messaging queue), service discovery mechanisms, and security token formats, ensuring consistency across all new microservices.

An Architecture Contract is the formal agreement between the development partners (the project team) and the architecture sponsors (the Architecture Board/function) on the deliverables, quality, and fitness-for-purpose of an architecture. It is the primary governance mechanism used in Phase G to ensure compliance. In this scenario, the contract would be reviewed, and the non-compliance would trigger a defined process for remediation or formal dispensation.

Requirements Management is the continuous process that operates at the center of the ADM graphic. It ensures that all architecture requirements—whether from business, technical, or other sources—are identified, stored, prioritized, and managed throughout all phases of the ADM cycle.

The Architecture Capability Framework, a part of the TOGAF standard, provides guidelines for establishing and operating an architecture function. This includes the Architecture Skills Framework, which defines a set of roles (e.g., Enterprise Architect, Solution Architect), skills, and proficiency levels needed to build a competent and effective architecture team.

This is the core distinction. An Architecture Building Block (ABB) defines the required functionality and interfaces logically, without specifying a product (e.g., 'a customer relationship management service'). A Solution Building Block (SBB) is a concrete implementation of one or more ABBs, often a specific product or custom-built component (e.g., 'Salesforce Enterprise Edition' or 'a custom Java-based CRM module'). ABBs define 'what' is needed, and SBBs define 'how' it will be implemented.

The most effective evolution is to shift the focus from technical compliance to demonstrating business value. Value-stream mapping is a technique used in Business Architecture (Phase B) that directly connects activities, including architecture work, to the value delivered to the customer and the business. This creates a clear line of sight from EA efforts to the financial metrics and business outcomes that executive leadership cares about. Stricter compliance, more detailed artifacts, or new tools are internally focused and do not inherently translate EA activities into business terms.

In a federated model, the central Architecture Board's role is to enable and guide, not command and control. Defining 'guardrails' (enterprise standards, principles, and reference architectures) allows business units to maintain autonomy and agility while ensuring alignment and interoperability. The board also serves as the final point of escalation for disputes that cannot be resolved at lower levels, maintaining overall enterprise coherence.

In a federated model, the central Architecture Board's role is to enable and guide, not command and control. Defining 'guardrails' (enterprise standards, principles, and reference architectures) allows business units to maintain autonomy and agility while ensuring alignment and interoperability. The board also serves as the final point of escalation for disputes that cannot be resolved at lower levels, maintaining overall enterprise coherence.

This statement is false. The Enterprise Continuum is a conceptual model or a 'virtual repository' used to classify architecture and solution artifacts. It provides a method for understanding the relationships between different types of assets, from generic to specific. The Architecture Repository is the physical system or location where these assets are stored and managed.

This approach provides the best balance. A federated model decentralizes decision-making while maintaining central oversight. 'Guardrails' (e.g., security standards, approved technologies) provide clear boundaries for autonomous teams. Reusable SBBs accelerate development and ensure consistency. Embedding architects in teams facilitates continuous, real-time guidance, making governance a collaborative enabler rather than a gatekeeping bottleneck. This aligns with modern agile and DevOps practices.

A Value Stream/Application matrix is the most suitable artifact for this purpose. It explicitly maps business value streams (like 'Client Onboarding') to the applications that support them. This tabular format makes it easy to visualize which applications support each stage of the value stream and to identify overlaps or redundancies where multiple applications support the same function. While the diagram shows some relationships, the matrix provides a more systematic and comprehensive view for analysis.