Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe Exam AD0-E903 Topic 2 Question 4 Discussion

Actual exam question for Adobe's AD0-E903 exam
Question #: 4
Topic #: 2
[All AD0-E903 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

In this scenario, the fact that Task 2's start date did not shift automatically despite its dependency on Task 1 suggests that a manual override was applied, resulting in a Task Constraint of 'Must Start On.' This type of constraint locks a task to a specific date, preventing it from dynamically adjusting based on changes to its predecessor. The other options either do not explain why the start date remained static or involve user-specific scheduling conflicts, which would not affect the system-driven date adjustment.


by Valentin at Sep 14, 2024, 08:41 AM

Limited Time Offer

25%

Off

Get Premium AD0-E903 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Bobbie
4 months ago
That's a good point, Leonardo. It could be a manual change by the project owner that caused the issue.
upvoted 0 times
...
Leonardo
4 months ago
I disagree, I believe it's because of option B. The project owner must have manually changed the start date.
upvoted 0 times
...
Dominga
4 months ago
Haha, what if the primary assignee had scheduled a vacation during the new planned start date for Task 2? That would be a classic case of bad timing, just like option C describes.
upvoted 0 times
...
Melissia
4 months ago
Hmm, I think the primary assignee must have submitted a Commit Date for the previous planned start date on Task 2, even though the project owner didn't accept it. That's likely the reason, as stated in option A.
upvoted 0 times
...
Chanel
4 months ago
The planned start date of Task 2 remained the same because the project owner manually changed the Task Constraint to Must Start On, as mentioned in option B.
upvoted 0 times
Glen
3 months ago
Yeah, that could have also played a role in keeping the planned start date the same.
upvoted 0 times
...
Halina
3 months ago
Maybe the primary assignee had already submitted a Commit Date for the previous planned start date on Task 2.
upvoted 0 times
...
Felix
4 months ago
That makes sense, it would explain why the planned start date didn't shift.
upvoted 0 times
...
Celia
4 months ago
I agree, it's important to be aware of how manual changes can impact the project schedule.
upvoted 0 times
...
Son
4 months ago
That makes sense, the manual change to the Task Constraint would definitely keep the planned start date static.
upvoted 0 times
...
Mira
4 months ago
I think the project owner manually changed the Task Constraint of Task 2 to Must Start On.
upvoted 0 times
...
...
Bobbie
4 months ago
I think the planned start date of Task 2 remained the same because of option A.
upvoted 0 times
...

Save Cancel