OGA-031 ArchiMate 3 Part 1 Examination Questions and Answers

According to the standard notation conventions, a structure element is denoted by a rectangle with rounded corners. A structure element represents an entity that has a state and exhibits some behavior. Examples of structure elements are actors, roles, components, nodes, and objects.

According to the ArchiMate® 3.2 Specification 1 , a principle defines a general property that applies to any system in a certain context.  A principle is a normative property of all systems in a given context that expresses a fundamental value or property 1 . Therefore, the correct answer is A. A principle.

Comprehensive and Detailed in Depth Explanation: An Interface in ArchiMate represents an access point through which elements interact with services . It can be a Business Interface, Application Interface, or Technology Interface .

Interfaces serve as a boundary between internal and external systems, allowing controlled interactions. The ArchiMate 3.2 Specification explicitly states that interfaces expose services to the environment .

References:

Archi User Guide ​

ArchiMate 3.2 Specification

According to the Technology Layer metamodel, a communication network is a physical communication medium between two or more devices or other networks. A communication network realizes a path, which is a relation between two or more nodes through which they can exchange information.

References: Technology Layer in ArchiMate Part 1 - Metamodel 1 ; ArchiMate® 3.2 Specification, Chapter 10: Technology Layer 2 .

Comprehensive and Detailed In-Depth Explanation:

This ArchiMate Physical Layer diagram represents logistics and supply chain operations . The elements in the diagram align with physical infrastructure concepts used in ArchiMate 3.2 .

Understanding the Diagram Elements:

V (Factory symbol) → Represents a Factory or Production Facility , where goods are manufactured.

W (Gear symbol) → Represents Raw Material or Equipment that is used in production .

X (Network or Transportation symbol) → Represents Transportation or a Distribution network for moving goods.

Y (End-point receiving goods) → Represents a logistics center, warehouse, or transportation endpoint .

This matches option D , where:

V = Factory → The starting point of manufacturing.

W = Raw material → Essential input for production.

X = Transportation → Moving products to distribution centers.

Analysis of Answer Choices:

✅ A. V = Production process, W = Finished Material, X = Transport network → ❌ Incorrect

V is not a process ; it is a physical location (Factory) .

W represents raw material, not finished material .

X represents transportation, but V is wrongly classified as a process.

✅ B. V = Equipment, W = Facility, X = Distribution channel → ❌ Incorrect

V represents a Facility (Factory), not just Equipment .

W represents raw material, not a Facility .

X is more of a transportation network rather than a distribution channel.

✅ C. V = Facility, W = Equipment, X = Distribution network → ❌ Incorrect

W represents raw material, not just Equipment .

X represents Transportation, not strictly a distribution network.

✅ D. V = Factory, W = Raw material, X = Transportation → ✅ Correct Answer

This is the best match with the diagram’s physical elements .

V (Factory) is the production source .

W (Raw material) is used in production .

X (Transportation) is the means of moving goods.

ArchiMate 3.2 Specification, Section 7.7 , defines Facilities, Materials, and Transportation as part of the Physical Layer modeling concepts.

Final Answer: ✅ D. V = Factory, W = Raw material, X = Transportation.

References:

ArchiMate 3.2 Specification: Sections 7.7 (Facilities & Physical Elements), 7.8 (Material Flow), and 7.9 (Distribution & Logistics).

Archi User Guide: Modeling physical infrastructure in enterprise architecture.

According to the ArchiMate 3.2 Specification 1 , a business event is a behavior element that denotes an organizational state change. It may originate from and be resolved inside or outside the organization. A business event accesses a passive structure element that represents an entity relevant from a business perspective, such as a business object, a contract, or a product. A business passive structure element is denoted by a rectangular shape with square corners. The access relationship is denoted by a line with an open arrowhead.

The diagram below shows a business event named Order Received that accesses a business passive structure element named Order. The access relationship indicates that the event reads or writes the order.

 This is because the diagram shows the three main categories of relationships in ArchiMate: structural relationships, which model the static construction or composition of concepts; dependency relationships, which model how elements depend on or use other elements; and dynamic relationships, which model the temporal or causal connections between elements.

