PMI CAPM Exam Dumps, Practice Test Questions

100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

PMI CAPM Premium Bundle
$79.97
$59.98

CAPM Premium Bundle

  • Premium File: 688 Questions & Answers. Last update: Nov 2, 2026
  • Training Course: 123 Video Lectures
  • Study Guide: 719 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

CAPM Premium Bundle

PMI CAPM Premium Bundle
  • Premium File: 688 Questions & Answers. Last update: Nov 2, 2026
  • Training Course: 123 Video Lectures
  • Study Guide: 719 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$79.97
$59.98

PMI CAPM Practice Test 2

Question 10

After a corrective decision on Program-versus-portfolio grouping, 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: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Verify the risk register links the delivery trigger to a named response and procurement lead time. Reconcile the result with the current approved decision baseline.
  2. Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit.
  3. Inspect documented approval, impact assessment and updated authorized baseline. Retain the initiating evidence for audit.
  4. Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies.

Explanation

Correct Answer

B:

This checks the actual mechanism rather than merely declaring success: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit. The desired observed result is Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls. [R158 R158-Q0010; case R158-C003; CAPM domain 1, task 1.1; source ECO.]

Incorrect Answers

A:

This option concerns a different Project life cycles and processes situation: A supplier may miss a future delivery date; the team has named a backup supplier but has not set a trigger or response owner. For the reported case, use this verification: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit.

C:

The proposed verify (Inspect documented approval, impact assessment and updated authorized baseline. Retain the initiating evidence for audit.) comes from a different Project life cycles and processes situation: During a factory automation project an engineer begins a new production line without delegated approval because it improves technical performance. It does not resolve or independently test the stated issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Here, the relevant check is Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit. [R158 R158-Q0010; case R158-C003; CAPM domain 1, task 1.1; source ECO.]

D:

This is a tempting but unsupported shortcut in this case: Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies. It does not show that Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls. [R158 R158-Q0010; case R158-C003; CAPM domain 1, task 1.1; source ECO.]

Question 11

Which statement most accurately flags a misleading shortcut to avoid in this Program-versus-portfolio grouping case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Record the rationale before the next commitment.
  2. Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit.
  3. Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls.
  4. Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies.

Explanation

Correct Answer

D:

The shortcut is mistaken: Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies. The appropriate response is to manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Record the rationale before the next commitment.

Incorrect Answers

A:

This is a supported decision, not the unsupported claim: Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Record the rationale before the next commitment. It responds to the actual project issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments.

B:

This is an appropriate independent test of the proposed decision: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit. It is not the invalid shortcut.

C:

This is a relevant outcome to seek after the decision: Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls. It is not an unsupported assumption.

Question 12

Select THREE consistent elements of the Program-versus-portfolio grouping 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: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Assess proposed changes through the project's governance and obtain appropriate authority before adding new scope. Record the rationale before the next commitment.
  2. Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls.
  3. Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Record the rationale before the next commitment.
  4. Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit.
  5. Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies.
  6. Leaders receive accurate status and can choose a response based on real progress. The result is recorded in the project controls.

Explanation

Correct Answer

B:

The stated result demonstrates the case acceptance condition: Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls. It depends on the decision Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Record the rationale before the next commitment.

C:

The case evidence identifies A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. The specified decision directly addresses it: Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Record the rationale before the next commitment. This can be checked using Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit. [R158 R158-Q0012; case R158-C003; CAPM domain 1, task 1.1; source ECO.]

D:

This checks the actual mechanism rather than merely declaring success: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit. The desired observed result is Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls. [R158 R158-Q0012; case R158-C003; CAPM domain 1, task 1.1; source ECO.]

Incorrect Answers

A:

The proposed action (Assess proposed changes through the project's governance and obtain appropriate authority before adding new scope. Record the rationale before the next commitment.) comes from a different Project life cycles and processes situation: During a factory automation project an engineer begins a new production line without delegated approval because it improves technical performance. It does not resolve or independently test the stated issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Here, the relevant check is Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit. [R158 R158-Q0012; case R158-C003; CAPM domain 1, task 1.1; source ECO.]

E:

This is a tempting but unsupported shortcut in this case: Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies. It does not show that Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls. [R158 R158-Q0012; case R158-C003; CAPM domain 1, task 1.1; source ECO.]

F:

This option concerns a different Project life cycles and processes situation: An integration milestone is late, but a lead asks for a green status to prevent executive scrutiny. For the reported case, use this verification: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Retain the initiating evidence for audit.

Question 13

Which project-management decision best addresses the Program-versus-portfolio grouping situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Disclose the conflict promptly, follow the organization's procurement safeguards and recuse where independence is required. Record the rationale before the next commitment.
  2. Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Document impacted stakeholders and the decision owner at the review.
  3. Disclose the conflict promptly, follow the organization's procurement safeguards and recuse where independence is required. Document impacted stakeholders and the decision owner at the review.
  4. Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies.

Explanation

Correct Answer

B:

The case evidence identifies A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. The specified decision directly addresses it: Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. [R158 R158-Q0013; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

Incorrect Answers

A:

The proposed action (Disclose the conflict promptly, follow the organization's procurement safeguards and recuse where independence is required. Record the rationale before the next commitment.) comes from a different Project life cycles and processes situation: A project evaluator has a close financial interest in a vendor under consideration but plans to score proposals without telling the review panel. It does not resolve or independently test the stated issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Here, the relevant check is Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. [R158 R158-Q0013; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

C:

The proposed action (Disclose the conflict promptly, follow the organization's procurement safeguards and recuse where independence is required. Document impacted stakeholders and the decision owner at the review.) comes from a different Project life cycles and processes situation: A project evaluator has a close financial interest in a vendor under consideration but plans to score proposals without telling the review panel. It does not resolve or independently test the stated issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Here, the relevant check is Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. [R158 R158-Q0013; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

D:

This is a tempting but unsupported shortcut in this case: Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies. It does not show that Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence. [R158 R158-Q0013; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

Question 14

After a corrective decision on Program-versus-portfolio grouping, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies.
  2. Compare approved benefit measures with baseline and after-release processing times. Reconcile the result with the current approved decision baseline.
  3. Compare approved benefit measures with baseline and after-release processing times. Retain the initiating evidence for audit.
  4. Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline.

Explanation

Correct Answer

D:

This checks the actual mechanism rather than merely declaring success: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. The desired observed result is Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence. [R158 R158-Q0014; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies. It does not show that Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence. [R158 R158-Q0014; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

B:

The proposed verify (Compare approved benefit measures with baseline and after-release processing times. Reconcile the result with the current approved decision baseline.) comes from a different Project life cycles and processes situation: A sponsor measures the upgrade only by the number of screens delivered even though the business case concerns reduced claims processing time. It does not resolve or independently test the stated issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Here, the relevant check is Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. [R158 R158-Q0014; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

C:

The proposed verify (Compare approved benefit measures with baseline and after-release processing times. Retain the initiating evidence for audit.) comes from a different Project life cycles and processes situation: A sponsor measures the upgrade only by the number of screens delivered even though the business case concerns reduced claims processing time. It does not resolve or independently test the stated issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Here, the relevant check is Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. [R158 R158-Q0014; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

Question 15

Which statement most accurately flags a misleading shortcut to avoid in this Program-versus-portfolio grouping case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline.
  2. Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Document impacted stakeholders and the decision owner at the review.
  3. Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence.
  4. Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies.

Explanation

Correct Answer

D:

The shortcut is mistaken: Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies. The appropriate response is to manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Document impacted stakeholders and the decision owner at the review.

Incorrect Answers

A:

This is an appropriate independent test of the proposed decision: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.

B:

This is a supported decision, not the unsupported claim: Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments.

C:

This is a relevant outcome to seek after the decision: Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence. It is not an unsupported assumption.

Question 16

Select THREE consistent elements of the Program-versus-portfolio grouping case: appropriate decision, verification, and observable success condition. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Leaders receive accurate status and can choose a response based on real progress. The result is recorded in the project controls.
  2. Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence.
  3. Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies.
  4. Disclose the conflict promptly, follow the organization's procurement safeguards and recuse where independence is required. Document impacted stakeholders and the decision owner at the review.
  5. Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline.
  6. Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Document impacted stakeholders and the decision owner at the review.

Explanation

Correct Answer

B:

The stated result demonstrates the case acceptance condition: Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence. It depends on the decision Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Document impacted stakeholders and the decision owner at the review.

E:

This checks the actual mechanism rather than merely declaring success: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. The desired observed result is Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence. [R158 R158-Q0016; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

F:

The case evidence identifies A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. The specified decision directly addresses it: Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. [R158 R158-Q0016; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

Incorrect Answers

A:

This option concerns a different Project life cycles and processes situation: An integration milestone is late, but a lead asks for a green status to prevent executive scrutiny. For the reported case, use this verification: Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline.

C:

This is a tempting but unsupported shortcut in this case: Combining projects solely because they share a sponsor makes every portfolio a program regardless of dependencies. It does not show that Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The decision can be traced to the review evidence. [R158 R158-Q0016; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

D:

The proposed action (Disclose the conflict promptly, follow the organization's procurement safeguards and recuse where independence is required. Document impacted stakeholders and the decision owner at the review.) comes from a different Project life cycles and processes situation: A project evaluator has a close financial interest in a vendor under consideration but plans to score proposals without telling the review panel. It does not resolve or independently test the stated issue: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. Here, the relevant check is Inspect the benefits map and inter-project dependencies, distinguishing program integration from portfolio prioritization. Reconcile the result with the current approved decision baseline. [R158 R158-Q0016; case R158-C004; CAPM domain 1, task 1.1; source ECO.]

Question 17

Which project-management decision best addresses the Predictive-or-adaptive life-cycle fit situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A benefits portal team has disputed eligibility rules and expects monthly feedback that will change interface behavior. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Locking unconfirmed user needs into a full fixed specification eliminates change but does not reduce requirement uncertainty.
  2. Use an adaptive discovery and delivery approach with frequent validation of changing rules instead of freezing all details at initiation. Record the rationale before the next commitment.
  3. Record the uncertain event with probability, impact, early trigger, owner and contingent sourcing response. Document impacted stakeholders and the decision owner at the review.
  4. Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Record the rationale before the next commitment.

Explanation

Correct Answer

B:

Use an adaptive discovery and delivery approach with frequent validation of changing rules instead of freezing all details at initiation. Record the rationale before the next commitment. To verify the specified result, compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit.

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Locking unconfirmed user needs into a full fixed specification eliminates change but does not reduce requirement uncertainty. It does not show that The team adjusts the product on evidence without treating every learning cycle as an uncontrolled baseline breach. The result is recorded in the project controls. [R158 R158-Q0017; case R158-C005; CAPM domain 1, task 1.1; source ECO.]

C:

This option concerns a different Project life cycles and processes situation: A supplier may miss a future delivery date; the team has named a backup supplier but has not set a trigger or response owner. For the reported case, use this verification: Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit.

D:

The proposed action (Manage interdependent projects as a program for coordinated benefits while the portfolio still selects investments against strategy. Record the rationale before the next commitment.) comes from a different Project life cycles and processes situation: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. It does not resolve or independently test the stated issue: A benefits portal team has disputed eligibility rules and expects monthly feedback that will change interface behavior. Here, the relevant check is Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit. [R158 R158-Q0017; case R158-C005; CAPM domain 1, task 1.1; source ECO.]

Question 18

After a corrective decision on Predictive-or-adaptive life-cycle fit, 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: A benefits portal team has disputed eligibility rules and expects monthly feedback that will change interface behavior. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Review assumption-validation dates and the approved cost limit in the planning baseline. Reconcile the result with the current approved decision baseline.
  2. Check transition ownership, staff readiness criteria and post-rollout benefit measurements. Reconcile the result with the current approved decision baseline.
  3. Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit.
  4. Locking unconfirmed user needs into a full fixed specification eliminates change but does not reduce requirement uncertainty.

Explanation

Correct Answer

C:

Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit. The expected result is the team adjusts the product on evidence without treating every learning cycle as an uncontrolled baseline breach. The result is recorded in the project controls.

Incorrect Answers

A:

This option concerns a different Project life cycles and processes situation: An energy retrofit plan assumes a regulator will approve a permit, while the funding ceiling is a fixed contractual limit. For the reported case, use this verification: Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit.

B:

This option concerns a different Project life cycles and processes situation: A health system installs a new triage tool but does not assign anyone to transition daily workflows or support staff adoption. For the reported case, use this verification: Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit.

D:

This is a tempting but unsupported shortcut in this case: Locking unconfirmed user needs into a full fixed specification eliminates change but does not reduce requirement uncertainty. It does not show that The team adjusts the product on evidence without treating every learning cycle as an uncontrolled baseline breach. The result is recorded in the project controls. [R158 R158-Q0018; case R158-C005; CAPM domain 1, task 1.1; source ECO.]

Question 19

Which statement most accurately flags a misleading shortcut to avoid in this Predictive-or-adaptive life-cycle fit case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A benefits portal team has disputed eligibility rules and expects monthly feedback that will change interface behavior. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit.
  2. Use an adaptive discovery and delivery approach with frequent validation of changing rules instead of freezing all details at initiation. Record the rationale before the next commitment.
  3. Locking unconfirmed user needs into a full fixed specification eliminates change but does not reduce requirement uncertainty.
  4. The team adjusts the product on evidence without treating every learning cycle as an uncontrolled baseline breach. The result is recorded in the project controls.

Explanation

Correct Answer

C:

The shortcut is mistaken: Locking unconfirmed user needs into a full fixed specification eliminates change but does not reduce requirement uncertainty. The appropriate response is to use an adaptive discovery and delivery approach with frequent validation of changing rules instead of freezing all details at initiation. Record the rationale before the next commitment.

Incorrect Answers

A:

This is an appropriate independent test of the proposed decision: Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit. It is not the invalid shortcut.

B:

This is a supported decision, not the unsupported claim: Use an adaptive discovery and delivery approach with frequent validation of changing rules instead of freezing all details at initiation. Record the rationale before the next commitment. It responds to the actual project issue: A benefits portal team has disputed eligibility rules and expects monthly feedback that will change interface behavior.

D:

This is a relevant outcome to seek after the decision: The team adjusts the product on evidence without treating every learning cycle as an uncontrolled baseline breach. The result is recorded in the project controls. It is not an unsupported assumption.

Question 20

Which observed result supports acceptance of the Predictive-or-adaptive life-cycle fit corrective decision ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A benefits portal team has disputed eligibility rules and expects monthly feedback that will change interface behavior. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Leaders receive accurate status and can choose a response based on real progress. The result is recorded in the project controls.
  2. The team adjusts the product on evidence without treating every learning cycle as an uncontrolled baseline breach. The result is recorded in the project controls.
  3. Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls.
  4. Locking unconfirmed user needs into a full fixed specification eliminates change but does not reduce requirement uncertainty.

Explanation

Correct Answer

B:

The stated result demonstrates the case acceptance condition: The team adjusts the product on evidence without treating every learning cycle as an uncontrolled baseline breach. The result is recorded in the project controls. It depends on the decision Use an adaptive discovery and delivery approach with frequent validation of changing rules instead of freezing all details at initiation. Record the rationale before the next commitment.

Incorrect Answers

A:

This option concerns a different Project life cycles and processes situation: An integration milestone is late, but a lead asks for a green status to prevent executive scrutiny. For the reported case, use this verification: Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit.

C:

The proposed outcome (Shared benefits and dependencies are tracked at program level while investment priorities remain visible at portfolio level. The result is recorded in the project controls.) comes from a different Project life cycles and processes situation: A hospital groups linked clinical record, identity, and data-migration projects under one coordinated benefit but reports them as unrelated portfolio investments. It does not resolve or independently test the stated issue: A benefits portal team has disputed eligibility rules and expects monthly feedback that will change interface behavior. Here, the relevant check is Compare decision logs and learning from each demonstration with changes made to the prioritized backlog. Retain the initiating evidence for audit. [R158 R158-Q0020; case R158-C005; CAPM domain 1, task 1.1; source ECO.]

D:

This is a tempting but unsupported shortcut in this case: Locking unconfirmed user needs into a full fixed specification eliminates change but does not reduce requirement uncertainty. It does not show that The team adjusts the product on evidence without treating every learning cycle as an uncontrolled baseline breach. The result is recorded in the project controls. [R158 R158-Q0020; case R158-C005; CAPM domain 1, task 1.1; source ECO.]

Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.