OG0-091 Practice Exam Questions with Answers TOGAF 9 Part 1 Certification

To determine service levels for the architecture

To establish quality metrics for the architecture

To identify commercial building blocks to be purchased

To identify missing functions

To validate nonfunctional requirements

To define the capabilities of the organization

To communicate the technical readiness of the project

To evaluate the readiness of the organization to undergo change

To produce a new Request for Architecture Work

TOGAF Guidelines and Techniques

TOGAF Recommended

TOGAF Supporting

TOGAF Extension

It provides for effective communication of the end architecture project to the stakeholders

It is sent from the sponsor and triggers the start of an architecture development cycle

It contains an assessment of the current architecture requirements

It lists work packages on a timeline showing progress towards the Target Architecture

It forms the basis of a contractual agreement between the sponsor and the architecture organization

Business Transformation Readiness Assessment

Business Value Assessment Technique

Capability-Based Planning

Communications and Stakeholder Management

Gap Analysis

Capability Assessment

Change Request

Requirements Impact Analysis

Statement of Architecture Work

Standards Information Base

Enterprise Continuum

Governance Log

Architecture Landscape

Reference Library

To define and plan an enterprise architecture transformation based on Capability-Based Planning

To develop a set of general rules and guidelines for the architecture being developed

To develop a set of security guidelines for the architecture being developed

To help identify and understand the business requirements that an architecture must address

To identify and mitigate the risks when implementing an architecture project

Architecture Change Management

Implementation governance

Migration planning

Preliminary Phase

Requirements Management

Phase D

Phase E

Phase F

Phase G

Phase H

establish quality parameters for the architecture

identify potential missing or overlapping functions

validate nonfunctional requirements

identify commercial building blocks to be purchased

determine the required service levels for the architecture

deliverable

matrix

building block

diagram

catalog

To ensure that architecture information is communicated to the right stakeholders at the right time

To evangelize the architecture to the end user community

To govern the architecture through to implementation

To keep the Architecture Review Board informed of changes to the architecture

To show progression of change from the Baseline Architecture to the Target Architecture

Part II: Architecture Development Method

Part III: ADM Guidelines and Techniques

Part IV: Architecture Content Framework

Part VI: TOGAF Reference Models

Part VII: Architecture Capability Framework

Common Systems Solutions

Strategic Solutions

Industry Solutions

Organization-Specific Solutions

Foundation Solutions

Metamodel

Architecture Viewpoint

Work Package

Architecture Framework

Deliverable

The artifacts are transformed into solution architectures

The artifacts become increasingly product focused

The artifacts become increasingly generic and re-usable

The artifacts evolve from generic architectures to organization-specific architectures

The artifacts evolve from common systems architectures to foundation architectures

It is used to develop requirements for Transition Architectures that deliver business value

It is used to dispose of, address and prioritize architecture requirements

It is used to establish requirements for Phase A

It is used to manage architecture requirements throughout the ADM cycle

It is used to review business requirements

Organizational Metamodel, Architecture Capability, Architecture Landscape, Best Practices, Reference Library, Compliance Strategy

Architecture Metamodel, Organizational Capability Model, Application Landscape, SIB, Reference Library, Governance Model

Business Metamodel, Architecture Capability, Architecture Landscape, SIB, Reference Library, Governance Log

Architecture Metamodel, Architecture Capability, Architecture Landscape, SIB, Reference Library, Governance Log

Architecture governance

Corporate governance

IT governance

Technology governance

The program management office

Name

Statement of Principle

Rationale

Enforcement Policy

Implications

Rational, Explained, Precise, Stated, Identifiable

Comprehensive, Future proof, Short, Concise, Consistent

Open, Enabling, Flexible, Agile, Dynamic

Stable, Understandable, Complete, Robust, Consistent

It highlights areas of stakeholder concern

It highlights the impacts of change

It highlights services that are yet to be developed

It highlights services that are available

It highlights different viewpoints

To show the evolution of deliverables

To permit adaptation as required

To enable use with the Architecture Content Framework

To support change management

activity model, perspective

viewpoint, requirements

view, concerns

Node Connectivity Diagram, interconnections

Architecture trade-off analysis, constraints

To ensure that architecture information is communicated to the right stakeholders at the right time

To govern the architecture throughout its implementation process

To provide a high-level view of the end architecture product

To show progression of change from the Baseline Architecture to the Target Architecture

Authoring the Architecture Definition Document

Ensuring the compliance of individual projects to the enterprise architecture

Controlling the implementation and deployment organizations

Authoring the Communications Plan for a given architecture project

Conducting Business Scenarios

Part I, the Enterprise Continuum, describes a model for structuring a virtual repository

Part II, the Architecture Development Method, describes the definitions of terms used in TOGAF, and the changes between versions of TOGAF

Part III, Tools and Support, describes a collection of guidelines and techniques used in the other parts of TOGAF

Part VI, TOGAF Reference Models, includes a model for release management of the TOGAF specification

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

architecture building block

architecture model

architecture vision

requirement

viewpoint

To align it closer to the business

To make the use more realistic

To move through the cycle faster

To suit the specific needs of the enterprise

Capability Architecture

Operational Architecture

Segment Architecture

Strategic Architecture

Tactical Architecture

To create a roadmap that describes the evolution of the architecture over time

To prepare a Solution Architecture for the enterprise

To define an IT Strategy that maps out the technology infrastructure

To allocate the resources needed to implement the architecture project

To articulate an Architecture Vision

observations of the CIO/CTO

opinions of the sponsors

observations of the architect staff

concerns of stakeholders

stakeholder requirements

Common Systems Architecture

Foundation Architecture

Industry Architecture

Organization Specific Architecture

Product Line Architecture

Requirements Management

Phase E

Phase F

Phase G

Phase H

The Architecture Repository

The Enterprise Continuum

The Integrated Information Infrastructure Model

The TOGAF Technical Reference Model

The organization must utilize an architecture tool in order to tailor the templates for use

It must be adapted to satisfy organization specific requirements

It can be utilized by most enterprises without further customization

It can only be used for enterprise level architecture projects

It should only be employed under the supervision of highly trained consultants

Architecture Domains

Enterprise Focus

Level of Detail

Subject Matter

Time Period

Business Scenarios

Capacity Measurement

Change Management

Measuring Business Growth

To define, scope and prioritize architecture tasks

To define the architecture principles

To develop a Target Business Architecture

To obtain management commitment for this cycle of the ADM

To prioritize work packages

Content

Context

Process Flow Control

Repository

Vision

The TOGAF Architecture Development Method mandates the use of the Technical Reference Model for large complex architecture projects

The Technical Reference Model is an integral part of the TOGAF Architecture Development Method

The Technical Reference Model should not be modified

The Technical Reference Model includes a set of graphical models and a corresponding taxonomy

The Technical Reference Model provides a direct mapping to the Zachman Framework

A checklist for compliance reviews

An evaluation tool to select vendors to conduct a proof of concept demonstration

A tool for calculating detailed cost estimates

A tool for project planning the implementation activities

A tool for selling the benefits of the proposed capability to stakeholders

Architecture Contract

Architecture Landscape

Architecture Roadmap

Requirements Impact Statement

Transition Architecture

A business planning technique that focuses on business outcomes

A business planning technique that focuses on horizontal capabilities

A business planning technique that focuses on vertical capabilities

A human resource planning technique that focuses on capable architects

Architecture Landscape

Architecture Vision

Enterprise Continuum

Governance Log

Standards Information Base

Architecture principles

Buy lists

Procurement policies

Requirements

Stakeholder concerns

is an example and should be tailored to the needs of an organization

must be used "as is" for developing comprehensive architecture models

contains several industry specific frameworks

is intended to contain the Enterprise Continuum

contains only solution building blocks

Phase D

Phase E

Phase F

Phase G

Phase H

Architecture

Metamodel

Model

Ontology

Pattern

nonconformant solution building blocks

an error has occurred and the architecture must be re-evaluated

requirements have not been properly documented

functionality that should be eliminated

a new function that must be built or procured

It is a detailed data model that can be tailored to specific industries

It is an example of a Common Systems Architecture

It is a fundamental architecture upon which more specific architectures can be based

It is a model of application components and application services software, including brokering applications

Configuration Database

library of architecture artifacts

Requirements Management System

Standards Information Base

view of the Architecture Repository

Phase E

Phase F

Phase G

Phase H

Preliminary Phase

Building Blocks

Application Platform Interfaces

Deliverables

Frameworks

Artifacts

Architecture Landscape

Architecture Metamodel

Governance Log

Reference Library

Standards Information Base

Ensuring consistency between sub-architectures

