OG0-091 Sample Questions Answers

To catch errors in a project architecture early

To guide decision making throughout the enterprise

To help identify and understand business requirements

To highlight shortfalls between the baseline and target architectures

To mitigate risk when implementing an architecture project

Application

Capability

Segment

Transition

Vision

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

Finalize the Implementation and Migration Plan

Establish the recourses for architecture governance

Ensure conformance for the target architecture

Operate the governance framework

Develop the Target Technology Architecture

Allocating resources for architecture projects

Creating the Statement of Architecture Work

Enforcement of architecture compliance

Determining the scope of an architecture compliance review

Conducting assessments of the maturity level of architecture discipline within the organization

Phase C: Data Architecture

Preliminary Phase

Phase A: Architecture Vision

Phase F: Migration Planning

Phase B: Business Architecture

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

An architecture of a commercial organization

An architecture that consists of more than one subsidiary company

An architecture that crosses multiple systems, and multiple functional groups within the enterprise

The highest level of architecture that can be achieved in a given organization

To coordinate with the other management frameworks in use

To describe how an architecture addresses stakeholder concerns

To identify and understand business requirements

To provide a system for continuous monitoring

To structure re-usable architecture and solution assets

The categorization after implementation of mitigating actions

The categorization after initial risk assessment

The categorization after mitigation and residual risk assessment

The categorization before determining and implementing mitigating actions

The categorization before risk identification

To aid communication and understanding between architects

To coordinate with the other management frameworks in use

To describe how an architecture addresses stakeholder concerns

To evaluate how best to develop and implement an architecture

To help identify and understand business requirements

To create an implementation and migration strategy

To establish an architecture change management process

To priorities work packages and projects

To validate the business principles, goals, drivers and key performance indicators

Develop an Architecture Roadmap

Populate the Architecture Repository

Populate the Enterprise Continuum

Use the Architecture Development Method

Use the Implementation Governance Phase

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

Name

Statement of Principle

Rationale

Enforcement Policy

Implications

It is used to coordinate with the other management frameworks in use

It is used to describe how an architecture addresses stakeholder concerns

It is used to identify and understand business requirements

It is used to provide a system for continuous monitoring

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

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

Business requirements

Cultural aspirations

Forecast financial requirements

Strategic Intent

Technical elegance

Architecture governance

Corporate governance

IT governance

Technology governance

The program management office

Architecture Capability

Architecture Landscape

Architecture Metamodel

Governance Log

Reference Library

Architecture governance

Business imperatives

Solution architecture

Service level agreements

Time horizon

Requirements Management

Phase D

Phase F

Phase G

Phase H

To define the Baseline Architecture for this cycle of the ADM

To define the application systems for the Target Architecture

To define the framework and methodologies to be used

To define the relevant stakeholders and their concerns

To define and prioritise work packages

Common Systems Architecture

Foundation Architecture

Industry Architecture

Organization Specific Architecture

Product Line Architecture

Enterprise Architecture Capability

IT Governing Board

Program Management Office

Quality Assurance department

Service Management department

Business scenario

Impact analysis

Mission statement

Requirements analysis

Solution architecture

are assembled; are single function components

are single function components; are groups of architecture building blocks

are reusable; are not reusable

define the architecture; provide the existing legacy system

define functionality; define the implementation of functionality

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

Requirements Management

Phase E

Phase F

Phase G

Phase H

a complete ADM cycle

a complete re-architecting change

a full revision of the enterprise architecture

an incremental change

a simplification change

A repository area that lists the set of specifications to which architectures must conform

A repository area that describes the organization specific architecture framework and method.

A repository area that defines the parameters, structures, and processes to support governance

A repository area that provides guidelines, templates, and patterns used to create new architectures

A repository area that provides a record of the governance activity across the enterprise

Concerns

Principles

Requirements

Views

Viewpoints

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

Preliminary Phase

Phase A

Phase E

Phase G

Phase H

To build a top-down, all inclusive architecture description

To enable development of reference architectures

To enable the architecture domains to be integrated

To ensure that the method is being applied correctly

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

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

To govern the architecture throughout its implementation process

To act as a deliverable container for artifacts created during a project

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

Creating the Architecture Vision deliverable

Defining a set of Architecture Principles

Developing an Architecture Contract

Extending the business scenario with business modeling

Preparing a consolidated Gap Analysis

Phase A

Phase E

Phase F

Phase G

Phase H

TOGAF Reference Models

Architecture Content Framework

Architecture Capability Framework

Enterprise Continuum & Tools

Architecture Development Method