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 75

Question 740

Which observed result supports acceptance of the Benefit-driven-release-tradeoff corrective decision ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. The team learns whether the core product creates value before expanding scope. The decision can be traced to the review evidence.
  2. Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing.
  3. The selected release delivers a justified set of outcomes under explicit constraints. The result is recorded in the project controls.
  4. The roadmap guides strategic sequencing without pretending uncertain distant scope is contractual. The result is recorded in the project controls.

Explanation

Correct Answer

C:

The stated result demonstrates the case acceptance condition: The selected release delivers a justified set of outcomes under explicit constraints. The result is recorded in the project controls. It depends on the decision Compare user value, compliance needs, dependencies and effort to prioritize the release content transparently. Record the rationale before the next commitment.

Incorrect Answers

A:

The proposed outcome (The team learns whether the core product creates value before expanding scope. The decision can be traced to the review evidence.) comes from a different Product roadmaps situation: A customer-support product has 40 requested features but needs early validation of whether its core triage workflow solves the problem. It does not resolve or independently test the stated issue: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Here, the relevant check is Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Retain the initiating evidence for audit. [R158 R158-Q0740; case R158-C185; CAPM domain 4, task 4.4; source ECO.]

B:

This is a tempting but unsupported shortcut in this case: Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing. It does not show that The selected release delivers a justified set of outcomes under explicit constraints. The result is recorded in the project controls. [R158 R158-Q0740; case R158-C185; CAPM domain 4, task 4.4; source ECO.]

D:

The proposed outcome (The roadmap guides strategic sequencing without pretending uncertain distant scope is contractual. The result is recorded in the project controls.) comes from a different Product roadmaps situation: A product roadmap presents exploratory AI features three quarters away as guaranteed deliveries on fixed dates. It does not resolve or independently test the stated issue: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Here, the relevant check is Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Retain the initiating evidence for audit. [R158 R158-Q0740; case R158-C185; CAPM domain 4, task 4.4; source ECO.]

Question 741

Which project-management decision best addresses the Benefit-driven-release-tradeoff situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Compare user value, compliance needs, dependencies and effort to prioritize the release content transparently. Document impacted stakeholders and the decision owner at the review.
  2. Represent roadmap horizons and assumptions honestly and distinguish committed release decisions from tentative discovery options. Record the rationale before the next commitment.
  3. Define a minimal valuable release with testable outcome and plan later enhancements based on feedback. Document impacted stakeholders and the decision owner at the review.
  4. Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing.

Explanation

Correct Answer

A:

