McAfee-Secured Website

Exam Bundle

Exam Code: CAPM

Exam Name Certified Associate in Project Management (PMI-100)

Certification Provider: PMI

Corresponding Certification: CAPM

PMI CAPM Bundle $44.99

100% PMI CAPM Guaranteed Success With Testking Training Materials

Get Real CAPM Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    CAPM Questions & Answers

    688 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual CAPM exam while allowing you to hone and measure every aspect of your test-taking ability.

  • CAPM Video Course

    CAPM Video Course

    123 Video Lectures

    CAPM Video Course is developed by PMI Professionals to help you pass the CAPM exam.

    Description

    This course will improve your knowledge and skills required to pass Certified Associate in Project Management (PMI-100) exam.
  • Study Guide

    CAPM Study Guide

    719 PDF Pages

    Developed by industry experts, this 719-page guide spells out in painstaking detail all of the information you need to ace CAPM exam.

Certified Associate in Project Management (PMI-100) (CAPM) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    688 Questions

    $124.99
  • CAPM Video Course

    Video Course

    123 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    719 PDF Pages

    $29.99

PMI CAPM Practice Test 58

Question 570

How should the project team verify a successful response to: A sprint review shows features built but no acceptance criteria agreed with stakeholders.

  1. The next iteration selects high-value feasible work from an ordered backlog.
  2. Review dates and team planning rhythm become predictable.
  3. Participating teams can trace work to an agreed release objective.
  4. The completed increment passes agreed user-visible checks.

Explanation

Correct Answer

D:

The completed increment passes agreed user-visible checks. This validates the selected response: Define testable acceptance criteria for backlog items before completion decisions. The relevant management principle is: Adaptive acceptance requires shared definitions of done and desired behavior.

Incorrect Answers

A:

The next iteration selects high-value feasible work from an ordered backlog. This is evidence for ANOTHER case: A release backlog lists capabilities with no ordering although customer value and dependencies differ widely. The specific corrective response here is: Define testable acceptance criteria for backlog items before completion decisions.

B:

Review dates and team planning rhythm become predictable. This is evidence for ANOTHER case: An agile team changes sprint duration every week because a manager wants reports earlier. The specific corrective response here is: Define testable acceptance criteria for backlog items before completion decisions.

C:

Participating teams can trace work to an agreed release objective. This is evidence for ANOTHER case: A program team adopts scaled ceremonies but retains conflicting product priorities across four component teams. The specific corrective response here is: Define testable acceptance criteria for backlog items before completion decisions.

Question 571

A project team asks why this occurs: A sprint review shows features built but no acceptance criteria agreed with stakeholders. Which project management principle best explains it?

  1. Adaptive acceptance requires shared definitions of done and desired behavior.
  2. Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order.
  3. Short iteration planning still requires dependency management.
  4. Short feedback loops expose incorrect assumptions early.

Explanation

Correct Answer

A:

Adaptive acceptance requires shared definitions of done and desired behavior. This explains the case: A sprint review shows features built but no acceptance criteria agreed with stakeholders. The targeted action is: Define testable acceptance criteria for backlog items before completion decisions.

Incorrect Answers

B:

Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order. This rationale better explains a DIFFERENT problem: A release backlog lists capabilities with no ordering although customer value and dependencies differ widely. The key mechanism for the current situation is: Adaptive acceptance requires shared definitions of done and desired behavior.

C:

Short iteration planning still requires dependency management. This rationale better explains a DIFFERENT problem: A product owner sets iteration scope using only estimated hours and ignores a high-risk external integration dependency. The key mechanism for the current situation is: Adaptive acceptance requires shared definitions of done and desired behavior.

D:

Short feedback loops expose incorrect assumptions early. This rationale better explains a DIFFERENT problem: A team repeatedly misses end-user needs because all decisions come from one executive before development starts. The key mechanism for the current situation is: Adaptive acceptance requires shared definitions of done and desired behavior.

Question 572