Based on the ArchiMate 3 documents or objectives, a communication network represents a set of structures that connects devices or system software for transmission, routing, and reception of data. A path models the relation between two or more technology internal active structure elements, through which these can exchange information. The diagram uses a flow relationship to indicate that data flows from server B to communication network E, then through path F to communication network I. The notation for a flow relationship is a dashed line with an open arrowhead at the end that points to the direction of the flow.

References: ArchiMate® 3.2 Specification, Chapter 11 Technology Layer, Section 11.2 Active Structure Elements  1 ; ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.4 Dynamic Relationships  1 ; ArchiMate communication network  2 .

Based on the ArchiMate 3 documents or objectives, a realization relationship indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity. A serving relationship models that an element provides its functionality to another element. The diagram should use a realization relationship from the Risk Assessment service to the Enterprise Risk Management process to indicate that the service realizes the process. The diagram should also use a serving relationship from the Risk Measurement application to the Risk Assessment service to indicate that the application serves the service.

References: ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.1 Structural Relationships  1 ; ArchiMate® 3.2 Specification, Chapter 5 Relationships, Section 5.2 Dependency Relationships  1 ; ArchiMate Notation: Part 8 – Relationships - ArchiMate Resources for FREE  2 .

According to the ArchiMate 3.2 Specification 1 , a capability is an ability that an active structure element, such as an organization, person, or system, possesses. A requirement is a statement of need that must be realized by a system. Capabilities and requirements are both motivation elements that represent the reasons for designing and implementing an architecture.

The ArchiMate language defines two relationships that are permitted between capabilities and requirements:

Assigned to: This relationship links a requirement to a core element (such as a business actor, a business service, a business process, an application service, an application component, etc.) that is responsible for realizing it. The core element may be assigned to a capability that enables it to realize the requirement.

Realizes: This relationship links a capability to a requirement that is fully or partially realized by that capability.

Comprehensive and Detailed In-Depth Explanation:

This ArchiMate Technology Layer diagram represents a software application architecture where different application components interact with data objects.

"Online Claims" is an application component that interacts with "Loss Claim" .

"Loss Claim" is another application component, likely acting as a back-end system that processes claims.

"Customer Record" is a data object that "Loss Claim" accesses to retrieve or store customer-related information.

The Online Claims system does not directly access the Customer Record , but instead relies on the Loss Claim system to fetch the required data .

Analysis of Answer Choices:

✅ A. The Loss Claim application serves the Online Claims department and accesses a data object called Customer Record. → ❌ Incorrect

There is no indication that "Online Claims" represents a department; it is an application component.

The diagram focuses on software components, not organizational units .

✅ B. The Online Claims application uses a back-end module called Loss Claim to access a data object called Customer Record. → ✅ Correct Answer

The Online Claims system depends on the Loss Claim system, which in turn accesses the Customer Record .

This matches the typical structure of a front-end application relying on a back-end module .

ArchiMate 3.2 Specification, Section 7.3 , states that application components can interact hierarchically, where a front-end application calls a back-end service to process data.

✅ C. The Loss Claim application realizes the Online Claims service and accesses a Customer Record data object. → ❌ Incorrect

"Realization" means the Loss Claim application would be implementing a service provided by Online Claims.

In the diagram, Online Claims and Loss Claim are separate application components , and Loss Claim is not a realization of an Online Claims service .

✅ D. The Customer Record application uses Loss Claim middleware to present the Online Claims user interface. → ❌ Incorrect

The Customer Record is a data object, not an application.

Loss Claim is not middleware; it is a back-end application component.

The diagram does not indicate that Loss Claim is responsible for presenting a user interface.

Final Answer: ✅ B. The Online Claims application uses a back-end module called Loss Claim to access a data object called Customer Record.

References:

ArchiMate 3.2 Specification: Sections 7.3 (Application Components), 7.5 (Data Objects), and 7.6 (Application Services).

Archi User Guide: Modeling front-end and back-end application interactions.

Comprehensive and Detailed in Depth Explanation: The ArchiMate framework consists of three core layers :

Business Layer : Represents business processes, services, roles, and actors.

Application Layer : Describes software applications and their interactions.

Technology Layer : Represents infrastructure elements like servers, networks, and storage.

The ArchiMate 3.2 Specification defines these three core layers as the primary structure of Enterprise Architecture modeling .

References:

Archi User Guide ​

