OG0-021 ArchiMate 2 Part 1 Examination Questions and Answers

There are three purpose dimensions and three abstraction levels

There are two purpose dimensions and three abstraction layers

There are four purpose dimensions and two abstraction levels

There are three purpose dimensions and four abstraction layers

The Claims Adjudication Process realizes the Claim File

Claims are filed after the Claims Adjudication process is complete

The Claims Adjudication team relies on the Claim File to get its work done

The Claims Adjudication process accesses the Claim File

The Underwriting Application groups together a number of modules that are either free-standing or part of other applications

The Underwriting Application is composed of three application components

The Underwriting Application invokes three other modules

The Underwriting Application performs three functions

Relationship 1

Relationship 2

Relationship 3

Relationship 4

It represents a relatively stable intermediate state during the migration from the Baseline to the Target Architectures

It represents a project that progresses the architecture from Baseline to Target

It represents the deliverables necessary to transform the architecture from Baseline to Target

It represents a conceptual point of transition between the two architectures, but one that is unlikely to exist in reality for more than an instant

Access

Assignment

Association

Flow

Transition

Gap

Work Package

Deliverable

It is the only way to model enterprise architecures that are useable and easy to communicate to the stakeholders

It is needed to represent the same concept on different viewpoints

It provides extra flexibility, enabling users to customize the language to their own preferences and needs, while maintaining the underlying precise definition of the concepts

It is allowed because without this mechanism it would be impossible to add attributes to ArchiMate concepts and relations

Application component

Application function r

Data object

Business object

Work Package, Artifact, Plateau, Driver

Work Package, Deliverable, Plateau, Gap

Project, Work Package, Deliverable, Plateau

Project, Resource, Deliverable, Gap

It connects structural relationships of different types

It connects dynamic relationships of the same type

It connects dynamic relationships of different types

It connects structural relationships of the same type

Triggering

Access

Flow

Assignment

A point of access where an application service is made available to the business layer

A point of access where a business service is made available to the environment

An aggregate of two or more business roles that work together to perform collective behavior

A formal or informal agreement that specifies the rights and obligations associated with a business service

RepairMaster is a business product that includes three services and is used by three different roles

RepairMaster is a business service that includes three products and is used by three different business actors

RepairMaster is a business object that holds information about three different services, and is accessed by three different roles

RepairMaster is a business product that delivers three different kinds of value to the three different roles that use it

Product architecture

Business process architecture

Application landscape

Internal software structure

A device with two system software environments. Two artifacts are deployed in one system software environment, and one artifact is deployed in the other environment

A node with two devices. Two artifacts are deployed in one device, and one artifact is deployed in the other device

A node with two system software environments. Two artifacts are deployed in one system software environment, and one artifact is deployed in the other environment

A node with two application components. Two artifacts are deployed in one application component, and one artifact is deployed in the other components

1,2,3,4

1,2,4,3

4,2,1,3

4,1,2,3

A work package that realizes a deliverable

A business process that realizes a representation

A work package that realizes a gap

A plateau that realizes a gap

Added value of business processes, consistency and completeness, responsibilities

Identification of competencies, authority and responsibilities

Application dependencies, performance, scalability

Structures and dependencies of the used data and information

Preliminary Phase

Phase B: Business Architecture

Phase C: Information Systems Architectures

Phase D: Technology Architecture

Resourcing of projects

The main differences between the baseline and the target architecture

The motivation for projects

The results produced by different projects