OGA-032 Sample Questions & Answers

The Realization relationship is used to indicate that a more abstract element is made concrete by a more tangible element. In the Technology Layer, a Node (a physical or virtual computational resource) realizes System Software, meaning it provides the execution environment for that software. Assignment is used for deploying artifacts to nodes, not for the execution environment itself. Composition is structurally incorrect.

A 'Gap' is the specific ArchiMate element used to represent a statement of difference between two Plateaus (e.g., baseline and target). In this case, the missing 'Customer 360 View' capability is the gap that needs to be addressed by the migration plan. A Work Package is what will be done to close the gap, and a Plateau is a state of the architecture, not the difference itself.

The Infrastructure Viewpoint is specifically designed to show the software and hardware infrastructure elements that support the Application Layer. Its typical elements include Node, Device, System Software, and Path, which directly correspond to the stakeholder's concerns about physical hardware, system software, and network connections. The other viewpoints focus on different layers or different aspects of the technology layer.

Composition is the correct relationship. It represents that an element consists of one or more other elements. This implies a whole/part relationship where the parts are essential to the whole and typically cease to exist if the whole is destroyed. Aggregation is a weaker form of whole/part relationship where the parts can exist independently. Given that 'Payment Gateway' and 'Inventory Check' are integral parts of 'Order Processing', Composition is the stronger, more accurate choice.

The correct model is that the Work Package realizes the Deliverable. A Work Package represents a set of actions to be performed, while a Deliverable represents a precise outcome of that work. The Realization relationship indicates that the Work Package produces or creates the Deliverable. The other options represent incorrect semantics for this context.

A Value Stream is the correct element. It is defined as a sequence of activities that create an overall result for a customer, stakeholder, or end user. It provides a high-level, strategic view of how value is created, which is exactly what the architect needs. A Business Process is more operational and detailed, while a Capability represents an ability, not the flow of value-creating activities.

A Business Interaction is the correct element to model a unit of collective behavior performed by two or more business actors, roles, or collaborations. While a Business Collaboration would represent the aggregate of the two roles working together, the specific unit of behavior (the conversation to resolve the issue) is the Business Interaction. The Business Interaction is then assigned to the Business Collaboration.

This is the correct modeling approach. A Principle is a statement of intent that guides decisions. It doesn't directly create a requirement, but it strongly 'influences' it. Therefore, the Principle influences a more concrete Requirement (e.g., 'The customer database must support AES-256 encryption'). This Requirement is then 'realized' by the Application Component, meaning the component is designed and built to meet that requirement. This chain correctly shows the traceability from high-level guidance to concrete implementation.

This is the core distinction. A Node is a computational resource (physical or virtual) upon which artifacts can be deployed for execution (e.g., a server, a virtual machine). A Device is a physical IT resource that is NOT a computational platform, such as a sensor, or a physical resource from the real world that processes materials or information (e.g., a network router, a CNC machine, a printer). A server is a Node; a network switch is a Device.

The correct element is 'Application Interaction'. An Application Interaction models a unit of collective behavior performed by a collaboration of application components. In this case, 'Catalog Synchronization' is the interaction. This Application Interaction is then 'assigned' to the 'Global SCM Collaboration', indicating that the components within that collaboration are the ones that perform this collective behavior.