ArchiMate 3.2 Specification

Comprehensive and Detailed In-Depth Explanation:

This diagram represents a goal-driven model where the bottom element (Let customers choose how they interact with ArchiSurance) describes a high-level objective or outcome , while the top elements represent specific implementations that fulfill this objective .

In ArchiMate 3.2 , the Realization relationship is used when:

A higher-level concept (e.g., a goal or requirement) is realized by more specific lower-level elements.

Concrete solutions (e.g., features or processes) implement or fulfill an abstract goal.

Understanding the Diagram:

The goal is to let customers choose how they interact with ArchiSurance .

The two elements at the top ("Add secure email message submission" and "Add click-to-chat feature") are specific solutions that make this goal achievable .

This fits exactly with the Realization relationship , where a goal or requirement is realized by specific actions .

Analysis of Answer Choices:

✅ A. Aggregation → ❌ Incorrect

Aggregation represents a "whole-part" relationship , where elements can exist independently of the whole.

The top elements are not separate, independent components but rather implementations of the bottom element.

✅ B. Access → ❌ Incorrect

Access relationships are used for information flow , such as reading, writing, or modifying data.

This model is about realizing a business objective, not accessing data.

✅ C. Realization → ✅ Correct Answer

The bottom element is a higher-level goal , and the top elements implement or realize it.

ArchiMate 3.2 Specification, Section 6.4.9 , states that Realization relationships link abstract concepts (like goals) to concrete implementations (like processes, services, or functions).

✅ D. Specialization → ❌ Incorrect

Specialization relationships are used when one concept is a subtype of another.

The top elements are not specialized versions of the bottom element ; rather, they implement it.

Final Answer: ✅ C. Realization

References:

ArchiMate 3.2 Specification: Section 6.4.9 (Realization Relationship).

Archi User Guide: Understanding goal realization and requirement fulfillment.

Based on the ArchiMate 3 documents or objectives, a business actor represents a business entity that is capable of performing behavior. A business actor is a business entity as opposed to a technical entity; i.e., it belongs to the Business Layer. The notation for a business actor is a circle with a stick figure inside it. The Chief Marketing Officer in this diagram is a business actor that performs the behavior assigned to the Marketing Manager role.

References: ArchiMate® 3.2 Specification, Chapter 8 Business Layer, Section 8.2 Active Structure Elements  1 ; ArchiMate Example: Business Actor - Visual Paradigm Community Circle  2 .

Based on the ArchiMate 3 documents or objectives, the generic metamodel defines two main types of elements: structure and behavior. Structure elements represent the structural concepts that model the static construction or composition of concepts of the same or different types. Behavior elements represent units of activity performed by one or more active structure elements.

References: ArchiMate® 3.2 Specification, Chapter 4 Generic Metamodel, Section 4.1 Behavior and Structure Elements  1 ; ArchiMate® 3.0.1 Specification - The Open Group  2 .

Comprehensive and Detailed in Depth Explanation: Architecture Viewpoints are predefined perspectives or templates that define how specific stakeholders view an architecture . They provide guidelines for structuring models to communicate effectively with different stakeholders .

The ArchiMate 3.2 Specification describes Architecture Viewpoints as tools for filtering and structuring architectural representations to address stakeholder concerns .

References:

Archi User Guide ​

ArchiMate 3.2 Specification

Comprehensive and Detailed In-Depth Explanation:

This diagram represents a Technology Layer model in ArchiMate, where X and Z are servers , and E is a shared technology component .

X and Z are likely hardware devices (Servers), which are typically represented as Technology Nodes or Devices in ArchiMate.

E is a shared resource that both servers connect to, implying a common storage or network area storage device.

According to ArchiMate 3.2 , Technology Objects like Storage Devices or Infrastructure Services can be shared across multiple devices.

Analysis of Answer Choices:

✅ A. The servers, represented by devices, are connected by a communication network. → ❌ Incorrect

There is no explicit network symbol (e.g., a communication path or a network node).

The relationship between X, Z, and E indicates a shared resource rather than a network connection .

ArchiMate 3.2 Specification, Section 6.6.4 , defines Communication Networks separately, and none are present here.

✅ B. The servers are shown in the technology interaction E, where they collectively process data. → ❌ Incorrect

