OMG OMG-Certified Expert in BPM 2 - Fundamental OMG-OCEB2-FUND100 Exam Dumps: Updated Questions & Answers (January 2026)

Within the OMG BPMN framework,Level 3 – Executable modelingrepresents a process definition that is detailed enough to bedirectly executed by a BPM engine. This level includes:

Implementation-specific details (data mappings, transaction boundaries, technical error handling)

Engine- or vendor-specific extensions and attributes

Bindings to services, message formats, and integration mechanisms

Because these details depend on how a specificvendor toolorexecution platforminterprets BPMN,executable models are somewhat vendor-tool dependent. Different engines support different subsets of BPMN and add their own extensions, making the executable level less portable than descriptive or analytical models.

The other options do not represent OMG’s three levels of BPMN:

Pattern modelingandsource-code modelingare not standard BPMN levels.

Descriptive modelingis tool-independent and used for communication, not execution.

Thus,executable modelingis the level that is somewhat vendor-tool dependent.

The BMM aligns directly with theZachman Framework.

Specifically:

TheOwner’s perspectivecorresponds to thebusiness view(row 2).

TheWhy columnof Zachman represents motivation:EndsandMeans.

The BMM’s purpose is to document:

Ends(Goals, Objectives)

Means(Strategies, Tactics)

The influence of external/internal factors

This exactly corresponds to theOwner’s view of the “Why” column.

Thus,Option B is correct.

AnExpanded Sub-Process without Sequence Flows between its Tasksis interpreted as anAd-Hoc Sub-Process, provided it is marked as such (with the ad-hoc tilde marker). In BPMN / OMG terms, an ad-hoc sub-process:

Hasno predefined execution orderbetween its contained activities.

Allows activities to be performedin any order, possibly

multiple times,

not at all,

or in parallel.

Continues until somecompletion conditionis satisfied or the process decides to end that sub-process.

This is exactly what optionCdescribes.

OptionAandDimpose ordering or “exactly-once” semantics that BPMN doesnotdefine for an ad-hoc sub-process.

OptionBis incorrect because BPMN explicitly allows ad-hoc subprocesses where tasks are not connected by sequence flows.

Therefore,Cis the correct interpretation.

In BPMN,Data Objectsare artifacts that show what data isusedorproducedby activities. They are connected usingData Associations, which are drawn asdashed/dotted lines with arrowheads:

Arrowfrom Data Object to Activity= the data is aninputto that activity.

Arrowfrom Activity to Data Object= the data is anoutputproduced by that activity.

Looking at the options:

Option AshowsTask Awith:

A dashed association arrow fromData Object 1 to Task A(Data Object 1 is input).

A dashed association arrow fromTask A to Data Object 2(Data Object 2 is output).This matches BPMN rules exactly and is a canonical textbook example of input and output data objects for a task.

Option Bshows both data objects associated as outputs only (arrows from Task A to both), which would not reflect the typical input–output pattern and is generally not the intended “correct” example for demonstrating BPMN data object usage.

Options C and Dinvolve attaching a data object to a sequence flow. While BPMN allows associating a data object to a sequence flow as shorthand, the official specification states that when associating an artifact with asequence or message flow, the association is normallynon-directional(no arrowheads), because the flow itself already shows direction. One of these options uses directional arrows incorrectly, and thus these are not preferred as the “correct” representation in a strict exam context.

Given the OMG specification and common BPMN teaching examples,Option Ais the clearly correct and standards-compliant diagram for data objects and data associations.

According to BPMN:

Aprivate (internal) Business Processmodels theinternal workflow of a single organization or participant. Its Activities are tasks, subprocesses, etc., performedinsidethat participant. Messages to other parties are shown only as message flows on the boundary, not as separate activities.

AChoreographydiagram, in contrast, models theinteractions between independent participants.

EachChoreography Activityrepresents aset of message exchangesbetween two or more participants (e.g., “Place Order,” “Send Invoice”), not the internal steps inside any one organization.

Thus the essential difference is exactly what optionDstates:

Private process activities = internal work;

