In the small BPMN fragment, element B is an End Event drawn with a thick (bold) border , which in BPMN indicates a Terminate End Event .

Terminate End Event semantics in OMG BPMN:

When a token arrives at a Terminate End Event, it immediately ends the entire process instance (or the entire scope/subprocess) , regardless of any other active tokens in parallel branches.

It therefore “interrupts” the process , stopping all ongoing activities for that instance.

Evaluating the options:

A. throws an error – That would be an Error End Event (with a lightning-bolt icon), not a bold-bordered circle.

B. generates a token – Token generation is behavior of Start Events , not End Events.

C. consumes a token – All End Events consume the arriving token; this is true but not distinctive to this specific symbol.

D. interrupts the process – This is the defining behavior of a Terminate End Event , so this is the correct answer.

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

In BPMN:

A Catching Intermediate Timer Event placed in the normal sequence flow between 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 A shows exactly this pattern:

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

Why the others are not correct:

Option B visually suggests the timer is before A or attached differently, not clearly expressing “after A, then wait, then B.”

Option C uses a boundary timer event on A. A boundary timer on A represents a timeout during A’s execution (e.g., if A takes longer than one hour, do something), not a guaranteed wait period after A finishes.

Option D introduces 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” is Option A .

In most enterprise and BPM frameworks , including those aligned with OMG value chain and BPMN modeling , organizational functions are split into:

Primary (core) activities – directly create value for the customer (e.g., operations, marketing & sales, service).

Support activities – enable and support the core, but do not directly deliver the product/service to the customer (e.g., HR, accounting, IT, procurement).

Among the options:

Human resources is classically modeled as a support function :

It provides recruitment, training, development, performance management, and policy support .

In OMG-based enterprise models, HR is often shown as a shared service or support process that other processes call upon (e.g., “Hire employee,” “Onboard staff,” “Manage skills and competencies”).

Why the others are less appropriate as the answer:

A. Marketing – Typically considered a primary/value-creating function , directly involved in demand creation, customer communication, and revenue generation.

B. Accounting – Also a support function in many models, but in value-chain diagrams and BPM teaching examples, HR is the most universally and explicitly labeled as “support” .

D. Research and development – Often considered technology development ; in some value chains it’s a support activity, but in many industries (pharma, tech, engineering) it is a core strategic function .

Therefore, the function most generally and clearly considered a support function in BPM and OMG-aligned organizational modeling is Human resources .

In a process-focused or process-centric organization , a formal governing body (often called a Process Council , BPM Steering Committee , or similar) is responsible for overseeing enterprise processes. OMG-aligned BPM governance frameworks typically assign such a body the role to:

Provide cross-enterprise oversight of major processes

Resolve conflicts between process owners and functional managers

Prioritize process improvement and transformation initiatives

Allocate resources (budget, people, tools) to the most critical process changes based on strategy and value

This is exactly reflected in Option C :

Prioritize initiatives and allocate resources

Why the other options don’t fit:

A. Firefight business problems – Governance bodies should not operate primarily as reactive “firefighters”; they work at a strategic and prioritization level , not as an escalation helpdesk.

B. Define the organization's business strategy – Strategy is defined by the executive leadership ; the process governance body ensures processes align with and execute that strategy , but typically does not define it.

D. Define the organization's senior executive structure – That is an organizational design / board-level matter, not a role of a process governance council.

Therefore, in a process-centric organization, the formal process-governing body should prioritize initiatives and allocate resources , making C correct.

===============

In OMG BPM, process discovery refers to uncovering and making explicit the as-is state of business processes. The primary goal is to document and visualize what actually happens—before analysis, redesign, or automation.

Option A correctly describes this: Process discovery captures, documents, and makes explicit the organizational understanding of current business processes.

Option B refers to process optimization , which comes later.

Option C is part of project initiation, not discovery itself.

Option D refers to process implementation in a BPMS.

Thus, the correct characteristic of process discovery is making current processes explicit .

Process topology refers to the sequence and structure of activities—the flow of tasks.

The only option that directly discovers process flow and ordering is:

✔ C: Discovering the previous and next tasks for each task.

This is a classic method in BPM to reconstruct the end-to-end process and map dependencies.

Other options focus on metrics, decisions, or data—not the structural topology .

In BPMN, parallel flow means that more than one path is taken simultaneously . Besides using a Parallel Gateway, one legitimate way is:

An activity with multiple outgoing, unconditional Sequence Flows : each such flow is taken when the activity completes, so the paths proceed in parallel.

That is exactly what option C states: Multiple unconditional paths exit an activity → all of them are taken, which starts parallel execution.

Option A (multiple paths from an exclusive gateway) is not parallel; an exclusive gateway allows only one outgoing path per token.

Option B (multiple conditional paths) may or may not create parallelism, depending on which conditions are true; it’s not the canonical way to model parallel flow.

Option D is invalid because an exclusive gateway cannot have multiple default flows.

Hence, C is the legitimate way to commence parallel flow.