Technology Interaction represents behavior in ArchiMate, meaning two or more active elements are collaborating on a process .

E is a shared object, not an interaction process.

✅ C. The servers share a common network area storage device E. → ✅ Correct Answer

E is a shared resource , meaning it is likely a storage device used by both servers .

ArchiMate 3.2 Specification, Section 6.6.2 , states that Technology Objects can represent storage elements used by multiple devices.

This matches the pattern of a shared Network Attached Storage (NAS) or Storage Area Network (SAN).

✅ D. Technology collaboration E represents a point of access for services offered by the servers. → ❌ Incorrect

Technology Collaboration elements represent active behavior , not a static resource like a shared storage system.

E does not behave as a collaboration element but as a shared infrastructure object.

Final Answer: ✅ C. The servers share a common network area storage device E.

References:

ArchiMate 3.2 Specification: Sections 6.6.2 (Technology Object), 6.6.4 (Communication Network), and 6.6.7 (Technology Collaboration).

Archi User Guide: Understanding shared technology infrastructure and storage modeling.

Comprehensive and Detailed In-Depth Explanation:

This diagram represents a value stream , which is a key concept in ArchiMate 3.2 . A value stream describes how value is created and delivered across a sequence of activities. It is used to represent high-level business activities that contribute to the value creation for a stakeholder or customer.

The Acquire Insurance Product at the top level represents an end-to-end flow.

The sub-elements ( Develop Products, Market and Sell Products, Manage Policies and Claims, and Serve Customers ) depict how value is progressively built through different stages.

The dashed arrows indicate a flow of value from one stage to the next, typical in value streams.

Analysis of Answer Choices:

✅ A. A set of processes for acquiring insurance products → ❌ Incorrect.

Processes are typically lower-level activities depicted using process modeling , such as BPMN or a process flow diagram.

ArchiMate 3.2 Specification, Section 6.3.2 , differentiates business processes from value streams .

✅ B. A sequence of capabilities for acquiring insurance products → ❌ Incorrect.

Capabilities represent the organization’s abilities rather than sequential activities.

In ArchiMate , capabilities are more static, focusing on what the organization can do , rather than how value is delivered over time .

ArchiMate 3.2 Specification, Section 7.3 , explains the distinction between capabilities and value streams .

✅ C. A value stream for acquiring insurance products → ✅ Correct Answer

A value stream represents a series of high-level activities that create value for a customer or stakeholder.

ArchiMate 3.2 Specification, Section 8.2.4 , defines value streams as sequences that deliver value incrementally .

This exact pattern (top-level action decomposed into a structured sequence of stages ) is a value stream .

✅ D. A decomposition of the course of action for acquiring insurance products → ❌ Incorrect.

Course of action is a concept in Strategy Layer of ArchiMate, referring to guidelines, policies, or directions rather than a flow of activities .

This is not a strategic breakdown , but rather a flow of value creation .

ArchiMate 3.2 Specification, Section 7.5 , states that course of action is different from a structured value creation sequence .

Final Answer: ✅ C. A value stream for acquiring insurance products.

References:

ArchiMate 3.2 Specification: Sections 6.3.2 (Business Process), 7.3 (Capabilities), 8.2.4 (Value Streams), and 7.5 (Course of Action) .

Archi User Guide: Value Stream modeling and decomposition principles .

Comprehensive and Detailed in Depth Explanation: The Assignment relationship is used to link elements that perform or fulfill a function . A Technology Function represents a logical grouping of technology behavior (e.g., storage, networking), while an Application Function represents software behavior (e.g., processing business transactions).

Since technology functions enable applications to operate, the Assignment relationship correctly models this dependency. The ArchiMate 3.2 Specification explicitly states that Technology Functions can be assigned to Application Functions .

References:

Archi User Guide ​

ArchiMate 3.2 Specification

Based on the ArchiMate 3 documents or objectives, an application interface represents a point of access where an application service is made available to a user, another application component, or a node. An application interface specifies how the functionality of a component can be accessed by other elements. The notation for an application interface is a square with a small circle attached to it.

References: ArchiMate® 3.2 Specification, Chapter 10 Application Layer, Section 10.1 Active Structure Elements  1 ; Application Layer in ArchiMate Part 2 – Notation and Concepts - ArchiMate Resources for FREE  2 .