List of questions
Related questions
Question 51 - AD0-E903 discussion
Task 2 has a 5-day duration, is tied to Task 1 with a predecessor, and is expected to begin once Task 1 is completed. Due to a resource availability conflict, Task 1 was rescheduled to start 1 week later. Once Task 1 was rescheduled, the planned start date on Task 2 did not dynamically shift by 5 days as expected but instead remained the same planned start date that existed before the change to Task 1.
What may have caused the planned start date of Task 2 to remain the same?
A.
The primary assignee had already submitted a Commit Date for the previous planned start date on Task 2, even though the project owner did not accept this Commit Date, the project plan made this date a Must Start On Constraint on Task 2.
B.
The project owner has at some point made a manual change to the planned start date of Task 2, which has in turn changed the Task Constraint of Task 2 to Must Start On.
C.
The primary assignee had scheduled time off during the new planned start date that Task 2 should have shifted toward. Due to this time off scheduled the date remained the same.
D.
The project owner has at some point made a manual change to the Task Constraint of Task 2 to As Soon As Possible, which has forced the date of Task 2 to be static.
Your answer:
0 comments
Sorted by
Leave a comment first