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 54

Question 530

After a corrective decision on Kanban-WIP-limits, 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 service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Starting more cases whenever a worker is free can increase WIP and delay completion.
  2. Inspect who makes product-ordering decisions and how Developers select and adapt Sprint work. Reconcile the result with the current approved decision baseline.
  3. Inspect regression rates and the build/test pipeline on each integrated change. Reconcile the result with the current approved decision baseline.
  4. Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.

Explanation

Correct Answer

D:

This checks the actual mechanism rather than merely declaring success: Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. The desired observed result is Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. [R158 R158-Q0530; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Starting more cases whenever a worker is free can increase WIP and delay completion. It does not show that Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. [R158 R158-Q0530; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

B:

This option concerns 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. For the reported case, use this verification: Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.

C:

This option concerns a different Adaptive plan and methodologies situation: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. For the reported case, use this verification: Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.

Question 531

Which statement most accurately flags a misleading shortcut to avoid in this Kanban-WIP-limits case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.
  2. Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.
  3. Starting more cases whenever a worker is free can increase WIP and delay completion.
  4. Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls.

Explanation

Correct Answer

C:

The shortcut is mistaken: Starting more cases whenever a worker is free can increase WIP and delay completion. The appropriate response is to visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.

Incorrect Answers

A:

This is a supported decision, not the unsupported claim: Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment. It responds to the actual project issue: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens.

B:

This is an appropriate independent test of the proposed decision: Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. It is not the invalid shortcut.

D:

This is a relevant outcome to seek after the decision: Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. It is not an unsupported assumption.

Question 532

Select THREE consistent elements of the Kanban-WIP-limits case: appropriate decision, verification, and observable success condition. During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.
  2. Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls.
  3. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.
  4. Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls.
  5. Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.
  6. Starting more cases whenever a worker is free can increase WIP and delay completion.

Explanation

Correct Answer

A:

This checks the actual mechanism rather than merely declaring success: Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. The desired observed result is Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. [R158 R158-Q0532; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

C:

The case evidence identifies A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. The specified decision directly addresses it: Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment. This can be checked using Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. [R158 R158-Q0532; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

D:

The stated result demonstrates the case acceptance condition: Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. It depends on the decision Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.

Incorrect Answers

B:

The proposed outcome (Shared impediments are resolved without replacing each team's execution autonomy. The result is recorded in the project controls.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. [R158 R158-Q0532; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

E:

The proposed action (Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit. [R158 R158-Q0532; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

F:

This is a tempting but unsupported shortcut in this case: Starting more cases whenever a worker is free can increase WIP and delay completion. It does not show that Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls. [R158 R158-Q0532; case R158-C133; CAPM domain 3, task 3.4; source KANBAN.]

Question 533

Which project-management decision best addresses the Kanban-WIP-limits situation ? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Document impacted stakeholders and the decision owner at the review.
  2. Starting more cases whenever a worker is free can increase WIP and delay completion.
  3. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review.
  4. Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.

Explanation

Correct Answer

C:

The case evidence identifies A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. The specified decision directly addresses it: Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review. This can be checked using Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. [R158 R158-Q0533; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

Incorrect Answers

A:

The proposed action (Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Document impacted stakeholders and the decision owner at the review.) 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: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. [R158 R158-Q0533; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

B:

This is a tempting but unsupported shortcut in this case: Starting more cases whenever a worker is free can increase WIP and delay completion. It does not show that Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence. [R158 R158-Q0533; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

D:

The proposed action (Establish clear cross-team dependencies and synchronization at the appropriate scaling level while retaining team delivery ownership. Record the rationale before the next commitment.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. [R158 R158-Q0533; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

Question 534

After a corrective decision on Kanban-WIP-limits, 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 service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Starting more cases whenever a worker is free can increase WIP and delay completion.
  2. Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit.
  3. Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit.
  4. Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline.

Explanation

Correct Answer

D:

This checks the actual mechanism rather than merely declaring success: Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. The desired observed result is Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence. [R158 R158-Q0534; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Starting more cases whenever a worker is free can increase WIP and delay completion. It does not show that Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence. [R158 R158-Q0534; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

B:

The proposed verify (Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit.) 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: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. [R158 R158-Q0534; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

C:

The proposed verify (Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit.) comes from a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. It does not resolve or independently test the stated issue: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. [R158 R158-Q0534; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

Question 535

Which statement most accurately flags a misleading shortcut to avoid in this Kanban-WIP-limits case? At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Starting more cases whenever a worker is free can increase WIP and delay completion.
  2. Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline.
  3. Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence.
  4. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review.

Explanation

Correct Answer

A:

The shortcut is mistaken: Starting more cases whenever a worker is free can increase WIP and delay completion. The appropriate response is to visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review.

Incorrect Answers

B:

This is an appropriate independent test of the proposed decision: Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. It is not the invalid shortcut.

C:

This is a relevant outcome to seek after the decision: Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence. It is not an unsupported assumption.

D:

This is a supported decision, not the unsupported claim: Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review. It responds to the actual project issue: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens.

Question 536

Select THREE consistent elements of the Kanban-WIP-limits case: appropriate decision, verification, and observable success condition. At a later governance checkpoint, conflicting stakeholder pressure makes a second, evidence-based decision necessary. Scenario: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Respect Product Owner accountability for Product Backlog ordering and Developers' responsibility for Sprint planning and execution. Record the rationale before the next commitment.
  2. Starting more cases whenever a worker is free can increase WIP and delay completion.
  3. Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence.
  4. Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls.
  5. Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline.
  6. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review.

Explanation

Correct Answer

C:

The stated result demonstrates the case acceptance condition: Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence. It depends on the decision Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review.

E:

This checks the actual mechanism rather than merely declaring success: Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. The desired observed result is Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence. [R158 R158-Q0536; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

F:

The case evidence identifies A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. The specified decision directly addresses it: Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review. This can be checked using Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. [R158 R158-Q0536; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

Incorrect Answers

A:

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: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. [R158 R158-Q0536; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

B:

This is a tempting but unsupported shortcut in this case: Starting more cases whenever a worker is free can increase WIP and delay completion. It does not show that Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence. [R158 R158-Q0536; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

D:

The proposed outcome (Value priorities and technical execution responsibilities are clear and collaborative. The result is recorded in the project controls.) 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: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. Here, the relevant check is Compare WIP, throughput and cycle-time trends before and after limiting starts. Reconcile the result with the current approved decision baseline. [R158 R158-Q0536; case R158-C134; CAPM domain 3, task 3.4; source KANBAN.]

Question 537

Which project-management decision best addresses the XP-technical-practices situation ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.
  2. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.
  3. Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
  4. Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review.

Explanation

Correct Answer

A:

Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment. To verify the specified result, inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit.

Incorrect Answers

B:

The proposed action (Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Record the rationale before the next commitment.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. [R158 R158-Q0537; case R158-C135; CAPM domain 3, task 3.4; source ECO.]

C:

This is a tempting but unsupported shortcut in this case: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. It does not show that Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls. [R158 R158-Q0537; case R158-C135; CAPM domain 3, task 3.4; source ECO.]

D:

The proposed action (Visualize work and enforce practical work-in-progress limits to improve flow and expose bottlenecks. Document impacted stakeholders and the decision owner at the review.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. [R158 R158-Q0537; case R158-C135; CAPM domain 3, task 3.4; source ECO.]

Question 538

After a corrective decision on XP-technical-practices, 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 team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Review dependency visibility and integration progress at agreed coordination points. Retain the initiating evidence for audit.
  2. Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
  3. Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.
  4. Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit.

Explanation

Correct Answer

D:

Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. The expected result is fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls.

Incorrect Answers

A:

This option concerns a different Adaptive plan and methodologies situation: Several teams share integration dependencies but the project attempts to solve them by appointing one person to micromanage every team task. For the reported case, use this verification: Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit.

B:

This is a tempting but unsupported shortcut in this case: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. It does not show that Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls. [R158 R158-Q0538; case R158-C135; CAPM domain 3, task 3.4; source ECO.]

C:

The proposed verify (Compare WIP, throughput and cycle-time trends before and after limiting starts. Retain the initiating evidence for audit.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. [R158 R158-Q0538; case R158-C135; CAPM domain 3, task 3.4; source ECO.]

Question 539

Which statement most accurately flags a misleading shortcut to avoid in this XP-technical-practices case? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
  2. Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.
  3. Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls.
  4. Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit.

Explanation

Correct Answer

A:

The shortcut is mistaken: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. The appropriate response is to adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.

Incorrect Answers

B:

This is a supported decision, not the unsupported claim: Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment. It responds to the actual project issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions.

C:

This is a relevant outcome to seek after the decision: Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls. It is not an unsupported assumption.

D:

This is an appropriate independent test of the proposed decision: Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. It is not the invalid shortcut.

Question 540

Which observed result supports acceptance of the XP-technical-practices corrective decision ? During scope and delivery planning, the team must make a documented decision before significant work proceeds. Scenario: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Assume the named constraints and approvals are genuine and that no unrelated problem is present.

  1. Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery.
  2. Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls.
  3. Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls.
  4. Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence.

Explanation

Correct Answer

B:

The stated result demonstrates the case acceptance condition: Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls. It depends on the decision Adopt disciplined technical practices such as automated tests, continuous integration and collaborative code review for rapid changes. Record the rationale before the next commitment.

Incorrect Answers

A:

This is a tempting but unsupported shortcut in this case: Increasing release frequency without technical testing discipline is not sufficient for reliable XP-style delivery. It does not show that Fast feedback is supported by working automated quality controls rather than uncontrolled deployment frequency. The result is recorded in the project controls. [R158 R158-Q0540; case R158-C135; CAPM domain 3, task 3.4; source ECO.]

C:

The proposed outcome (Fewer items are stranded in progress and flow becomes more predictable. The result is recorded in the project controls.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. [R158 R158-Q0540; case R158-C135; CAPM domain 3, task 3.4; source ECO.]

D:

The proposed outcome (Fewer items are stranded in progress and flow becomes more predictable. The decision can be traced to the review evidence.) comes from a different Adaptive plan and methodologies situation: A service team starts 30 cases simultaneously, queues grow, and completion lead time worsens. It does not resolve or independently test the stated issue: A team deploys frequently but lacks reliable automated checks and regularly introduces regressions. Here, the relevant check is Inspect regression rates and the build/test pipeline on each integrated change. Retain the initiating evidence for audit. [R158 R158-Q0540; case R158-C135; CAPM domain 3, task 3.4; 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.