Ensuring flexibility of the enterprise architecture to meet business needs

Improving the maturity of the organization's architecture discipline

Monitoring of architecture contracts

Preparing architecture review reports

To allow an enterprise to exploit the latest trends in technology

To enable the CIO to take effective control of the business units across an enterprise

To ensure compliance in an enterprise to corporate auditing standards

To optimise an enterprise into an environment that is responsive to business needs

To provide a set of standards that all actors must adhere to within an enterprise

The development of requirements that deliver business value

The management of architecture requirements throughout the ADM cycle

The review of business requirements within the TOGAF ADM

The prioritization and disposal of architecture requirements

The development of requirements for ADM Phase A.

Existing application models

Generic business models relevant to the organization’s industry sector

Existing IT services

Generic data models relevant to the organization’s industry sector

To build a top-down, all inclusive architecture description

To enable a fast response to market changes

To verify that the method is being applied correctly

To permit the architecture domains to be integrated

To enable development of reference architectures

stakeholder

sponsor

consumer

lead architect

Application Architecture should be developed first, then Data Architecture

Application Architecture should be developed concurrently with Data Architecture

Data Architecture should be developed first, then Application Architecture

Application Architecture and Data Architecture may be developed in either sequence

To define the initial implementation plans

To define the scope, identifying stakeholders and obtaining approvals

To develop the Technology Architecture

To manage requirements throughout the ADM

To perform architectural oversight for the implementation

Opportunities and Solutions

Business Architecture

Data Architecture

Architecture Vision

Technology Architecture

Architecture governance

Corporate governance

IT governance

Portfolio management

Technology governance

An agreement between development partners and the sponsor on architecture deliverables

A description of how the new capability will address stakeholder concerns

A description of the scope and approach for completion of the architecture project

A set of quantitative statements outlining requirements on the implementation

A set of rules and guidelines to support fulfilling the mission of the organization

To create the initial version of the Architecture Roadmap

To develop a vision of the business value to be delivered by the proposed enterprise architecture

To select and implement tools to support the Architecture Capability

To obtain approval for the Statement of Architecture Work

To document the baseline architecture

Architecture Road map

Architecture Requirements Specification

Communications Plan

Implementation and Migration Plan

Implementation Governance Model

Identifying business transformation risks for an architecture project

Identifying errors in the project architecture

Identifying relationships between management frameworks

Identifying stakeholders and their concerns

Architecture Change Management

Architecture Vision

Business Architecture

Preliminary Phase

Technology Architecture

Any collection of organizations that has a common set of goals

Any corporation with more than 10,000 employees

Any organization involved in commerce

Any organization whose stock is traded

Any set of organizations based at the same geographic location

Technology Architecture

Data Architecture

Application Architecture

Business Architecture

Application Architecture

Business Architecture

Data Architecture

Technology Architecture

Building Block

Catalog

Diagram

Matrix

Deliverable

To confirm the ability of the enterprise to undergo change

To demonstrate how stakeholder concerns are addressed in the Business Architecture

To develop a Target Technology Architecture to support the business

To finalize the Architecture Vision and Architecture Definition documents

To maximize the business value from the architecture

Architecture principles

Business scenarios

Business Transformation Readiness Assessment

Capability-based planning

Gap analysis

To ensure that implementation projects conform with the Target Architecture

To ensure that the enterprise’s Architecture Capability meets current requirements

To assess the performance of the architecture and make recommendations for change

To establish the value realization process

To prioritise the projects through risk validation

Baseline Architectures, and To Be Architectures

Segment Architectures, and Capability Architectures

Gap Architectures, and target Architectures

Solution Architectures, and Corporate Architectures

Transitional Architectures, and Incremental Architectures

Marginal

Residual

Low

Initial

Critical

Common Systems Solutions, Organization-Specific Solutions and Industry Solutions

Catalogs, Matrices and Diagrams

Artifacts, Best Practices and Standards

Audit Information, Process Status and Reference Data

Capability, Segment, and Transition Architectures

A high-level outline architecture

A formally reviewed, preliminary architecture

A draft, detailed architecture

A formally reviewed, detailed architecture

A preliminary outline architecture

Parameters, structures, and processes to support governance of the repository

Specifications to which architectures must conform

The organization specific architecture framework, including a method for architecture development and a metamodel for architecture content

A record of the governance activity across the enterprise

Patterns, templates, and guidelines used to create new architectures