Refer to the exhibit. Based on the error log, which task has a dependency issue?
T2's error log shows its predecessor finishing after T2's scheduled start, violating finish-to-start logic. Unlike T3, which has no predecessor constraint, T2 depends on T1's completion, so the schedule conflict confirms the dependency issue. This satisfies the stem's requirement to identify the task with a dependency problem.
Why this answer
The error log shows 'Dependency not met for T2: predecessor T1 not completed'. This indicates T2 has a dependency issue because its predecessor task (T1) has not finished, violating the logical relationship defined in the project schedule. In project management, a finish-to-start dependency requires the predecessor to be 100% complete before the successor can begin.
Exam trap
PMI often tests the distinction between which task has the dependency issue (the successor) versus which task is causing the issue (the predecessor), leading candidates to incorrectly select the predecessor task (T1) instead of the successor (T2).
How to eliminate wrong answers
Option A is wrong because T3 is not mentioned in the error log; the dependency error is explicitly for T2, not T3. Option B is wrong because T1 is the predecessor that is not completed, but the dependency issue is on the successor task (T2), not on T1 itself. Option C is wrong because T4 is not referenced in the error log; the error is specifically about T2's dependency on T1.