If a task has an upstream task that is assigned, the downstream task does not start until the upstream task is completed.

If a task has an upstream task that is assigned, the downstream task does not start until the upstream task is completed.

• A. Downstream can start before upstream completes
• B. Downstream task does not start until upstream completion
• C. Downstream starts immediately after upstream assignment
• D. Downstream is canceled if upstream fails

Answer: (B)

In this type of workflow, downstream work is gated by the completion of upstream work. Even if the upstream task has been assigned to a resource, it isn’t considered ready for downstream work until it is finished. This ensures the downstream task has all the prerequisites and data it needs to proceed. So, the downstream task should not start until the upstream task is completed because the flow depends on the upstream's results or state being fully finished. For example, diagnosing a issue (upstream) must be completed before applying a fix (downstream) can begin. The other ideas would bypass the actual progress of work: starting downstream before upstream finishes ignores the dependency; starting immediately after assignment ignores the need for completion; canceling downstream whenever upstream fails is not a universal rule—failure handling often involves rework or re-scheduling rather than automatic cancellation.

In this type of workflow, downstream work is gated by the completion of upstream work. Even if the upstream task has been assigned to a resource, it isn’t considered ready for downstream work until it is finished. This ensures the downstream task has all the prerequisites and data it needs to proceed.

So, the downstream task should not start until the upstream task is completed because the flow depends on the upstream's results or state being fully finished. For example, diagnosing a issue (upstream) must be completed before applying a fix (downstream) can begin.

The other ideas would bypass the actual progress of work: starting downstream before upstream finishes ignores the dependency; starting immediately after assignment ignores the need for completion; canceling downstream whenever upstream fails is not a universal rule—failure handling often involves rework or re-scheduling rather than automatic cancellation.