Pass the OMG Certification OMG-OCEB2-FUND100 Questions and answers with Dumpstech

“Repeat for Each Customer” means thewhole sequenceof activities (Request → Receive → Update) must be executed once per customer. In BPMN this is modeled as amulti-instance activity/subprocess(the three vertical bars marker), which represents “for each element in a collection.” Option B shows exactly that. Option A is a simple loop, C loops each task separately, and D is just a manual cycle in the flow.

Compliance—whether for SOX, ISO, GDPR, or internal governance—requires:

Documented, repeatable processes

Properly structured internal controls

Validation mechanisms (audits, test procedures, monitoring)

This is the foundational prerequisite for compliant operations.

Hiring experts (A) may help but isnota prerequisite.

Lobbying (B) is unrelated to compliance execution.

Reducing processes (C) does not lead to compliance.

Thus the correct prerequisite isD.

Smith and Fingar describe human-system interaction components as:

Workflow(routing, sequencing of human tasks)

Automation / work allocation

Task management(task lists, inboxes, lifecycle mgmt.)

Form-based data entry(human data interaction layer)

Option D is theexact matchto the classification provided inThe Third Wave.

The other options include unrelated BPMN elements or organizational metrics not used by Smith & Fingar.

In Six Sigma and statistical process control, which are often referenced within Object Management Group (OMG) Business Process Management practices for performance measurement and process capability analysis, variation in a process is categorized into two types:

Common cause variation (natural variation)

This is the inherent, stable variation built into the process.

It reflects the normal, expected fluctuations when the process is operating in a state of statistical control.

On a control chart, data points that reflect only common cause variationremain within the control limits (UCL and LCL)and do not exhibit specific non-random patterns.

Special cause variation (assignable variation)

This arises from specific, identifiable factors not normally part of the process (e.g., equipment failure, operator error, unusual input material).

On a control chart, it is typically indicated by pointsoutside the control limitsor by defined abnormal patterns (runs, trends, cycles) even if still inside the limits.

In the diagram shown:

The horizontal center line represents theprocess average.

The upper and lower horizontal lines representUCL (Upper Control Limit)andLCL (Lower Control Limit), typically set at ±3σ from the mean.

Zones A, B, and C mark bands of 1-sigma increments from the mean but are allwithinthe control limits.

From a standard Six Sigma / SPC standpoint, and consistent with how OMG-based BPM measurement and control concepts are applied:

All data points inside the UCL and LCLare considered to be a result ofcommon cause variation, provided they do not exhibit specific rule-violating patterns.

Data points outside the UCL or LCLare not common cause; they are indications ofspecial cause variationthat must be investigated and corrected.

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.

The requirement is:“after completing task A, wait one hour before starting task B.”

In BPMN:

ACatching Intermediate Timer Eventplacedin the normal sequence flowbetween two activities means:

Activity A completes.

The token arrives at the Timer Intermediate Event.

The timer waits for its specified duration (here, one hour).

Once the timer condition is satisfied, the token proceeds to Activity B.

Option Ashows exactly this pattern:

Task A → (Intermediate Timer Event) → Task B.

Why the others are not correct:

Option Bvisually suggests the timer isbeforeA or attached differently, not clearly expressing “after A, then wait, then B.”

Option Cuses aboundary timer eventon A. A boundary timer on A represents atimeout during A’s execution(e.g., if A takes longer than one hour, do something), not a guaranteed wait period after A finishes.

Option Dintroduces a gateway and an end event, implying alternate paths rather than a simple fixed delay between A and B.

Thus, the diagram that correctly models “after completing A, wait one hour, then start B” isOption A.

In Quality Management (TQM, Six Sigma, ISO 9001),commonly used quality toolsinclude:

Run chart

Control chart

Pareto chart

Fishbone diagram

Histogram

Scatter diagram

Check sheet

Among the options:

Run chart→ Correct, a standard quality analysis tool

Gantt chart → Project scheduling tool, not quality-specific

Quality cost baseline → A document, not a tool

Work Breakdown Structure (WBS) → Project decomposition tool, not used in quality analysis

Therefore, the correct answer isA.

In theObject Management Group (OMG) Business Process Maturity Model (BPMM), each maturity level is characterized by a specific scope of focus and a defined set of process areas.

ForMaturity Level 2 – Managed, BPMM clearly states that the emphasis is on bringing basic management discipline toindividual organizational units where work is performed, typically calledwork units(e.g., departments, teams, projects, operational units).

At this level:

Processes areplanned, performed, monitored, and controlledat thework unit level.

The goal is to ensure that commitments are met, performance is tracked, and issues are managed within these units.

Process areas at Level 2 (such as those concerned with work unit management, performance, and corrective action) explicitly assume that theprimary organizational entity of concern is the work unit, not yet the end-to-end, cross-functional business process.

This is a key distinction in BPMM:

Level 1 (Initial):Work is performed, but processes are ad hoc and largely unmanaged.

Level 2 (Managed):Processes are managedwithin work units. The discipline of basic planning, monitoring, and control is introduced at this local level.

Level 3 (Standardized):Processes becomestandardized and harmonized across the organization, and attention shifts toend-to-end processesthat cut across functional and organizational boundaries.

Higher levels (4 and 5) further institutionalize measurement, predictability, and continuous optimization across these standardized processes.

Given this structure:

Option A – work units

Correct. This is exactly the organizational focus of Level 2 process areas in BPMM.

Option B – business area managers

While business area managers may be involved, BPMM does not define maturity level 2 as focusing on managers as entities; it focuses onwork units as the organizational locusof process management.

Option C – information technology operations

IT operations may constitute a particular type of work unit, but BPMM Level 2 isnot limitedto IT; it is generic to all work units across the enterprise. Therefore, this is too narrow and not aligned with the model’s definition.

Option D – end-to-end product and service offerings

This reflects a Level 3 and above concern, wherecross-functional, end-to-end processesare standardized and managed as a whole. It isnotthe focus of maturity level 2, which is still concentrated on thelocal, work-unitperspective.

Accordingly, based on the OMGBusiness Process Maturity Modelspecification, the process areas atmaturity level 2focus onwork unitsas the primary organizational entities.

In BPMN, aText Annotationis anartifactused purely to add explanatory comments to elements in a diagram. Itnever affects the process flow or execution semantics. OMG specifies that artifacts, including Text Annotations, are connected to flow objects (activities, events, gateways, sequence flows, etc.) usingAssociations, which are dotted (or dashed) lines. The association may be directional or non-directional, but it is still anAssociation, not a Sequence Flow or Message Flow.

Therefore:

Option A is false because Text Annotations donotaffect process flow.

Option B is false because a Text Annotation may be connected toanyflow object (and even to flows), not only to pools, lanes, or groups.

Option C correctly states that a Text Annotation is connected by anAssociation.

Option D is about its graphic shape, but the question asks for adescriptionthat is true in general, which is precisely captured by Option C.

So,Cis the correct answer in accordance with the OMG BPMN 2.0.2 specification.