At a distributed delivery organization, the team wants to avoid repeating: A sprint review shows features built but no acceptance criteria agreed with stakeholders. Which safeguard should it retain?

  1. Identify risky interfaces during backlog refinement.
  2. Review acceptance conditions during refinement.
  3. Audit completion and rework handling in metrics.
  4. Reassess delivery approach as product understanding develops.

Explanation

Correct Answer

B:

Review acceptance conditions during refinement. This helps prevent recurrence of: A sprint review shows features built but no acceptance criteria agreed with stakeholders. The required evidence of effective control is: The completed increment passes agreed user-visible checks.

Incorrect Answers

A:

Identify risky interfaces during backlog refinement. That is a useful control for ANOTHER case: A product owner sets iteration scope using only estimated hours and ignores a high-risk external integration dependency. The current situation is better prevented by: Review acceptance conditions during refinement.

C:

Audit completion and rework handling in metrics. That is a useful control for ANOTHER case: A project team burns down total estimated tasks but repeatedly counts reopened defects as completed work. The current situation is better prevented by: Review acceptance conditions during refinement.

D:

Reassess delivery approach as product understanding develops. That is a useful control for ANOTHER case: A new patient portal's requirements change after each usability trial but leaders demand that all details be frozen a year ahead. The current situation is better prevented by: Review acceptance conditions during refinement.

Question 573

A CAPM-level project coordinator sees: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day. What is the best next approved step?

  1. Maintain a visible backlog, iteration board and meaningful delivery measures.
  2. Keep visible rationale for priority changes and relevant stakeholder decisions.
  3. Agree a coherent sprint goal and select a feasible set of prioritized work.
  4. Use appropriate flow metrics such as cycle time, WIP and throughput for continuous work.

Explanation

Correct Answer

D:

Use appropriate flow metrics such as cycle time, WIP and throughput for continuous work. This addresses the fictional case: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day. The project-management rationale is: Agile control artifacts should fit the chosen workflow. Verify by: The dashboard shows aging and delivery rate of individual items.

Incorrect Answers

A:

Maintain a visible backlog, iteration board and meaningful delivery measures. This would address a DIFFERENT fictional project situation: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. It is less directly applicable to: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day.

B:

Keep visible rationale for priority changes and relevant stakeholder decisions. This would address a DIFFERENT fictional project situation: A product owner reorders the backlog but does not record why critical work moved below a cosmetic change. It is less directly applicable to: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day.

C:

Agree a coherent sprint goal and select a feasible set of prioritized work. This would address a DIFFERENT fictional project situation: A two-week sprint begins without a selected goal and developers start ten unrelated backlog items. It is less directly applicable to: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day.

Question 574

For an independent research initiative, what is the strongest acceptance evidence after addressing: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day.

  1. The dashboard shows aging and delivery rate of individual items.
  2. Cross-team decisions reference delivered results instead of summing incompatible story points.
  3. Cycle time and work-in-progress decrease while throughput stabilizes.
  4. Mandatory compliance approvals and flexible training iterations are separately controlled.

Explanation

Correct Answer

A:

The dashboard shows aging and delivery rate of individual items. This validates the selected response: Use appropriate flow metrics such as cycle time, WIP and throughput for continuous work. The relevant management principle is: Agile control artifacts should fit the chosen workflow.

Incorrect Answers

B:

Cross-team decisions reference delivered results instead of summing incompatible story points. This is evidence for ANOTHER case: An agile portfolio dashboard equates all story points across unrelated teams as identical units of value. The specific corrective response here is: Use appropriate flow metrics such as cycle time, WIP and throughput for continuous work.

C:

Cycle time and work-in-progress decrease while throughput stabilizes. This is evidence for ANOTHER case: A Kanban team does not display work-in-progress limits and has 25 concurrent tasks, none finished. The specific corrective response here is: Use appropriate flow metrics such as cycle time, WIP and throughput for continuous work.

D:

Mandatory compliance approvals and flexible training iterations are separately controlled. This is evidence for ANOTHER case: A safety-critical pharmaceutical build has fixed validation gates but uncertain training content based on early users. The specific corrective response here is: Use appropriate flow metrics such as cycle time, WIP and throughput for continuous work.

