If a task has an upstream task that is unassigned, the downstream task does not get assigned.

If a task has an upstream task that is unassigned, the downstream task does not get assigned.

• A. Downstream may still be assigned if other conditions permit
• B. False
• C. True
• D. It depends on upstream priority

Answer: (C)

In Field Service Management, tasks are linked in a sequence, and a downstream task is typically blocked until its upstream task has moved forward (or has an assignment). If the upstream task is unassigned, there’s no active work or resource allocated to it, so the system prevents the downstream task from being assigned as well. This keeps work flowing in the intended order and avoids pulling resources into tasks that depend on prerequisites not yet in motion. So the statement is true: the downstream task does not get assigned when the upstream task is unassigned. In practice, you’ll often see the downstream task marked as Blocked or Pending until the upstream task gets assigned or progresses. The other options would imply exceptions to this default sequencing, which isn’t how the typical dependency rule operates.

In Field Service Management, tasks are linked in a sequence, and a downstream task is typically blocked until its upstream task has moved forward (or has an assignment). If the upstream task is unassigned, there’s no active work or resource allocated to it, so the system prevents the downstream task from being assigned as well. This keeps work flowing in the intended order and avoids pulling resources into tasks that depend on prerequisites not yet in motion. So the statement is true: the downstream task does not get assigned when the upstream task is unassigned. In practice, you’ll often see the downstream task marked as Blocked or Pending until the upstream task gets assigned or progresses. The other options would imply exceptions to this default sequencing, which isn’t how the typical dependency rule operates.