What do Timer Events and Conditional Events have in common? Note: There are 2 correct answers to this question.

Question

Options

• AThey can only be used as start events.
• BThey can only be catching-type events.
• CThey can only be throwing-type events.
• DThey cannot be used as end events.

• A
  75% (47)
• C
  16% (10)
• D
  10% (6)

Explanation

Both Timer Events and Conditional Events are always passive/reactive - they wait for something to happen (a time trigger or a condition becoming true), which means they are inherently catching-type events (B correct) and serve as triggers to initiate or react within a process, making them valid as start events (A correct).

Option C is wrong because neither event type can be throwing - you cannot "throw" a timer or a condition; these events only receive/detect signals, never emit them. Option D is a tempting distractor: while it's true they don't appear as end events, the correct reason is captured more precisely by A (they function as start/trigger events) and B (they're catching-only), making D redundant rather than an independent insight the question is testing.

Memory tip: Think "Timer and Conditional events are listeners, not speakers" - they catch (never throw), and they kick things off (start events). If you remember they always listen for a trigger, both A and B follow naturally.

No community discussion yet for this question.