Question 575

A postincident review considers: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day. Which principle most directly accounts for the behavior?

  1. Adaptive controls use lightweight transparent artifacts rather than no artifacts.
  2. Agile control artifacts should fit the chosen workflow.
  3. Excessive parallel work can reduce flow and predictability.
  4. Kanban transparency depends on explicit workflow definitions.

Explanation

Correct Answer

B:

Agile control artifacts should fit the chosen workflow. This explains the case: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day. The targeted action is: Use appropriate flow metrics such as cycle time, WIP and throughput for continuous work.

Incorrect Answers

A:

Adaptive controls use lightweight transparent artifacts rather than no artifacts. This rationale better explains a DIFFERENT problem: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. The key mechanism for the current situation is: Agile control artifacts should fit the chosen workflow.

C:

Excessive parallel work can reduce flow and predictability. This rationale better explains a DIFFERENT problem: A Kanban team does not display work-in-progress limits and has 25 concurrent tasks, none finished. The key mechanism for the current situation is: Agile control artifacts should fit the chosen workflow.

D:

Kanban transparency depends on explicit workflow definitions. This rationale better explains a DIFFERENT problem: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. The key mechanism for the current situation is: Agile control artifacts should fit the chosen workflow.

Question 576

What ongoing preventive practice would most reduce recurrence of: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day.

  1. Review metrics for unintended incentives.
  2. Include demonstrations in regular inspect-and-adapt events.
  3. Evaluate metrics against work-arrival patterns.
  4. Coach managers on servant leadership and boundaries.

Explanation

Correct Answer

C:

Evaluate metrics against work-arrival patterns. This helps prevent recurrence of: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day. The required evidence of effective control is: The dashboard shows aging and delivery rate of individual items.

Incorrect Answers

A:

Review metrics for unintended incentives. That is a useful control for ANOTHER case: A scrum team reports velocity increasing after splitting every story into many identical subtask points without improving delivery. The current situation is better prevented by: Evaluate metrics against work-arrival patterns.

B:

Include demonstrations in regular inspect-and-adapt events. That is a useful control for ANOTHER case: A release review uses only a slide deck of planned stories and never demonstrates working product. The current situation is better prevented by: Evaluate metrics against work-arrival patterns.

D:

Coach managers on servant leadership and boundaries. That is a useful control for ANOTHER case: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management. The current situation is better prevented by: Evaluate metrics against work-arrival patterns.

Question 577

At a regional transit-project team, the review identifies: A developer believes pair programming in XP means one person codes while the other does unrelated email. Which response best addresses the specific project management problem?

  1. Use collaborative pair work with continuous review and shared understanding at the same task.
  2. Define a coherent inspect-and-adapt cadence suited to chosen framework.
  3. Define workflow policies and consistent criteria for moving work between stages.
  4. Use a hybrid plan combining governed safety deliverables and iterative training refinement.

Explanation

Correct Answer

A:

Use collaborative pair work with continuous review and shared understanding at the same task. This addresses the fictional case: A developer believes pair programming in XP means one person codes while the other does unrelated email. The project-management rationale is: Pair programming provides real-time joint problem-solving and review. Verify by: The pair validates code and both understand the implemented change.

Incorrect Answers

B:

Define a coherent inspect-and-adapt cadence suited to chosen framework. This would address a DIFFERENT fictional project situation: A delivery group calls every requested change a new sprint without fixed review points or learning cycles. It is less directly applicable to: A developer believes pair programming in XP means one person codes while the other does unrelated email.

C:

Define workflow policies and consistent criteria for moving work between stages. This would address a DIFFERENT fictional project situation: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. It is less directly applicable to: A developer believes pair programming in XP means one person codes while the other does unrelated email.

D:

Use a hybrid plan combining governed safety deliverables and iterative training refinement. This would address a DIFFERENT fictional project situation: A safety-critical pharmaceutical build has fixed validation gates but uncertain training content based on early users. It is less directly applicable to: A developer believes pair programming in XP means one person codes while the other does unrelated email.

Question 578

