Means this task must be completed before any downstream tasks can be started.

• A. A task that must be completed after downstream tasks
• B. A task that can be started at any time
• C. Means this task must be completed before any downstream tasks can be started.
• D. A task that starts and ends simultaneously with others

Answer: (C)

The main concept here is a dependency or prerequisite in task sequencing. When a task must be completed before any downstream tasks can start, it serves as a blocking prerequisite for the rest of the work. This means the flow can’t move forward to dependent tasks until this one is finished, ensuring that upstream work, approvals, data, or setup is in place before subsequent steps begin. In ServiceNow FSM and similar planning contexts, modeling this relationship keeps the work orderly, aligns with resource availability, and reduces the risk of starting tasks without the necessary foundation.

Why this fits best: it explicitly enforces a strict order—upstream task must finish before downstream tasks can begin. The other descriptions describe different timing relationships: finishing after others, starting at any time, or running in parallel with others. Those do not capture the notion of a required, finishing-before-downstream dependency.