100% Latest & Updated PMI CAPM Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 550
After a corrective decision on Scaled-coordination-boundary, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.
- Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.
- Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
B:This checks the actual mechanism rather than merely declaring success: Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. The desired observed result is Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. [R158 R158-Q0550; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
Incorrect Answers
A:This is a tempting but unsupported shortcut in this case: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. It does not show that Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. [R158 R158-Q0550; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
C:The proposed verify (Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Retain the initiating evidence for audit.) comes from a different Adaptive plan and methodologies situation: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0550; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
D:The proposed verify (Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive plan and methodologies situation: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0550; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
Question 551
Which statement most accurately flags a misleading shortcut to avoid in this Scaled-coordination-boundary case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.
- Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
C:The shortcut is mistaken: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. The appropriate response is to establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:This is a supported decision, not the unsupported claim: Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task.
B:This is a relevant outcome to seek after the decision: Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. It is not an unsupported assumption.
D:This is an appropriate independent test of the proposed decision: Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.
Question 552
Select THREE consistent elements of the Scaled-coordination-boundary case: appropriate decision, verification, and observable success condition. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls.
- A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework.
- Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline.
- Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.
- Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.
- Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence.
Explanation
Correct Answer
C:This checks the actual mechanism rather than merely declaring success: Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. The desired observed result is Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. [R158 R158-Q0552; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
D:The case evidence identifies Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. The specified decision directly addresses it: Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review. This can be checked using Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0552; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
F:The stated result demonstrates the case acceptance condition: Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. It depends on the decision Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:The proposed outcome (Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls.) comes from a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0552; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
B:This is a tempting but unsupported shortcut in this case: A single manager assigning all individual tasks is not the essential purpose of an agile scaling framework. It does not show that Shared impediments are resolved without replacing each team's execution autonomy. The decision can be traced to the review evidence. [R158 R158-Q0552; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
E:The proposed action (Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.) comes from a different Adaptive plan and methodologies situation: A department head assigns developers detailed tasks and also independently reorders the Product Backlog without engaging the Product Owner. It does not resolve or independently test the stated issue: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. Here, the relevant check is Review dependency visibility and integration progress at agreed coordination points. Reconcile the result with the current approved decision baseline. [R158 R158-Q0552; case R158-C138; CAPM domain 3, task 3.4; source ECO.]
Question 553
Which project-management decision best addresses the Product-backlog-priority-risk-value situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Inspect the Increment with stakeholders and adapt the Product Backlog based on the discovered need. Record the rationale before the next commitment.
- Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Record the rationale before the next commitment.
- Sorting requirements solely by number of requests disregards severity and deadline constraints.
- Inspect the Increment with stakeholders and adapt the Product Backlog based on the discovered need. Document impacted stakeholders and the decision owner at the review.
Explanation
Correct Answer
B:The case evidence identifies The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. The specified decision directly addresses it: Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Record the rationale before the next commitment. This can be checked using Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. [R158 R158-Q0553; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
Incorrect Answers
A:The proposed action (Inspect the Increment with stakeholders and adapt the Product Backlog based on the discovered need. Record the rationale before the next commitment.) comes from a different Adaptive task management and prioritization situation: A Sprint Review shows that a released feature misses a frequent edge case, but the team treats the review as a ceremonial demo only. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. [R158 R158-Q0553; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
C:This is a tempting but unsupported shortcut in this case: Sorting requirements solely by number of requests disregards severity and deadline constraints. It does not show that High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls. [R158 R158-Q0553; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
D:The proposed action (Inspect the Increment with stakeholders and adapt the Product Backlog based on the discovered need. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive task management and prioritization situation: A Sprint Review shows that a released feature misses a frequent edge case, but the team treats the review as a ceremonial demo only. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. [R158 R158-Q0553; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
Question 554
After a corrective decision on Product-backlog-priority-risk-value, 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: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Inspect blocked age, dependency resolution and the number of unfinished work items. Reconcile the result with the current approved decision baseline.
- Sorting requirements solely by number of requests disregards severity and deadline constraints.
- Verify that the edge-case finding is recorded and reprioritized with acceptance criteria. Reconcile the result with the current approved decision baseline.
- Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit.
Explanation
Correct Answer
D:This checks the actual mechanism rather than merely declaring success: Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. The desired observed result is High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls. [R158 R158-Q0554; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
Incorrect Answers
A:This option concerns a different Adaptive task management and prioritization situation: A high-priority story remains blocked on an API contract while the team continually starts lower-priority tasks. For the reported case, use this verification: Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit.
B:This is a tempting but unsupported shortcut in this case: Sorting requirements solely by number of requests disregards severity and deadline constraints. It does not show that High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls. [R158 R158-Q0554; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
C:The proposed verify (Verify that the edge-case finding is recorded and reprioritized with acceptance criteria. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive task management and prioritization situation: A Sprint Review shows that a released feature misses a frequent edge case, but the team treats the review as a ceremonial demo only. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. [R158 R158-Q0554; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
Question 555
Which statement most accurately flags a misleading shortcut to avoid in this Product-backlog-priority-risk-value case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit.
- High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls.
- Sorting requirements solely by number of requests disregards severity and deadline constraints.
- Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Record the rationale before the next commitment.
Explanation
Correct Answer
C:The shortcut is mistaken: Sorting requirements solely by number of requests disregards severity and deadline constraints. The appropriate response is to assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Record the rationale before the next commitment.
Incorrect Answers
A:This is an appropriate independent test of the proposed decision: Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. It is not the invalid shortcut.
B:This is a relevant outcome to seek after the decision: High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls. It is not an unsupported assumption.
D:This is a supported decision, not the unsupported claim: Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Record the rationale before the next commitment. It responds to the actual project issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume.
Question 556
Select THREE consistent elements of the Product-backlog-priority-risk-value case: appropriate decision, verification, and observable success condition. During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Define observable acceptance criteria for the target search behavior and test the Increment against them. Record the rationale before the next commitment.
- Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Record the rationale before the next commitment.
- Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit.
- Sorting requirements solely by number of requests disregards severity and deadline constraints.
- Feedback alters future work in service of the Product Goal. The decision can be traced to the review evidence.
- High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls.
Explanation
Correct Answer
B:The case evidence identifies The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. The specified decision directly addresses it: Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Record the rationale before the next commitment. This can be checked using Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. [R158 R158-Q0556; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
C:This checks the actual mechanism rather than merely declaring success: Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. The desired observed result is High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls. [R158 R158-Q0556; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
F:The stated result demonstrates the case acceptance condition: High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls. It depends on the decision Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Record the rationale before the next commitment.
Incorrect Answers
A:This option concerns a different Adaptive task management and prioritization situation: A story states merely improve search, and the team cannot agree whether it is done. For the reported case, use this verification: Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit.
D:This is a tempting but unsupported shortcut in this case: Sorting requirements solely by number of requests disregards severity and deadline constraints. It does not show that High-consequence work is surfaced early and the remaining value trade-offs are explicit. The result is recorded in the project controls. [R158 R158-Q0556; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
E:The proposed outcome (Feedback alters future work in service of the Product Goal. The decision can be traced to the review evidence.) comes from a different Adaptive task management and prioritization situation: A Sprint Review shows that a released feature misses a frequent edge case, but the team treats the review as a ceremonial demo only. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Retain the initiating evidence for audit. [R158 R158-Q0556; case R158-C139; CAPM domain 3, task 3.5; source ECO.]
Question 557
Which project-management decision best addresses the Product-backlog-priority-risk-value situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Define observable acceptance criteria for the target search behavior and test the Increment against them. Record the rationale before the next commitment.
- Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Document impacted stakeholders and the decision owner at the review.
- Sorting requirements solely by number of requests disregards severity and deadline constraints.
- Inspect the Increment with stakeholders and adapt the Product Backlog based on the discovered need. Record the rationale before the next commitment.
Explanation
Correct Answer
B:Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Document impacted stakeholders and the decision owner at the review. To verify the specified result, check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline.
Incorrect Answers
A:The proposed action (Define observable acceptance criteria for the target search behavior and test the Increment against them. Record the rationale before the next commitment.) comes from a different Adaptive task management and prioritization situation: A story states merely improve search, and the team cannot agree whether it is done. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline. [R158 R158-Q0557; case R158-C140; CAPM domain 3, task 3.5; source ECO.]
C:This is a tempting but unsupported shortcut in this case: Sorting requirements solely by number of requests disregards severity and deadline constraints. It does not show that High-consequence work is surfaced early and the remaining value trade-offs are explicit. The decision can be traced to the review evidence. [R158 R158-Q0557; case R158-C140; CAPM domain 3, task 3.5; source ECO.]
D:The proposed action (Inspect the Increment with stakeholders and adapt the Product Backlog based on the discovered need. Record the rationale before the next commitment.) comes from a different Adaptive task management and prioritization situation: A Sprint Review shows that a released feature misses a frequent edge case, but the team treats the review as a ceremonial demo only. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline. [R158 R158-Q0557; case R158-C140; CAPM domain 3, task 3.5; source ECO.]
Question 558
After a corrective decision on Product-backlog-priority-risk-value, which independent evidence most directly verifies the result ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Demonstrate the behavior using representative inputs and thresholds specified by the user. Retain the initiating evidence for audit.
- Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline.
- Verify that the edge-case finding is recorded and reprioritized with acceptance criteria. Reconcile the result with the current approved decision baseline.
- Sorting requirements solely by number of requests disregards severity and deadline constraints.
Explanation
Correct Answer
B:Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline. The expected result is high-consequence work is surfaced early and the remaining value trade-offs are explicit. The decision can be traced to the review evidence.
Incorrect Answers
A:The proposed verify (Demonstrate the behavior using representative inputs and thresholds specified by the user. Retain the initiating evidence for audit.) comes from a different Adaptive task management and prioritization situation: A story states merely improve search, and the team cannot agree whether it is done. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline. [R158 R158-Q0558; case R158-C140; CAPM domain 3, task 3.5; source ECO.]
C:The proposed verify (Verify that the edge-case finding is recorded and reprioritized with acceptance criteria. Reconcile the result with the current approved decision baseline.) comes from a different Adaptive task management and prioritization situation: A Sprint Review shows that a released feature misses a frequent edge case, but the team treats the review as a ceremonial demo only. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline. [R158 R158-Q0558; case R158-C140; CAPM domain 3, task 3.5; source ECO.]
D:This is a tempting but unsupported shortcut in this case: Sorting requirements solely by number of requests disregards severity and deadline constraints. It does not show that High-consequence work is surfaced early and the remaining value trade-offs are explicit. The decision can be traced to the review evidence. [R158 R158-Q0558; case R158-C140; CAPM domain 3, task 3.5; source ECO.]
Question 559
Which statement most accurately flags a misleading shortcut to avoid in this Product-backlog-priority-risk-value case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Document impacted stakeholders and the decision owner at the review.
- Sorting requirements solely by number of requests disregards severity and deadline constraints.
- High-consequence work is surfaced early and the remaining value trade-offs are explicit. The decision can be traced to the review evidence.
- Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline.
Explanation
Correct Answer
B:The shortcut is mistaken: Sorting requirements solely by number of requests disregards severity and deadline constraints. The appropriate response is to assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:This is a supported decision, not the unsupported claim: Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume.
C:This is a relevant outcome to seek after the decision: High-consequence work is surfaced early and the remaining value trade-offs are explicit. The decision can be traced to the review evidence. It is not an unsupported assumption.
D:This is an appropriate independent test of the proposed decision: Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.
Question 560
Which observed result supports acceptance of the Product-backlog-priority-risk-value corrective decision ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Assume the named constraints and approvals are genuine and that no unrelated problem is present.
- The team and user can objectively accept or reject the completed behavior. The decision can be traced to the review evidence.
- High-consequence work is surfaced early and the remaining value trade-offs are explicit. The decision can be traced to the review evidence.
- The team restores flow on high-value work and avoids growing unfinished inventory. The result is recorded in the project controls.
- Sorting requirements solely by number of requests disregards severity and deadline constraints.
Explanation
Correct Answer
B:The stated result demonstrates the case acceptance condition: High-consequence work is surfaced early and the remaining value trade-offs are explicit. The decision can be traced to the review evidence. It depends on the decision Assess urgency, risk, business value and dependencies, then make the priority trade-off transparent to the accountable Product Owner. Document impacted stakeholders and the decision owner at the review.
Incorrect Answers
A:The proposed outcome (The team and user can objectively accept or reject the completed behavior. The decision can be traced to the review evidence.) comes from a different Adaptive task management and prioritization situation: A story states merely improve search, and the team cannot agree whether it is done. It does not resolve or independently test the stated issue: The team has one high-risk compliance flaw and three cosmetic enhancements, but prioritizes cosmetic work due to stakeholder volume. Here, the relevant check is Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline. [R158 R158-Q0560; case R158-C140; CAPM domain 3, task 3.5; source ECO.]
C:This option concerns a different Adaptive task management and prioritization situation: A high-priority story remains blocked on an API contract while the team continually starts lower-priority tasks. For the reported case, use this verification: Check the revised Product Backlog order and documented rationale against regulatory deadlines. Reconcile the result with the current approved decision baseline.
D:This is a tempting but unsupported shortcut in this case: Sorting requirements solely by number of requests disregards severity and deadline constraints. It does not show that High-consequence work is surfaced early and the remaining value trade-offs are explicit. The decision can be traced to the review evidence. [R158 R158-Q0560; case R158-C140; CAPM domain 3, task 3.5; source ECO.]
Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests