What can create a deadlock in process modeling?

Question

Options

• AA loop has been modeled.
• BA merging exclusive gateway receives multiple tokens.
• COne of many tokens reaches the end of a process.
• DA parallel merging gateway expects more tokens than existing.

• A
  8% (2)
• B
  4% (1)
• C
  4% (1)
• D
  85% (22)

Explanation

A parallel merging gateway (AND-join) waits until it receives all expected incoming tokens before allowing the process to continue - if fewer tokens exist than the gateway expects (e.g., because a branch was never activated), the gateway waits forever, causing a deadlock. Option A is wrong because a loop, while potentially causing infinite cycles, doesn't inherently block the process from progressing. Option B describes a problem with an exclusive (XOR) merging gateway receiving multiple tokens, which causes unintended behavior but not a classic deadlock - the tokens still flow. Option C is the opposite of a deadlock; one token reaching the end simply completes one path, which is normal behavior in parallel flows.

Memory tip: Think of the AND-join as a meeting room that won't open until everyone on the invite list arrives - if someone never shows up, the door stays locked forever. "Parallel = all must arrive, or you're stuck."

No community discussion yet for this question.