Free OG0-093 sample questions

Correct answer: Part VII, the Architecture Capability Framework, describes processes and skills to establish an enterprise function

Part VII of TOGAF 9, the Architecture Capability Framework, describes the processes, skills, roles, and organizational structures needed to establish and operate an enterprise architecture capability within an organization. This section provides guidance on architecture governance, skills framework, and organizational structures. Part III covers Tools and Support (not guidelines), Part I is Introduction (not Enterprise Continuum), Part VI covers Reference Models (not release management), and Part II is the ADM (not definitions and changes).

Correct answer: Phase G

Phase G (Implementation Governance) of the ADM ensures that implementation projects conform to the defined architecture through ongoing oversight and compliance checking. This phase provides architectural oversight for implementation projects to ensure they align with the Target Architecture and comply with architectural principles and standards. Phase F focuses on migration planning, Requirements Management handles requirements flow, Phase H focuses on change management, and Phase D develops the Technology Architecture.

Correct answer: stores requirements and manages their flow into relevant ADM phases

The Requirements Management Phase stores requirements and manages their flow into relevant ADM phases throughout the architecture development process. This phase acts as a central hub that captures, stores, prioritizes, and manages requirements as they are identified and refined across all ADM phases. It does not dispose of requirements, does not generate new requirements itself, is not just a prioritization process, and does more than just resolve conflicts between phases.

Correct answer: To define the framework and methodologies to be used

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.

Correct answer: Refer to existing libraries of viewpoints, to identify one for re-use

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.

Correct answer: Foundation Architectures

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.

Correct answer: A high level description of the baseline and target architectures

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).

Correct answer: It is used to structure re-usable architecture and solution assets

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.

Correct answer: Request for Architecture Work

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.

Correct answer: The practice by which enterprise architectures are controlled at an enterprise-wide level

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.