Which TWO of the following are true about 'Wait for completion' in an activity?
'Wait for completion' halts the engine's progression at that activity, so subsequent activities in the flow do not start until the current one finishes. This satisfies the requirement that dependent work is not triggered prematurely, keeping execution order aligned with actual completion.
Why this answer
Option B is correct because 'Wait for completion' halts the activity's engine progression until the referenced activity or task reaches a completed state, preventing downstream processing from advancing prematurely. Option D is correct because enabling this setting establishes a dependency relationship, making the current activity contingent on the completion of the specified task before it can proceed. Option A is incorrect since this behavior is not limited to approvals; it applies to any activity type that supports the wait configuration.
Option C is incorrect because waiting for completion suspends progression rather than forcing the case to close. Option E is incorrect because 'Wait for completion' is an opt-in setting, not the default behavior for all tasks.
Exam trap
CIS-HR often tests the misconception that 'Wait for completion' is only for approvals or that it forces case closure, confusing it with other workflow settings like 'Wait for condition' or 'End workflow'.