100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 330
After a corrective decision on Critical-path-choice, which independent evidence most directly verifies the result ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.
- Inspect change analysis across affected engineering disciplines and the final governance decision. Reconcile the result with the current approved decision baseline.
- Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit.
- Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential.
Explanation
Correct Answer
C:This checks the actual mechanism rather than merely declaring success: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit. The desired observed result is The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The result is recorded in the project controls. [R158 R158-Q0330; case R158-C083; CAPM domain 2, task 2.2; source CPM.]
Incorrect Answers
A:The proposed verify (Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.) comes from a different Predictive project schedule and methods situation: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. It does not resolve or independently test the stated issue: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Here, the relevant check is Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit. [R158 R158-Q0330; case R158-C083; CAPM domain 2, task 2.2; source CPM.]
B:The proposed verify (Inspect change analysis across affected engineering disciplines and the final governance decision. Reconcile the result with the current approved decision baseline.) comes from a different Predictive project schedule and methods situation: A client requests a larger refrigeration unit that affects power demand, structural loads and installation cost. It does not resolve or independently test the stated issue: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Here, the relevant check is Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit. [R158 R158-Q0330; case R158-C083; CAPM domain 2, task 2.2; source CPM.]
D:This is a tempting but unsupported shortcut in this case: Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential. It does not show that The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The result is recorded in the project controls. [R158 R158-Q0330; case R158-C083; CAPM domain 2, task 2.2; source CPM.]
Question 331
Which statement most accurately flags a misleading shortcut to avoid in this Critical-path-choice case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The result is recorded in the project controls.
- Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit.
- Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Record the rationale before the next commitment.
- Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential.
Explanation
Correct Answer
D:The shortcut is mistaken: Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential. The appropriate response is to identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Record the rationale before the next commitment.
Incorrect Answers
A:This is a relevant outcome to seek after the decision: The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The result is recorded in the project controls. It is not an unsupported assumption.
B:This is an appropriate independent test of the proposed decision: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit. It is not the invalid shortcut.
C:This is a supported decision, not the unsupported claim: Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Record the rationale before the next commitment. It responds to the actual project issue: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task.
Question 332
Select THREE consistent elements of the Critical-path-choice case: appropriate decision, verification, and observable success condition. During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Calculate schedule variance as EV minus PV, yielding negative $15,000 of budget-valued schedule variance. Record the rationale before the next commitment.
- Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit.
- The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The result is recorded in the project controls.
- Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential.
- Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Record the rationale before the next commitment.
- Quality evidence demonstrates whether delivered units meet the defined requirement. The result is recorded in the project controls.
Explanation
Correct Answer
B:This checks the actual mechanism rather than merely declaring success: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit. The desired observed result is The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The result is recorded in the project controls. [R158 R158-Q0332; case R158-C083; CAPM domain 2, task 2.2; source CPM.]
C:The stated result demonstrates the case acceptance condition: The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The result is recorded in the project controls. It depends on the decision Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Record the rationale before the next commitment.
E:The case evidence identifies Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. The specified decision directly addresses it: Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Record the rationale before the next commitment. This can be checked using Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit. [R158 R158-Q0332; case R158-C083; CAPM domain 2, task 2.2; source CPM.]
Incorrect Answers
A:This option concerns a different Predictive project schedule and methods situation: A predictive project has PV=$90,000 and EV=$75,000 at the review date. For the reported case, use this verification: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit.
D:This is a tempting but unsupported shortcut in this case: Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential. It does not show that The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The result is recorded in the project controls. [R158 R158-Q0332; case R158-C083; CAPM domain 2, task 2.2; source CPM.]
F:This option concerns a different Predictive project schedule and methods situation: A manufacturing project must verify at most two critical defects per 1,000 units, but the team reports only completion of inspection paperwork. For the reported case, use this verification: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Retain the initiating evidence for audit.
Question 333
Which project-management decision best addresses the Critical-path-choice situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Decompose the approved project scope into deliverable-oriented components and work packages that can be planned and controlled. Record the rationale before the next commitment.
- Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review.
- Decompose the approved project scope into deliverable-oriented components and work packages that can be planned and controlled. Document impacted stakeholders and the decision owner at the review.
- Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential.
Explanation
Correct Answer
B:The case evidence identifies Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. The specified decision directly addresses it: Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review. This can be checked using Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. [R158 R158-Q0333; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
Incorrect Answers
A:The proposed action (Decompose the approved project scope into deliverable-oriented components and work packages that can be planned and controlled. Record the rationale before the next commitment.) comes from a different Predictive project schedule and methods situation: A project WBS has vague headings such as weekly calls and team morale but lacks identifiable deliverables for the security audit. It does not resolve or independently test the stated issue: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Here, the relevant check is Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. [R158 R158-Q0333; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
C:The proposed action (Decompose the approved project scope into deliverable-oriented components and work packages that can be planned and controlled. Document impacted stakeholders and the decision owner at the review.) comes from a different Predictive project schedule and methods situation: A project WBS has vague headings such as weekly calls and team morale but lacks identifiable deliverables for the security audit. It does not resolve or independently test the stated issue: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Here, the relevant check is Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. [R158 R158-Q0333; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
D:This is a tempting but unsupported shortcut in this case: Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential. It does not show that The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence. [R158 R158-Q0333; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
Question 334
After a corrective decision on Critical-path-choice, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential.
- Check 75,000−90,000=−15,000 and distinguish this cost-denominated metric from calendar days. Retain the initiating evidence for audit.
- Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Reconcile the result with the current approved decision baseline.
- Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. The desired observed result is The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence. [R158 R158-Q0334; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential. It does not show that The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence. [R158 R158-Q0334; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
B:This option concerns a different Predictive project schedule and methods situation: A predictive project has PV=$90,000 and EV=$75,000 at the review date. For the reported case, use this verification: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline.
C:The proposed verify (Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Reconcile the result with the current approved decision baseline.) comes from a different Predictive project schedule and methods situation: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. It does not resolve or independently test the stated issue: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Here, the relevant check is Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. [R158 R158-Q0334; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
Question 335
Which statement most accurately flags a misleading shortcut to avoid in this Critical-path-choice case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence.
- Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline.
- Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential.
- Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
C:The shortcut is mistaken: Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential. The appropriate response is to identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:This is a relevant outcome to seek after the decision: The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence. It is not an unsupported assumption.
B:This is an appropriate independent test of the proposed decision: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.
D:This is a supported decision, not the unsupported claim: Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task.
Question 336
Select THREE consistent elements of the Critical-path-choice case: appropriate decision, verification, and observable success condition. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Apply the approved quality plan's sampling and defect criteria and escalate nonconforming test results. Record the rationale before the next commitment.
- The activity has four days of total float before it threatens the controlling finish date. The decision can be traced to the review evidence.
- Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review.
- Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential.
- Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline.
- The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence.
Explanation
Correct Answer
C:The case evidence identifies Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. The specified decision directly addresses it: Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review. This can be checked using Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. [R158 R158-Q0336; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
E:This checks the actual mechanism rather than merely declaring success: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. The desired observed result is The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence. [R158 R158-Q0336; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
F:The stated result demonstrates the case acceptance condition: The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence. It depends on the decision Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:This option concerns a different Predictive project schedule and methods situation: A manufacturing project must verify at most two critical defects per 1,000 units, but the team reports only completion of inspection paperwork. For the reported case, use this verification: Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline.
B:The proposed outcome (The activity has four days of total float before it threatens the controlling finish date. The decision can be traced to the review evidence.) comes from a different Predictive project schedule and methods situation: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. It does not resolve or independently test the stated issue: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. Here, the relevant check is Calculate both path lengths as 8+4=12 and 13+4=17 days and inspect the dependency network. Reconcile the result with the current approved decision baseline. [R158 R158-Q0336; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
D:This is a tempting but unsupported shortcut in this case: Adding every parallel activity duration 8+13+4=25 falsely treats concurrent branches as sequential. It does not show that The milestone is based on the 17-day longest network path and the shorter branch has five days of path-length margin. The decision can be traced to the review evidence. [R158 R158-Q0336; case R158-C084; CAPM domain 2, task 2.2; source CPM.]
Question 337
Which project-management decision best addresses the Total-float-computation situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Compute total float as late start minus early start, giving four days under the stated unconstrained network. Record the rationale before the next commitment.
- Identify the procurement branch as the controlling longer path and plan the milestone at 17 days, assuming no other constraints. Document impacted stakeholders and the decision owner at the review.
- Define manageable work packages and then identify, sequence and estimate the activities required to produce them. Document impacted stakeholders and the decision owner at the review.
- Calling any nonzero float a four-day increase in the overall project duration confuses scheduling flexibility with extension approval.
Explanation
Correct Answer
A:Compute total float as late start minus early start, giving four days under the stated unconstrained network. Record the rationale before the next commitment. To verify the specified result, verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.
Incorrect Answers
B:This option concerns a different Predictive project schedule and methods situation: Two parallel activities lead to the same milestone: engineering takes 8 days, procurement 13 days, followed by a common 4-day commissioning task. For the reported case, use this verification: Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.
C:This option concerns a different Predictive project schedule and methods situation: A project team schedules the whole data-center migration as one eight-month activity without decomposing its scoped work package into executable tasks. For the reported case, use this verification: Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.
D:This is a tempting but unsupported shortcut in this case: Calling any nonzero float a four-day increase in the overall project duration confuses scheduling flexibility with extension approval. It does not show that The activity has four days of total float before it threatens the controlling finish date. The result is recorded in the project controls. [R158 R158-Q0337; case R158-C085; CAPM domain 2, task 2.2; source CPM.]
Question 338
After a corrective decision on Total-float-computation, which independent evidence most directly verifies the result ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Check 75,000−90,000=−15,000 and distinguish this cost-denominated metric from calendar days. Reconcile the result with the current approved decision baseline.
- Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.
- Trace work packages to scoped audit deliverables and identify the accountable control or acceptance point. Retain the initiating evidence for audit.
- Calling any nonzero float a four-day increase in the overall project duration confuses scheduling flexibility with extension approval.
Explanation
Correct Answer
B:Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit. The expected result is the activity has four days of total float before it threatens the controlling finish date. The result is recorded in the project controls.
Incorrect Answers
A:This option concerns a different Predictive project schedule and methods situation: A predictive project has PV=$90,000 and EV=$75,000 at the review date. For the reported case, use this verification: Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.
C:The proposed verify (Trace work packages to scoped audit deliverables and identify the accountable control or acceptance point. Retain the initiating evidence for audit.) comes from a different Predictive project schedule and methods situation: A project WBS has vague headings such as weekly calls and team morale but lacks identifiable deliverables for the security audit. It does not resolve or independently test the stated issue: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. Here, the relevant check is Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit. [R158 R158-Q0338; case R158-C085; CAPM domain 2, task 2.2; source CPM.]
D:This is a tempting but unsupported shortcut in this case: Calling any nonzero float a four-day increase in the overall project duration confuses scheduling flexibility with extension approval. It does not show that The activity has four days of total float before it threatens the controlling finish date. The result is recorded in the project controls. [R158 R158-Q0338; case R158-C085; CAPM domain 2, task 2.2; source CPM.]
Question 339
Which statement most accurately flags a misleading shortcut to avoid in this Total-float-computation case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- The activity has four days of total float before it threatens the controlling finish date. The result is recorded in the project controls.
- Compute total float as late start minus early start, giving four days under the stated unconstrained network. Record the rationale before the next commitment.
- Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.
- Calling any nonzero float a four-day increase in the overall project duration confuses scheduling flexibility with extension approval.
Explanation
Correct Answer
D:The shortcut is mistaken: Calling any nonzero float a four-day increase in the overall project duration confuses scheduling flexibility with extension approval. The appropriate response is to compute total float as late start minus early start, giving four days under the stated unconstrained network. Record the rationale before the next commitment.
Incorrect Answers
A:This is a relevant outcome to seek after the decision: The activity has four days of total float before it threatens the controlling finish date. The result is recorded in the project controls. It is not an unsupported assumption.
B:This is a supported decision, not the unsupported claim: Compute total float as late start minus early start, giving four days under the stated unconstrained network. Record the rationale before the next commitment. It responds to the actual project issue: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion.
C:This is an appropriate independent test of the proposed decision: Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit. It is not the invalid shortcut.
Question 340
Which observed result supports acceptance of the Total-float-computation corrective decision ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- The WBS covers authorized outputs without mistaking recurring meetings for the deliverables themselves. The result is recorded in the project controls.
- Calling any nonzero float a four-day increase in the overall project duration confuses scheduling flexibility with extension approval.
- The activity has four days of total float before it threatens the controlling finish date. The result is recorded in the project controls.
- The approved plan reflects coherent cross-functional impacts instead of isolated equipment changes. The result is recorded in the project controls.
Explanation
Correct Answer
C:The stated result demonstrates the case acceptance condition: The activity has four days of total float before it threatens the controlling finish date. The result is recorded in the project controls. It depends on the decision Compute total float as late start minus early start, giving four days under the stated unconstrained network. Record the rationale before the next commitment.
Incorrect Answers
A:The proposed outcome (The WBS covers authorized outputs without mistaking recurring meetings for the deliverables themselves. The result is recorded in the project controls.) comes from a different Predictive project schedule and methods situation: A project WBS has vague headings such as weekly calls and team morale but lacks identifiable deliverables for the security audit. It does not resolve or independently test the stated issue: An activity can start no earlier than project day 5 but can start as late as day 9 without delaying the current network completion. Here, the relevant check is Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit. [R158 R158-Q0340; case R158-C085; CAPM domain 2, task 2.2; source CPM.]
B:This is a tempting but unsupported shortcut in this case: Calling any nonzero float a four-day increase in the overall project duration confuses scheduling flexibility with extension approval. It does not show that The activity has four days of total float before it threatens the controlling finish date. The result is recorded in the project controls. [R158 R158-Q0340; case R158-C085; CAPM domain 2, task 2.2; source CPM.]
D:This option concerns a different Predictive project schedule and methods situation: A client requests a larger refrigeration unit that affects power demand, structural loads and installation cost. For the reported case, use this verification: Verify ES=5, LS=9 and the equivalent LF−EF calculation for the same activity. Retain the initiating evidence for audit.
Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests