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

Management documents without any External Links or URL:

In theBusiness Motivation Model (BMM):

Courses of Action(Strategies and Tactics) representhowthe organization intends to achieve its Ends (Goals and Objectives).

Directives(Business Policies and Business Rules)governandconstrainhow those Courses of Action are carried out.

So:

Directivesspecify what is allowed, required, or prohibited in implementing strategies and tactics.

This is why BMM explicitly states thatDirectives govern Courses of Action.

Why others are incorrect:

Objectives(B) are measurable targets (Ends), not governing elements.

Internal Influencers(C) affect assessments and motivation but donotdirectly govern Courses of Action.

Business Processes(D) are operational implementations, not governance elements in BMM terminology.

Thus, the correct governing elements for Courses of Action in BMM areDirectives.

In process and performance analysis, aheat mapis a diagram where colors (often gradients from green to red) are used to show intensity, volume, risk, performance, or other metrics across processes, activities, or dimensions. So it is fundamentally agraphical color displayused to visualize data.

TheSarbanes–Oxley Act (SOX)of 2002 was enacted to restore public confidence in corporate financial reporting after major accounting scandals.

Itskey objectiveis:

To ensureexecutive accountabilityfor accurate financial reporting

CEOs and CFOs mustcertify the accuracyof financial statements

Internal controls must be documented, tested, and auditable

Thus, the correct answer isD.

In OMG’s BPMN usage guidance and common practice, BPMN models are often discussed inthree levels of detail:

Level 1 – Descriptive (non-technical) modeling

Level 2 – Analytical (detailed but still platform-independent) modeling

Level 3 – Executable (implementation-ready) modeling

Descriptive modeling(Level 1) deliberately uses asmall, business-oriented subset of BPMN symbols. It avoids technical execution attributes and is meant primarily fordocumentation and communication among business stakeholdersacross the organization: managers, business analysts, and subject-matter experts.

Because it is simple, easy to read, and does not assume knowledge of execution semantics or tooling, it isthe easiest level to communicate across the organization.

The other options do not match OMG’s three levels:

Event modelingandvisual modelingare not defined as standard BPMN levels.

Executable modelingis Level 3, aimed at implementation, and isnotthe easiest for broad communication because it introduces technical details (data, error handling, engine-specific attributes).

Therefore, the correct answer isdescriptive modeling.

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.

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.

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.