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

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.

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.

In BPMN, when anExpanded Sub-Processcontains activities (here:CandD)without any Sequence Flows between them, there isno defined execution orderimplied by their vertical or horizontal placement. Unless there are explicit sequence flows or gateway logic:

Neither “C then D” nor “D then C” is mandated.

They may be performed in any order, potentially overlapping, or by ad-hoc control external to the diagram.

Therefore the only correct statement is thattheir order is undefined in the diagram.