Choreography activities = inter-participant message interactions.

Options A, B, and C misrepresent the relationship; a Choreography is not a special private process, nor is it just “the set of messages” of one process. It is a separate diagram type with its own semantics in BPMN.

Inmanagement by process, work is organized aroundend-to-end value-creating processesrather than around traditional functional departments. This is strongly reflected in OMG’s BPM thinking, where process models (e.g., BPMN) cut horizontally across functions to deliver value to customers.

A coreweaknessof process-centric structures is thatspecialized expertise may be distributed and duplicatedin multiple process teams (for example, having separate finance, HR, or IT expertise embedded within each major process area).

This can reduce economies of scale and create redundancy in roles and skills, compared with a centralized functional department model.

Why the other options arenotweaknesses of management by process:

A. Functional silo effect– This is a weakness offunctional management, not process management. Management by process aims specifically toeliminatesilo effects.

B. Lack of end-to-end focus– Process management’s defining strength isend-to-end focus, so this is the opposite of reality.

C. Poor handover between functions– Process management explicitly designscross-functional flows and handovers, reducing the risk of poor handover seen in traditional functional models.

Thus, aknown weakness of management by processisduplication of functional expertise, makingDcorrect.

COBIT (Control Objectives for Information and related Technology) is widely recognized as aframework of best practicesfor governing and managing enterprise IT. It provides a structured set of processes, control objectives, practices, and metrics that organizations can adopt to ensure that IT supports business goals, manages risks appropriately, and complies with relevant regulations.

From the perspective of Object Management Group (OMG) Business Process Management and enterprise architecture:

COBIT is used as agovernance and control frameworkthat sits above or alongside operational business processes modeled with BPMN.

It provideswhat must be controlled and measuredin IT-related processes, while BPM and OMG standards describehow those processes are modeled, executed, and improved.

COBIT defines domains and processes (e.g., plan and organize, acquire and implement, deliver and support, monitor and evaluate) which organizations can map to their BPMN-modeled IT and support processes, thereby aligning IT operations with business objectives.

Why the other options are incorrect:

Option A – “a set of rules that providers of IT solutions must comply with”: COBIT is not a mandatory rule set imposed on solution providers; it is avoluntary, best-practice frameworkadopted by organizations to improve IT governance.

Option B – “a set of regulations”: COBIT itself is not a law or regulation. Rather, it helps enterprises design controls and processes that support compliance with multiple regulations.

Option C – “a set of industry standards that promote the use of IT technologies”: COBIT is not a technical standard promoting specific technologies; it is amanagement and control frameworkdescribing what good IT governance looks like.

In theOMG Business Motivation Model (BMM), aBusiness Ruleis explicitly defined as atype of Directive.

Within BMM:

Directiveis a concept underMeansand represents guidance or constraints on how the business operates.

Directives are divided into two main types:

Business Policy

Business Rule

So, aBusiness Rule is not a Tactic, Strength, or Guideline, but aspecialization of the concept “Directive”. It is the most formal, detailed, and directly actionable form of guidance in the BMM structure, derived from Business Policies and used to govern operational behavior and processes.

Therefore, in BMM,Business Rule is a component of the concept “Directive.”

In BPMN, apublic (abstract) processshows only theexternal, message-based interactionsbetween a private (internal) business process and another participant. It hides the internal detailed flow and exposes just the communication behavior. That is exactly what optionBdescribes.

In the given diagram:

After activityA, there is anexclusive gateway(with conditionscond1andcond2), soeither B or Cis chosen—never both.

AfterBandC, their flows go into a gateway with aplus sign, which is aParallel Gateway (AND-join)in BPMN.

AParallel Joinwaits fora token fromeveryincoming branchbefore it can release a token onward toD. But due to the earlier exclusive split,only oneof the two branches (B or C) ever receives a token. The other branch never activates, so the parallel join never gets all required tokens.

Consequences:

The join gateway willnever be satisfied,

Therefore, the flownever proceeds to activity D.

So the defect is exactly what optionBsays:

The activity D can never be reached.

That is the correct answer.