100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 680
Which observed result supports acceptance of the Workshop-for-conflicting-requirements corrective decision ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Operations and compliance teams disagree on a case-handling deadline and their requirements cannot both be met. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- The team identifies tacit workflow requirements that a form alone might miss. The result is recorded in the project controls.
- The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls.
- A shared version of the deadline requirement is ready for implementation and testing. The decision can be traced to the review evidence.
- Recording both contradictory deadlines as final requirements postpones a necessary business decision.
Explanation
Correct Answer
C:The stated result demonstrates the case acceptance condition: A shared version of the deadline requirement is ready for implementation and testing. The decision can be traced to the review evidence. It depends on the decision Facilitate a joint requirements workshop to expose constraints, trade-offs and an authorized resolution. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:The proposed outcome (The team identifies tacit workflow requirements that a form alone might miss. The result is recorded in the project controls.) comes from a different Requirements elicitation and traceability situation: A hospital needs to understand why clinicians bypass a complicated transfer process and existing documentation is incomplete. It does not resolve or independently test the stated issue: Operations and compliance teams disagree on a case-handling deadline and their requirements cannot both be met. Here, the relevant check is Review the workshop decisions, outstanding questions and approved acceptance criteria. Reconcile the result with the current approved decision baseline. [R158 R158-Q0680; case R158-C170; CAPM domain 4, task 4.3; source ECO.]
B:The proposed outcome (The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls.) 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: Operations and compliance teams disagree on a case-handling deadline and their requirements cannot both be met. Here, the relevant check is Review the workshop decisions, outstanding questions and approved acceptance criteria. Reconcile the result with the current approved decision baseline. [R158 R158-Q0680; case R158-C170; CAPM domain 4, task 4.3; source ECO.]
D:This is a tempting but unsupported shortcut in this case: Recording both contradictory deadlines as final requirements postpones a necessary business decision. It does not show that A shared version of the deadline requirement is ready for implementation and testing. The decision can be traced to the review evidence. [R158 R158-Q0680; case R158-C170; CAPM domain 4, task 4.3; source ECO.]
Question 681
Which project-management decision best addresses the User-story-and-acceptance-criteria situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Conduct structured interviews with representative clinicians and follow with observation or artifact checks to uncover exceptions. Record the rationale before the next commitment.
- A vague adjective such as easier is not a sufficient acceptance rule by itself.
- Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Record the rationale before the next commitment.
- 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
C:The case evidence identifies A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. The specified decision directly addresses it: Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Record the rationale before the next commitment. This can be checked using Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit. [R158 R158-Q0681; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
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: Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit.
B:This is a tempting but unsupported shortcut in this case: A vague adjective such as easier is not a sufficient acceptance rule by itself. It does not show that The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls. [R158 R158-Q0681; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
D: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 sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit.
Question 682
After a corrective decision on User-story-and-acceptance-criteria, 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 self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Walk through error examples with the business owner and validate each required system response. Reconcile the result with the current approved decision baseline.
- A vague adjective such as easier is not a sufficient acceptance rule by itself.
- Inspect response coverage and question interpretation across rider segments. Retain the initiating evidence for audit.
- Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit. The desired observed result is The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls. [R158 R158-Q0682; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
Incorrect Answers
A: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: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Here, the relevant check is Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit. [R158 R158-Q0682; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
B:This is a tempting but unsupported shortcut in this case: A vague adjective such as easier is not a sufficient acceptance rule by itself. It does not show that The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls. [R158 R158-Q0682; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
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: Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit.
Question 683
Which statement most accurately flags a misleading shortcut to avoid in this User-story-and-acceptance-criteria case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit.
- Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Record the rationale before the next commitment.
- A vague adjective such as easier is not a sufficient acceptance rule by itself.
- The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls.
Explanation
Correct Answer
C:The shortcut is mistaken: A vague adjective such as easier is not a sufficient acceptance rule by itself. The appropriate response is to write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Record the rationale before the next commitment.
Incorrect Answers
A:This is an appropriate independent test of the proposed decision: Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit. It is not the invalid shortcut.
B:This is a supported decision, not the unsupported claim: Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Record the rationale before the next commitment. It responds to the actual project issue: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it.
D:This is a relevant outcome to seek after the decision: The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls. It is not an unsupported assumption.
Question 684
Select TWO case-specific elements of a justified User-story-and-acceptance-criteria resolution : the decision and its direct evidence. During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- 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.
- Walk through error examples with the business owner and validate each required system response. Reconcile the result with the current approved decision baseline.
- Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Record the rationale before the next commitment.
- A vague adjective such as easier is not a sufficient acceptance rule by itself.
- Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit.
Explanation
Correct Answer
C:The case evidence identifies A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. The specified decision directly addresses it: Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Record the rationale before the next commitment. This can be checked using Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit. [R158 R158-Q0684; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
E:This checks the actual mechanism rather than merely declaring success: Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit. The desired observed result is The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls. [R158 R158-Q0684; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
Incorrect Answers
A: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: Inspect sample address-change scenarios and whether each criterion can be independently tested. 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: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Here, the relevant check is Inspect sample address-change scenarios and whether each criterion can be independently tested. Retain the initiating evidence for audit. [R158 R158-Q0684; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
D:This is a tempting but unsupported shortcut in this case: A vague adjective such as easier is not a sufficient acceptance rule by itself. It does not show that The need is understandable and the delivered behavior has testable boundaries. The result is recorded in the project controls. [R158 R158-Q0684; case R158-C171; CAPM domain 4, task 4.3; source ECO.]
Question 685
Which project-management decision best addresses the User-story-and-acceptance-criteria situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Facilitate a joint requirements workshop to expose constraints, trade-offs and an authorized resolution. Record the rationale before the next commitment.
- A vague adjective such as easier is not a sufficient acceptance rule by itself.
- Conduct structured interviews with representative clinicians and follow with observation or artifact checks to uncover exceptions. Record the rationale before the next commitment.
- Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
D:The case evidence identifies A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. The specified decision directly addresses it: Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline. [R158 R158-Q0685; case R158-C172; 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 sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline.
B:This is a tempting but unsupported shortcut in this case: A vague adjective such as easier is not a sufficient acceptance rule by itself. It does not show that The need is understandable and the delivered behavior has testable boundaries. The decision can be traced to the review evidence. [R158 R158-Q0685; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
C:The proposed action (Conduct structured interviews with representative clinicians and follow with observation or artifact checks to uncover exceptions. Record the rationale before the next commitment.) comes from a different Requirements elicitation and traceability situation: A hospital needs to understand why clinicians bypass a complicated transfer process and existing documentation is incomplete. It does not resolve or independently test the stated issue: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Here, the relevant check is Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline. [R158 R158-Q0685; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
Question 686
After a corrective decision on User-story-and-acceptance-criteria, 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 self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- A vague adjective such as easier is not a sufficient acceptance rule by itself.
- Walk through error examples with the business owner and validate each required system response. Reconcile the result with the current approved decision baseline.
- Compare recorded interview themes with actual workflow examples and divergent role perspectives. Reconcile the result with the current approved decision baseline.
- Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline. The desired observed result is The need is understandable and the delivered behavior has testable boundaries. The decision can be traced to the review evidence. [R158 R158-Q0686; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: A vague adjective such as easier is not a sufficient acceptance rule by itself. It does not show that The need is understandable and the delivered behavior has testable boundaries. The decision can be traced to the review evidence. [R158 R158-Q0686; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
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: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Here, the relevant check is Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline. [R158 R158-Q0686; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
C:The proposed verify (Compare recorded interview themes with actual workflow examples and divergent role perspectives. Reconcile the result with the current approved decision baseline.) comes from a different Requirements elicitation and traceability situation: A hospital needs to understand why clinicians bypass a complicated transfer process and existing documentation is incomplete. It does not resolve or independently test the stated issue: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Here, the relevant check is Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline. [R158 R158-Q0686; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
Question 687
Which statement most accurately flags a misleading shortcut to avoid in this User-story-and-acceptance-criteria case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Document impacted stakeholders and the decision owner at the review.
- Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline.
- A vague adjective such as easier is not a sufficient acceptance rule by itself.
- The need is understandable and the delivered behavior has testable boundaries. The decision can be traced to the review evidence.
Explanation
Correct Answer
C:The shortcut is mistaken: A vague adjective such as easier is not a sufficient acceptance rule by itself. The appropriate response is to write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:This is a supported decision, not the unsupported claim: Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it.
B:This is an appropriate independent test of the proposed decision: Inspect sample address-change scenarios and whether each criterion can be independently tested. 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 need is understandable and the delivered behavior has testable boundaries. The decision can be traced to the review evidence. It is not an unsupported assumption.
Question 688
Select TWO case-specific elements of a justified User-story-and-acceptance-criteria resolution : the decision and its direct evidence. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Design a suitable survey with clear questions and representative outreach, documenting sampling limitations. Document impacted stakeholders and the decision owner at the review.
- A vague adjective such as easier is not a sufficient acceptance rule by itself.
- Walk through error examples with the business owner and validate each required system response. Reconcile the result with the current approved decision baseline.
- Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Document impacted stakeholders and the decision owner at the review.
- Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
D:The case evidence identifies A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. The specified decision directly addresses it: Write a user-centered story specifying actor and value, then add observable acceptance criteria and exception rules. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline. [R158 R158-Q0688; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
E:This checks the actual mechanism rather than merely declaring success: Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline. The desired observed result is The need is understandable and the delivered behavior has testable boundaries. The decision can be traced to the review evidence. [R158 R158-Q0688; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
Incorrect Answers
A: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 sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline.
B:This is a tempting but unsupported shortcut in this case: A vague adjective such as easier is not a sufficient acceptance rule by itself. It does not show that The need is understandable and the delivered behavior has testable boundaries. The decision can be traced to the review evidence. [R158 R158-Q0688; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
C: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: A self-service address-change feature is described only as make editing easier and developers cannot estimate or test it. Here, the relevant check is Inspect sample address-change scenarios and whether each criterion can be independently tested. Reconcile the result with the current approved decision baseline. [R158 R158-Q0688; case R158-C172; CAPM domain 4, task 4.3; source ECO.]
Question 689
Which project-management decision best addresses the Use-case-exception-flows situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- 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.
- Model main and alternative use-case flows with preconditions, exceptions and business outcomes. Record the rationale before the next commitment.
- Design a suitable survey with clear questions and representative outreach, documenting sampling limitations. Document impacted stakeholders and the decision owner at the review.
- Assuming all transactions succeed because the happy path works ignores material exception requirements.
Explanation
Correct Answer
B:The case evidence identifies An online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. The specified decision directly addresses it: Model main and alternative use-case flows with preconditions, exceptions and business outcomes. Record the rationale before the next commitment. This can be checked using Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit. [R158 R158-Q0689; case R158-C173; CAPM domain 4, task 4.3; source ECO.]
Incorrect Answers
A:The proposed action (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.) 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: An online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. Here, the relevant check is Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit. [R158 R158-Q0689; case R158-C173; CAPM domain 4, task 4.3; source ECO.]
C:The proposed action (Design a suitable survey with clear questions and representative outreach, documenting sampling limitations. Document impacted stakeholders and the decision owner at the review.) 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 online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. Here, the relevant check is Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit. [R158 R158-Q0689; case R158-C173; CAPM domain 4, task 4.3; source ECO.]
D:This is a tempting but unsupported shortcut in this case: Assuming all transactions succeed because the happy path works ignores material exception requirements. It does not show that Requirements cover common exceptions instead of shipping only the ideal transaction path. The result is recorded in the project controls. [R158 R158-Q0689; case R158-C173; CAPM domain 4, task 4.3; source ECO.]
Question 690
After a corrective decision on Use-case-exception-flows, 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 online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline.
- Inspect response coverage and question interpretation across rider segments. Retain the initiating evidence for audit.
- Assuming all transactions succeed because the happy path works ignores material exception requirements.
- Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit. The desired observed result is Requirements cover common exceptions instead of shipping only the ideal transaction path. The result is recorded in the project controls. [R158 R158-Q0690; case R158-C173; CAPM domain 4, task 4.3; source ECO.]
Incorrect Answers
A:The proposed verify (Check that candidate items are understandable and sufficiently small for credible near-term planning. Reconcile the result with the current approved decision baseline.) 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: An online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. Here, the relevant check is Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit. [R158 R158-Q0690; case R158-C173; CAPM domain 4, task 4.3; source ECO.]
B:The proposed verify (Inspect response coverage and question interpretation across rider segments. Retain the initiating evidence for audit.) 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 online refund flow has a documented happy path but no analysis of rejected payments, expired windows or failed identity checks. Here, the relevant check is Walk through error examples with the business owner and validate each required system response. Retain the initiating evidence for audit. [R158 R158-Q0690; case R158-C173; CAPM domain 4, task 4.3; source ECO.]
C:This is a tempting but unsupported shortcut in this case: Assuming all transactions succeed because the happy path works ignores material exception requirements. It does not show that Requirements cover common exceptions instead of shipping only the ideal transaction path. The result is recorded in the project controls. [R158 R158-Q0690; case R158-C173; CAPM domain 4, task 4.3; source ECO.]
Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests