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 71

Question 700

Which observed result supports acceptance of the Requirements-traceability-matrix corrective decision ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Counting test cases without mapping them to requirements does not prove complete requirement coverage.
  2. The team can demonstrate coverage and change impact across requirements and tests. The result is recorded in the project controls.
  3. Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls.
  4. A shared version of the deadline requirement is ready for implementation and testing. The result is recorded in the project controls.

Explanation

Correct Answer

B:

The stated result demonstrates the case acceptance condition: The team can demonstrate coverage and change impact across requirements and tests. The result is recorded in the project controls. It depends on the decision Build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Record the rationale before the next commitment.

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Counting test cases without mapping them to requirements does not prove complete requirement coverage. It does not show that The team can demonstrate coverage and change impact across requirements and tests. The result is recorded in the project controls. [R158 R158-Q0700; case R158-C175; CAPM domain 4, task 4.3; source ECO.]

C:

The proposed outcome (Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls.) comes from a different Requirements elicitation and traceability situation: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. It does not resolve or independently test the stated issue: A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. Here, the relevant check is Inspect forward and backward trace links and identify untested or orphaned items. Retain the initiating evidence for audit. [R158 R158-Q0700; case R158-C175; CAPM domain 4, task 4.3; source ECO.]

D:

The proposed outcome (A shared version of the deadline requirement is ready for implementation and testing. The result is recorded in the project controls.) comes from a different Requirements elicitation and traceability situation: Operations and compliance teams disagree on a case-handling deadline and their requirements cannot both be met. It does not resolve or independently test the stated issue: A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. Here, the relevant check is Inspect forward and backward trace links and identify untested or orphaned items. Retain the initiating evidence for audit. [R158 R158-Q0700; case R158-C175; CAPM domain 4, task 4.3; source ECO.]

Question 701

Which project-management decision best addresses the Requirements-traceability-matrix situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Document impacted stakeholders and the decision owner at the review.
  2. Design a suitable survey with clear questions and representative outreach, documenting sampling limitations. Record the rationale before the next commitment.
  3. Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Record the rationale before the next commitment.
  4. Counting test cases without mapping them to requirements does not prove complete requirement coverage.

Explanation

Correct Answer

A:

The case evidence identifies A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. The specified decision directly addresses it: Build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline. [R158 R158-Q0701; case R158-C176; CAPM domain 4, task 4.3; source ECO.]

Incorrect Answers

B:

This option concerns a different Requirements elicitation and traceability situation: A transit agency needs preference trends from thousands of routine riders rather than deep interviews with only a few volunteers. For the reported case, use this verification: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.

C:

This option concerns a different Requirements elicitation and traceability situation: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. For the reported case, use this verification: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.

D:

This is a tempting but unsupported shortcut in this case: Counting test cases without mapping them to requirements does not prove complete requirement coverage. It does not show that The team can demonstrate coverage and change impact across requirements and tests. The decision can be traced to the review evidence. [R158 R158-Q0701; case R158-C176; CAPM domain 4, task 4.3; source ECO.]

Question 702

After a corrective decision on Requirements-traceability-matrix, 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 financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Counting test cases without mapping them to requirements does not prove complete requirement coverage.
  2. Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.
  3. Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit.
  4. Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit.

Explanation

Correct Answer

B:

This checks the actual mechanism rather than merely declaring success: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline. The desired observed result is The team can demonstrate coverage and change impact across requirements and tests. The decision can be traced to the review evidence. [R158 R158-Q0702; case R158-C176; CAPM domain 4, task 4.3; source ECO.]

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Counting test cases without mapping them to requirements does not prove complete requirement coverage. It does not show that The team can demonstrate coverage and change impact across requirements and tests. The decision can be traced to the review evidence. [R158 R158-Q0702; case R158-C176; CAPM domain 4, task 4.3; source ECO.]

C:

This option concerns a different Requirements elicitation and traceability situation: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. For the reported case, use this verification: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.

D:

This option concerns a different Requirements elicitation and traceability situation: An online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. For the reported case, use this verification: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.

Question 703

Which statement most accurately flags a misleading shortcut to avoid in this Requirements-traceability-matrix case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Document impacted stakeholders and the decision owner at the review.
  2. Counting test cases without mapping them to requirements does not prove complete requirement coverage.
  3. Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.
  4. The team can demonstrate coverage and change impact across requirements and tests. The decision can be traced to the review evidence.

Explanation

Correct Answer

B:

The shortcut is mistaken: Counting test cases without mapping them to requirements does not prove complete requirement coverage. The appropriate response is to build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Document impacted stakeholders and the decision owner at the review.

Incorrect Answers

A:

This is a supported decision, not the unsupported claim: Build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented.

C:

This is an appropriate independent test of the proposed decision: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.

D:

This is a relevant outcome to seek after the decision: The team can demonstrate coverage and change impact across requirements and tests. The decision can be traced to the review evidence. It is not an unsupported assumption.

Question 704

Select TWO case-specific elements of a justified Requirements-traceability-matrix resolution : the decision and its direct evidence. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Facilitate a joint requirements workshop to expose constraints, trade-offs and an authorized resolution. Document impacted stakeholders and the decision owner at the review.
  2. Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.
  3. Compare recorded interview themes with actual workflow examples and divergent role perspectives. Retain the initiating evidence for audit.
  4. Build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Document impacted stakeholders and the decision owner at the review.
  5. Counting test cases without mapping them to requirements does not prove complete requirement coverage.

Explanation

Correct Answer

B:

This checks the actual mechanism rather than merely declaring success: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline. The desired observed result is The team can demonstrate coverage and change impact across requirements and tests. The decision can be traced to the review evidence. [R158 R158-Q0704; case R158-C176; CAPM domain 4, task 4.3; source ECO.]

D:

The case evidence identifies A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. The specified decision directly addresses it: Build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline. [R158 R158-Q0704; case R158-C176; CAPM domain 4, task 4.3; source ECO.]

Incorrect Answers

A:

This option concerns a different Requirements elicitation and traceability situation: Operations and compliance teams disagree on a case-handling deadline and their requirements cannot both be met. For the reported case, use this verification: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.

C:

This option concerns a different Requirements elicitation and traceability situation: A hospital needs to understand why clinicians bypass a complicated transfer process and existing documentation is incomplete. For the reported case, use this verification: Inspect forward and backward trace links and identify untested or orphaned items. Reconcile the result with the current approved decision baseline.

E:

This is a tempting but unsupported shortcut in this case: Counting test cases without mapping them to requirements does not prove complete requirement coverage. It does not show that The team can demonstrate coverage and change impact across requirements and tests. The decision can be traced to the review evidence. [R158 R158-Q0704; case R158-C176; CAPM domain 4, task 4.3; source ECO.]

Question 705

Which project-management decision best addresses the Product-backlog-refinement situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Record the rationale before the next commitment.
  2. Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes.
  3. Design a suitable survey with clear questions and representative outreach, documenting sampling limitations. Record the rationale before the next commitment.
  4. Facilitate a joint requirements workshop to expose constraints, trade-offs and an authorized resolution. Record the rationale before the next commitment.

Explanation

Correct Answer

A:

The case evidence identifies An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. The specified decision directly addresses it: Refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Record the rationale before the next commitment. This can be checked using Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. [R158 R158-Q0705; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

Incorrect Answers

B:

This is a tempting but unsupported shortcut in this case: Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes. It does not show that Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls. [R158 R158-Q0705; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

C:

The proposed action (Design a suitable survey with clear questions and representative outreach, documenting sampling limitations. Record the rationale before the next commitment.) comes from a different Requirements elicitation and traceability situation: A transit agency needs preference trends from thousands of routine riders rather than deep interviews with only a few volunteers. It does not resolve or independently test the stated issue: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Here, the relevant check is Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. [R158 R158-Q0705; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

D:

This option concerns a different Requirements elicitation and traceability situation: Operations and compliance teams disagree on a case-handling deadline and their requirements cannot both be met. For the reported case, use this verification: Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit.

Question 706

After a corrective decision on Product-backlog-refinement, 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 adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit.
  2. Inspect response coverage and question interpretation across rider segments. Reconcile the result with the current approved decision baseline.
  3. Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit.
  4. Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes.

Explanation

Correct Answer

C:

This checks the actual mechanism rather than merely declaring success: Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. The desired observed result is Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls. [R158 R158-Q0706; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

Incorrect Answers

A:

The proposed verify (Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit.) comes from a different Requirements elicitation and traceability situation: An online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. It does not resolve or independently test the stated issue: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Here, the relevant check is Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. [R158 R158-Q0706; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

B:

The proposed verify (Inspect response coverage and question interpretation across rider segments. Reconcile the result with the current approved decision baseline.) comes from a different Requirements elicitation and traceability situation: A transit agency needs preference trends from thousands of routine riders rather than deep interviews with only a few volunteers. It does not resolve or independently test the stated issue: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Here, the relevant check is Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. [R158 R158-Q0706; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

D:

This is a tempting but unsupported shortcut in this case: Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes. It does not show that Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls. [R158 R158-Q0706; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

Question 707

Which statement most accurately flags a misleading shortcut to avoid in this Product-backlog-refinement case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes.
  2. Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls.
  3. Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit.
  4. Refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Record the rationale before the next commitment.

Explanation

Correct Answer

A:

The shortcut is mistaken: Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes. The appropriate response is to refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Record the rationale before the next commitment.

Incorrect Answers

B:

This is a relevant outcome to seek after the decision: Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls. It is not an unsupported assumption.

C:

This is an appropriate independent test of the proposed decision: Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. It is not the invalid shortcut.

D:

This is a supported decision, not the unsupported claim: Refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Record the rationale before the next commitment. It responds to the actual project issue: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled.

Question 708

Select TWO case-specific elements of a justified Product-backlog-refinement resolution : the decision and its direct evidence. During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Conduct structured interviews with representative clinicians and follow with observation or artifact checks to uncover exceptions. Record the rationale before the next commitment.
  2. Walk through error examples with the business owner and validate each required system response. Reconcile the result with the current approved decision baseline.
  3. Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes.
  4. Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit.
  5. Refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Record the rationale before the next commitment.

Explanation

Correct Answer

D:

This checks the actual mechanism rather than merely declaring success: Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. The desired observed result is Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls. [R158 R158-Q0708; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

E:

The case evidence identifies An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. The specified decision directly addresses it: Refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Record the rationale before the next commitment. This can be checked using Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. [R158 R158-Q0708; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

Incorrect Answers

A:

This option concerns a different Requirements elicitation and traceability situation: A hospital needs to understand why clinicians bypass a complicated transfer process and existing documentation is incomplete. For the reported case, use this verification: Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit.

B:

The proposed verify (Walk through error examples with the business owner and validate each required system response. Reconcile the result with the current approved decision baseline.) comes from a different Requirements elicitation and traceability situation: An online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. It does not resolve or independently test the stated issue: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Here, the relevant check is Check that candidate items are understandable and sufficiently small for credible near-term planning. Retain the initiating evidence for audit. [R158 R158-Q0708; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

C:

This is a tempting but unsupported shortcut in this case: Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes. It does not show that Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The result is recorded in the project controls. [R158 R158-Q0708; case R158-C177; CAPM domain 4, task 4.3; source SCRUM.]

Question 709

Which project-management decision best addresses the Product-backlog-refinement situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Document impacted stakeholders and the decision owner at the review.
  2. Build requirement-to-design, test and acceptance links in a traceability matrix and update gaps visibly. Record the rationale before the next commitment.
  3. Design a suitable survey with clear questions and representative outreach, documenting sampling limitations. Record the rationale before the next commitment.
  4. Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes.

Explanation

Correct Answer

A:

The case evidence identifies An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. The specified decision directly addresses it: Refine backlog items with the Product Owner, clarify value, acceptance evidence and dependencies, and order ready work. Document impacted stakeholders and the decision owner at the review. This can be checked using Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline. [R158 R158-Q0709; case R158-C178; CAPM domain 4, task 4.3; source SCRUM.]

Incorrect Answers

B:

This option concerns a different Requirements elicitation and traceability situation: A financial reporting team has 60 approved requirements but cannot show which tests prove each has been implemented. For the reported case, use this verification: Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline.

C:

This option concerns a different Requirements elicitation and traceability situation: A transit agency needs preference trends from thousands of routine riders rather than deep interviews with only a few volunteers. For the reported case, use this verification: Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline.

D:

This is a tempting but unsupported shortcut in this case: Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes. It does not show that Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The decision can be traced to the review evidence. [R158 R158-Q0709; case R158-C178; CAPM domain 4, task 4.3; source SCRUM.]

Question 710

After a corrective decision on Product-backlog-refinement, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Walk through error examples with the business owner and validate each required system response. Reconcile the result with the current approved decision baseline.
  2. Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline.
  3. Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes.
  4. Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline.

Explanation

Correct Answer

D:

This checks the actual mechanism rather than merely declaring success: Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline. The desired observed result is Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The decision can be traced to the review evidence. [R158 R158-Q0710; case R158-C178; CAPM domain 4, task 4.3; source SCRUM.]

Incorrect Answers

A:

This option concerns a different Requirements elicitation and traceability situation: An online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. For the reported case, use this verification: Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline.

B:

The proposed verify (Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline.) comes from a different Requirements elicitation and traceability situation: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. It does not resolve or independently test the stated issue: An adaptive team has a backlog of slogans and unclear feature requests, leaving iteration planning stalled. Here, the relevant check is Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline. [R158 R158-Q0710; case R158-C178; CAPM domain 4, task 4.3; source SCRUM.]

C:

This is a tempting but unsupported shortcut in this case: Copying a raw wish list directly into a Sprint gives the team no usable agreement on outcomes. It does not show that Near-term work is selected from a clear, ordered backlog rather than guesses about vague requests. The decision can be traced to the review evidence. [R158 R158-Q0710; case R158-C178; CAPM domain 4, task 4.3; source SCRUM.]

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.