The case evidence identifies A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. The specified decision directly addresses it: Compare user value, compliance needs, dependencies and effort to prioritize the release content transparently. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. [R158 R158-Q0741; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

Incorrect Answers

B:

The proposed action (Represent roadmap horizons and assumptions honestly and distinguish committed release decisions from tentative discovery options. Record the rationale before the next commitment.) comes from a different Product roadmaps situation: A product roadmap presents exploratory AI features three quarters away as guaranteed deliveries on fixed dates. It does not resolve or independently test the stated issue: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Here, the relevant check is Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. [R158 R158-Q0741; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

C:

This option concerns a different Product roadmaps situation: A customer-support product has 40 requested features but needs early validation of whether its core triage workflow solves the problem. For the reported case, use this verification: Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline.

D:

This is a tempting but unsupported shortcut in this case: Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing. It does not show that The selected release delivers a justified set of outcomes under explicit constraints. The decision can be traced to the review evidence. [R158 R158-Q0741; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

Question 742

After a corrective decision on Benefit-driven-release-tradeoff, 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 school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Inspect the release dependency map and readiness of identity-verification acceptance tests. Retain the initiating evidence for audit.
  2. Check stakeholder communication for confidence levels, dependencies and decisions needed before commitment. Reconcile the result with the current approved decision baseline.
  3. Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing.
  4. Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline.

Explanation

Correct Answer

D:

This checks the actual mechanism rather than merely declaring success: Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. The desired observed result is The selected release delivers a justified set of outcomes under explicit constraints. The decision can be traced to the review evidence. [R158 R158-Q0742; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

Incorrect Answers

A:

The proposed verify (Inspect the release dependency map and readiness of identity-verification acceptance tests. Retain the initiating evidence for audit.) comes from a different Product roadmaps situation: A mobile banking app proposes releasing account transfers before the underlying identity verification capability is ready. It does not resolve or independently test the stated issue: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Here, the relevant check is Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. [R158 R158-Q0742; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

B:

The proposed verify (Check stakeholder communication for confidence levels, dependencies and decisions needed before commitment. Reconcile the result with the current approved decision baseline.) comes from a different Product roadmaps situation: A product roadmap presents exploratory AI features three quarters away as guaranteed deliveries on fixed dates. It does not resolve or independently test the stated issue: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Here, the relevant check is Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. [R158 R158-Q0742; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

C:

This is a tempting but unsupported shortcut in this case: Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing. It does not show that The selected release delivers a justified set of outcomes under explicit constraints. The decision can be traced to the review evidence. [R158 R158-Q0742; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

Question 743

Which statement most accurately flags a misleading shortcut to avoid in this Benefit-driven-release-tradeoff case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing.
  2. The selected release delivers a justified set of outcomes under explicit constraints. The decision can be traced to the review evidence.
  3. Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline.
  4. Compare user value, compliance needs, dependencies and effort to prioritize the release content transparently. Document impacted stakeholders and the decision owner at the review.

Explanation

Correct Answer

A:

The shortcut is mistaken: Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing. The appropriate response is to compare user value, compliance needs, dependencies and effort to prioritize the release content transparently. Document impacted stakeholders and the decision owner at the review.

Incorrect Answers

B:

This is a relevant outcome to seek after the decision: The selected release delivers a justified set of outcomes under explicit constraints. The decision can be traced to the review evidence. It is not an unsupported assumption.

C:

This is an appropriate independent test of the proposed decision: Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.

D:

This is a supported decision, not the unsupported claim: Compare user value, compliance needs, dependencies and effort to prioritize the release content transparently. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package.

Question 744

Select TWO case-specific elements of a justified Benefit-driven-release-tradeoff resolution : the decision and its direct evidence. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Inspect the release dependency map and readiness of identity-verification acceptance tests. Retain the initiating evidence for audit.
  2. Compare user value, compliance needs, dependencies and effort to prioritize the release content transparently. Document impacted stakeholders and the decision owner at the review.
  3. Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline.
  4. Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing.
  5. Sequence releases so required control and service dependencies precede the dependent customer capability. Document impacted stakeholders and the decision owner at the review.

Explanation

Correct Answer

B:

The case evidence identifies A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. The specified decision directly addresses it: Compare user value, compliance needs, dependencies and effort to prioritize the release content transparently. Document impacted stakeholders and the decision owner at the review. This can be checked using Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. [R158 R158-Q0744; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

C:

This checks the actual mechanism rather than merely declaring success: Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. The desired observed result is The selected release delivers a justified set of outcomes under explicit constraints. The decision can be traced to the review evidence. [R158 R158-Q0744; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

Incorrect Answers

A:

The proposed verify (Inspect the release dependency map and readiness of identity-verification acceptance tests. Retain the initiating evidence for audit.) comes from a different Product roadmaps situation: A mobile banking app proposes releasing account transfers before the underlying identity verification capability is ready. It does not resolve or independently test the stated issue: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Here, the relevant check is Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. [R158 R158-Q0744; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

D:

This is a tempting but unsupported shortcut in this case: Choosing branding solely for visual impact while ignoring agreed accessibility obligations is not benefit-driven sequencing. It does not show that The selected release delivers a justified set of outcomes under explicit constraints. The decision can be traced to the review evidence. [R158 R158-Q0744; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

E:

The proposed action (Sequence releases so required control and service dependencies precede the dependent customer capability. Document impacted stakeholders and the decision owner at the review.) comes from a different Product roadmaps situation: A mobile banking app proposes releasing account transfers before the underlying identity verification capability is ready. It does not resolve or independently test the stated issue: A school portal roadmap includes improved accessibility and cosmetic branding, but a deadline requires selecting one release package. Here, the relevant check is Inspect release rationale and accessibility acceptance criteria against deadline and capacity. Reconcile the result with the current approved decision baseline. [R158 R158-Q0744; case R158-C186; CAPM domain 4, task 4.4; source ECO.]

Question 745

Which project-management decision best addresses the Predictive-BA-baseline-discipline situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control.
  2. Continuously elicit and refine the ordered backlog while preserving clear product goals and acceptance criteria. Document impacted stakeholders and the decision owner at the review.
  3. Baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Record the rationale before the next commitment.
  4. Continuously elicit and refine the ordered backlog while preserving clear product goals and acceptance criteria. Record the rationale before the next commitment.

Explanation

Correct Answer

C:

The case evidence identifies An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. The specified decision directly addresses it: Baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Record the rationale before the next commitment. This can be checked using Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. [R158 R158-Q0745; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control. It does not show that The implementation and contract share a controlled, auditable specification. The result is recorded in the project controls. [R158 R158-Q0745; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

B:

The proposed action (Continuously elicit and refine the ordered backlog while preserving clear product goals and acceptance criteria. Document impacted stakeholders and the decision owner at the review.) comes from a different BA in predictive and adaptive approaches situation: A digital education product discovers new teacher needs after every classroom pilot, yet the analyst refuses to revise an early requirements document. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. [R158 R158-Q0745; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

D:

The proposed action (Continuously elicit and refine the ordered backlog while preserving clear product goals and acceptance criteria. Record the rationale before the next commitment.) comes from a different BA in predictive and adaptive approaches situation: A digital education product discovers new teacher needs after every classroom pilot, yet the analyst refuses to revise an early requirements document. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. [R158 R158-Q0745; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

Question 746

After a corrective decision on Predictive-BA-baseline-discipline, 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 infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit.
  2. Compare pilot feedback with backlog changes and delivered Increment behavior. Retain the initiating evidence for audit.
  3. Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control.
  4. Inspect audit traceability and feedback-driven UI acceptance tests for their respective governance paths. Retain the initiating evidence for audit.

Explanation

Correct Answer

A:

This checks the actual mechanism rather than merely declaring success: Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. The desired observed result is The implementation and contract share a controlled, auditable specification. The result is recorded in the project controls. [R158 R158-Q0746; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

Incorrect Answers

B:

The proposed verify (Compare pilot feedback with backlog changes and delivered Increment behavior. Retain the initiating evidence for audit.) comes from a different BA in predictive and adaptive approaches situation: A digital education product discovers new teacher needs after every classroom pilot, yet the analyst refuses to revise an early requirements document. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. [R158 R158-Q0746; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

C:

This is a tempting but unsupported shortcut in this case: Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control. It does not show that The implementation and contract share a controlled, auditable specification. The result is recorded in the project controls. [R158 R158-Q0746; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

D:

The proposed verify (Inspect audit traceability and feedback-driven UI acceptance tests for their respective governance paths. Retain the initiating evidence for audit.) comes from a different BA in predictive and adaptive approaches situation: A regulated claims system has fixed audit controls but flexible user-interface details that benefit from testing. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. [R158 R158-Q0746; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

Question 747

Which statement most accurately flags a misleading shortcut to avoid in this Predictive-BA-baseline-discipline case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control.
  2. Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit.
  3. Baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Record the rationale before the next commitment.
  4. The implementation and contract share a controlled, auditable specification. The result is recorded in the project controls.

Explanation

Correct Answer

A:

The shortcut is mistaken: Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control. The appropriate response is to baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Record the rationale before the next commitment.

Incorrect Answers

B:

This is an appropriate independent test of the proposed decision: Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. It is not the invalid shortcut.

C:

This is a supported decision, not the unsupported claim: Baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Record the rationale before the next commitment. It responds to the actual project issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally.

D:

This is a relevant outcome to seek after the decision: The implementation and contract share a controlled, auditable specification. The result is recorded in the project controls. It is not an unsupported assumption.

Question 748

Select TWO case-specific elements of a justified Predictive-BA-baseline-discipline 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 infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Inspect audit traceability and feedback-driven UI acceptance tests for their respective governance paths. Reconcile the result with the current approved decision baseline.
  2. Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control.
  3. Baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Record the rationale before the next commitment.
  4. Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit.
  5. Continuously elicit and refine the ordered backlog while preserving clear product goals and acceptance criteria. Record the rationale before the next commitment.

Explanation

Correct Answer

C:

The case evidence identifies An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. The specified decision directly addresses it: Baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Record the rationale before the next commitment. This can be checked using Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. [R158 R158-Q0748; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

D:

This checks the actual mechanism rather than merely declaring success: Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. The desired observed result is The implementation and contract share a controlled, auditable specification. The result is recorded in the project controls. [R158 R158-Q0748; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

Incorrect Answers

A:

The proposed verify (Inspect audit traceability and feedback-driven UI acceptance tests for their respective governance paths. Reconcile the result with the current approved decision baseline.) comes from a different BA in predictive and adaptive approaches situation: A regulated claims system has fixed audit controls but flexible user-interface details that benefit from testing. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. [R158 R158-Q0748; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

B:

This is a tempting but unsupported shortcut in this case: Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control. It does not show that The implementation and contract share a controlled, auditable specification. The result is recorded in the project controls. [R158 R158-Q0748; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

E:

The proposed action (Continuously elicit and refine the ordered backlog while preserving clear product goals and acceptance criteria. Record the rationale before the next commitment.) comes from a different BA in predictive and adaptive approaches situation: A digital education product discovers new teacher needs after every classroom pilot, yet the analyst refuses to revise an early requirements document. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Retain the initiating evidence for audit. [R158 R158-Q0748; case R158-C187; CAPM domain 4, task 4.5; source ECO.]

Question 749

Which project-management decision best addresses the Predictive-BA-baseline-discipline situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control.
  2. Maintain controlled mandatory compliance requirements while iteratively refining noncritical user experience needs. Record the rationale before the next commitment.
  3. Maintain controlled mandatory compliance requirements while iteratively refining noncritical user experience needs. Document impacted stakeholders and the decision owner at the review.
  4. Baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Document impacted stakeholders and the decision owner at the review.

Explanation

Correct Answer

D:

The case evidence identifies An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. The specified decision directly addresses it: Baseline approved requirements and route changes through impact assessment, authorization and updated traceability. Document impacted stakeholders and the decision owner at the review. This can be checked using Review approval dates and links among baselined requirements, changes and tests. Reconcile the result with the current approved decision baseline. [R158 R158-Q0749; case R158-C188; CAPM domain 4, task 4.5; source ECO.]

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control. It does not show that The implementation and contract share a controlled, auditable specification. The decision can be traced to the review evidence. [R158 R158-Q0749; case R158-C188; CAPM domain 4, task 4.5; source ECO.]

B:

The proposed action (Maintain controlled mandatory compliance requirements while iteratively refining noncritical user experience needs. Record the rationale before the next commitment.) comes from a different BA in predictive and adaptive approaches situation: A regulated claims system has fixed audit controls but flexible user-interface details that benefit from testing. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Reconcile the result with the current approved decision baseline. [R158 R158-Q0749; case R158-C188; CAPM domain 4, task 4.5; source ECO.]

C:

The proposed action (Maintain controlled mandatory compliance requirements while iteratively refining noncritical user experience needs. Document impacted stakeholders and the decision owner at the review.) comes from a different BA in predictive and adaptive approaches situation: A regulated claims system has fixed audit controls but flexible user-interface details that benefit from testing. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Reconcile the result with the current approved decision baseline. [R158 R158-Q0749; case R158-C188; CAPM domain 4, task 4.5; source ECO.]

Question 750

After a corrective decision on Predictive-BA-baseline-discipline, 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 infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Inspect audit traceability and feedback-driven UI acceptance tests for their respective governance paths. Reconcile the result with the current approved decision baseline.
  2. Inspect audit traceability and feedback-driven UI acceptance tests for their respective governance paths. Retain the initiating evidence for audit.
  3. Review approval dates and links among baselined requirements, changes and tests. Reconcile the result with the current approved decision baseline.
  4. Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control.

Explanation

Correct Answer

C:

This checks the actual mechanism rather than merely declaring success: Review approval dates and links among baselined requirements, changes and tests. Reconcile the result with the current approved decision baseline. The desired observed result is The implementation and contract share a controlled, auditable specification. The decision can be traced to the review evidence. [R158 R158-Q0750; case R158-C188; CAPM domain 4, task 4.5; source ECO.]

Incorrect Answers

A:

The proposed verify (Inspect audit traceability and feedback-driven UI acceptance tests for their respective governance paths. Reconcile the result with the current approved decision baseline.) comes from a different BA in predictive and adaptive approaches situation: A regulated claims system has fixed audit controls but flexible user-interface details that benefit from testing. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Reconcile the result with the current approved decision baseline. [R158 R158-Q0750; case R158-C188; CAPM domain 4, task 4.5; source ECO.]

B:

The proposed verify (Inspect audit traceability and feedback-driven UI acceptance tests for their respective governance paths. Retain the initiating evidence for audit.) comes from a different BA in predictive and adaptive approaches situation: A regulated claims system has fixed audit controls but flexible user-interface details that benefit from testing. It does not resolve or independently test the stated issue: An infrastructure contract requires a frozen requirement set and formal owner signoff, but the team accepts feature changes verbally. Here, the relevant check is Review approval dates and links among baselined requirements, changes and tests. Reconcile the result with the current approved decision baseline. [R158 R158-Q0750; case R158-C188; CAPM domain 4, task 4.5; source ECO.]

D:

This is a tempting but unsupported shortcut in this case: Treating informal conversations as immediate changes to the contractual baseline bypasses agreed control. It does not show that The implementation and contract share a controlled, auditable specification. The decision can be traced to the review evidence. [R158 R158-Q0750; case R158-C188; CAPM domain 4, task 4.5; 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.