OG0-093 Sample Questions & Answers

The Preliminary Phase of the ADM is focused on defining the framework and methodologies to be used for the architecture development effort. This includes establishing the Architecture Capability, defining architecture principles, and customizing TOGAF for the specific organizational context. Defining application systems happens in Phase C, work packages are defined in Phase F, baseline architecture is developed in Phase A, and stakeholder identification occurs across multiple phases.

When creating views for a particular architecture, TOGAF recommends first referring to existing libraries of viewpoints to identify one for reuse rather than creating new ones from scratch. This promotes consistency, saves time, and leverages proven approaches. Architecture views should be based on established viewpoints that have been tested and validated. Developing target views first, ensuring completeness, and designing custom viewpoints are later steps in the process.

Foundation Architectures in the Architecture Continuum contain the most reusable architecture elements because they represent generic technology building blocks and architectural patterns that can be applied across multiple organizations and industries. They provide the broadest applicability and highest level of reuse potential. Common Systems Architectures are more specific, Industry Architectures are tailored to particular sectors, and Organization-Specific Architectures are the least reusable as they are customized for specific organizations.

The Architecture Vision document provides a high-level description of both the baseline and target architectures, serving as the key deliverable of Phase A that articulates the value proposition and expected outcomes of the proposed architecture work. It sets the vision and scope for the architecture development effort and communicates the key benefits to stakeholders. It is not a detailed implementation schedule, not individual change increments (that would be a roadmap), not rules and guidelines (that would be principles), and not a development agreement (that would be a Statement of Architecture Work).

The Enterprise Continuum is used to structure reusable architecture and solution assets by providing a classification scheme that organizes architectural artifacts from generic to organization-specific. It helps architects leverage existing assets and promotes reuse by categorizing architectures, models, patterns, and other artifacts in a structured way. It does not identify business requirements (that is done through stakeholder analysis), does not describe stakeholder concerns (that is done through viewpoints), does not provide continuous monitoring, and does not coordinate with other management frameworks.

A Request for Architecture Work is the document sent from the sponsoring organization to the architecture organization to trigger the start of an ADM cycle. This document formally initiates the architecture development process by requesting that architecture work be undertaken. The Architecture Vision is created as a result of the request, Statement of Architecture Work defines the work to be done, Architecture Contract governs the implementation, and Architecture Definition Document contains the detailed architecture.

Architecture Governance is the practice by which enterprise architectures are controlled at an enterprise-wide level, including the processes, procedures, and responsibilities for making architecture decisions and ensuring compliance. It provides the framework for decision-making and ensures that architectural developments support business objectives. It is not about information lifecycle management, not a categorization mechanism (that is the Enterprise Continuum), not a framework for operations, and not a method for designing systems.

The Reference Library within the Architecture Repository holds best practice or template materials, including guidelines, templates, patterns, and other reference materials that can be used to construct architectures. This component provides reusable assets and proven approaches for architecture development. The Architecture Metamodel defines the structure, Architecture Landscape contains actual architectures, Governance Log tracks decisions, and Architecture Capability is the organizational ability to do architecture work.

According to TOGAF, allocating resources for architecture projects is NOT a responsibility of an Architecture Board. Resource allocation is typically a management function performed by project sponsors or portfolio management bodies. The Architecture Board is responsible for decision making for architectural changes, producing governance materials, improving the maturity of architecture discipline, and enforcing architecture compliance, but not for budget and resource allocation decisions.

The purpose of a Compliance Assessment is to govern the architecture throughout its implementation process by ensuring that implementation projects conform to the defined architecture and comply with architectural principles and standards. This ongoing assessment provides architectural oversight during implementation phases. It does not show progression from baseline to target (that is a roadmap), does not focus on communication timing, and does not provide high-level architecture views.