The project issue was: A developer believes pair programming in XP means one person codes while the other does unrelated email. Which outcome demonstrates that its remedy worked?

  1. A common integration build passes before release planning.
  2. The pair validates code and both understand the implemented change.
  3. Each item has clear, observable status and acceptance conditions.
  4. A real customer workflow passes integrated tests before release acceptance.

Explanation

Correct Answer

B:

The pair validates code and both understand the implemented change. This validates the selected response: Use collaborative pair work with continuous review and shared understanding at the same task. The relevant management principle is: Pair programming provides real-time joint problem-solving and review.

Incorrect Answers

A:

A common integration build passes before release planning. This is evidence for ANOTHER case: Two Scrum teams integrate code only at the final release despite frequent sprint demonstrations. The specific corrective response here is: Use collaborative pair work with continuous review and shared understanding at the same task.

C:

Each item has clear, observable status and acceptance conditions. This is evidence for ANOTHER case: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. The specific corrective response here is: Use collaborative pair work with continuous review and shared understanding at the same task.

D:

A real customer workflow passes integrated tests before release acceptance. This is evidence for ANOTHER case: A multi-team release declares success because each component team finished its sprint tasks though the integrated system cannot process a full transaction. The specific corrective response here is: Use collaborative pair work with continuous review and shared understanding at the same task.

Question 579

For a regional transit-project team, the documented failure was: A developer believes pair programming in XP means one person codes while the other does unrelated email. Which explanation is most accurate?

  1. Product inspection and team-process inspection serve distinct purposes.
  2. Adaptive planning requires structured feedback, not unmanaged change.
  3. Pair programming provides real-time joint problem-solving and review.
  4. Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order.

Explanation

Correct Answer

C:

Pair programming provides real-time joint problem-solving and review. This explains the case: A developer believes pair programming in XP means one person codes while the other does unrelated email. The targeted action is: Use collaborative pair work with continuous review and shared understanding at the same task.

Incorrect Answers

A:

Product inspection and team-process inspection serve distinct purposes. This rationale better explains a DIFFERENT problem: A Scrum team hosts sprint reviews but never holds retrospectives, leaving recurring handoff problems unaddressed. The key mechanism for the current situation is: Pair programming provides real-time joint problem-solving and review.

B:

Adaptive planning requires structured feedback, not unmanaged change. This rationale better explains a DIFFERENT problem: A delivery group calls every requested change a new sprint without fixed review points or learning cycles. The key mechanism for the current situation is: Pair programming provides real-time joint problem-solving and review.

D:

Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order. This rationale better explains a DIFFERENT problem: A release backlog lists capabilities with no ordering although customer value and dependencies differ widely. The key mechanism for the current situation is: Pair programming provides real-time joint problem-solving and review.

Question 580

Which recurring governance check best addresses the risk of repeating: A developer believes pair programming in XP means one person codes while the other does unrelated email.

  1. Track retrospective actions to completion.
  2. Review coordinated outcomes after each planning interval.
  3. Review the usefulness of tracking tools each retrospective.
  4. Assess collaboration effectiveness in technical retrospectives.

Explanation

Correct Answer

D:

Assess collaboration effectiveness in technical retrospectives. This helps prevent recurrence of: A developer believes pair programming in XP means one person codes while the other does unrelated email. The required evidence of effective control is: The pair validates code and both understand the implemented change.

Incorrect Answers

A:

Track retrospective actions to completion. That is a useful control for ANOTHER case: A Scrum team hosts sprint reviews but never holds retrospectives, leaving recurring handoff problems unaddressed. The current situation is better prevented by: Assess collaboration effectiveness in technical retrospectives.

B:

Review coordinated outcomes after each planning interval. That is a useful control for ANOTHER case: A program team adopts scaled ceremonies but retains conflicting product priorities across four component teams. The current situation is better prevented by: Assess collaboration effectiveness in technical retrospectives.

C:

Review the usefulness of tracking tools each retrospective. That is a useful control for ANOTHER case: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. The current situation is better prevented by: Assess collaboration effectiveness in technical retrospectives.