OMG-OCEB2-FUND100 Exam Dumps : OMG-Certified Expert in BPM 2 - Fundamental

InBPMN, a rounded rectangle with adashed borderaround activities is aGroupartifact.

Key BPMN semantics for aGroup:

It ispurely documentary: used to visually group related activities (for example, labeling them “Process Payment” or “Deliver Product”).

Itdoes not affect execution semantics—sequence flow, data flow, and transaction behavior areexactly the same as if the group were not drawn.

Looking at the diagram:

The sequence is:Verify Credit → Process Payment → Deliver Product → Notify Customer, each connected by normal sequence flows.

The two dashed rectangles just visually cluster the first two and last two activities; there are no special events or gateways.

Now the options:

A. Activities that are in the dashed rectangle must exchange data.BPMN Groups say nothing about data exchange; this is incorrect.

B. The activities are executed as if the dashed rectangles do not exist.This matches the BPMN definition of a Group artifact and is correct.

C. Canceling "Notify Customer" will cancel the result of "Deliver Product".That would require atransaction subprocess with cancel behavior, not just a Group.

D. "Verify Credit" and "Process Payment" are executed in parallel. "Deliver Product" and "Notify Customer" are executed in parallel.Parallelism requires a parallel gateway or similar construct; here, a simple sequence flow shows they are executedsequentially.

Therefore, the correct statement is that thedashed rectangles have no execution effect: optionB.

TheAs-Is processis used as a basis for To-Be modeling when thecurrent process exists and is still relevant, even if it needs modification—for example, whennew regulatory rules require adjustments. Regulatory changes mean the process structure stays largely valid, but must be updated to meet compliance requirements.

Options A and D are incorrect because if a process is new or undefined, no As-Is model exists.

Option B is incorrect becauseradically changed requirementstypically justify designing a fresh To-Be process without depending on the existing one.

BPMN distinguishes between:

Embedded (non-reusable) Sub-Processes

Event Sub-ProcessesandCall Activities

For anEmbedded Sub-Process:

Its life cycle iscontrolled by the parent process; the subprocess starts when the token enters it.

Therefore, itsStart Event (if drawn) must be of type “None”. No Message, Signal, Timer, or other trigger types are allowed for the start of a normal embedded subprocess; those trigger types are reserved forEvent Sub-Processesand top-level processes.

So, “All Start Events for an Embedded Sub-Process must be of which type?” →None.

Options A, B, and C are valid Start Event trigger types, butnotfor a standard embedded subprocess.