Which elements can be configured to customize task dependencies in project initiation? (Select two.)

Question

Options

• ARole-based assignments
• BTask predecessors
• CTask constraints
• DGroup-level sharing permissions

• A
  17% (6)
• B
  75% (27)
• D
  8% (3)

Explanation

Task predecessors (B) and task constraints (C) are the two elements directly used to customize task dependencies during project initiation. Predecessors define the sequential relationship between tasks (e.g., Task B cannot start until Task A finishes), while constraints set time-based rules (e.g., a task must start no earlier than a specific date) - both directly shape how tasks depend on and relate to each other in the project schedule.

Why the distractors are wrong:

• A (Role-based assignments) controls who does a task, not when or in what order tasks happen - it's about resource allocation, not dependency logic.
• D (Group-level sharing permissions) governs who can see or edit the project, which is an access control setting, not a scheduling or dependency configuration.

Memory tip: Think "dependencies = sequence + timing" - predecessors handle sequence (what comes before), constraints handle timing (when it can happen). Assignments and permissions answer "who," not "when."

No community discussion yet for this question.