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 28

Question 270

For a local government project office, what is the strongest acceptance evidence after addressing: A product owner reorders the backlog but does not record why critical work moved below a cosmetic change.

  1. The updated backlog shows current order with clear decision ownership.
  2. Cross-team decisions reference delivered results instead of summing incompatible story points.
  3. Stakeholders can view current priorities, completed items and blockers.
  4. The backlog contains small verifiable stories that can be completed during iteration.

Explanation

Correct Answer

A:

The updated backlog shows current order with clear decision ownership. This validates the selected response: Keep visible rationale for priority changes and relevant stakeholder decisions. The relevant management principle is: A product backlog is a living planning and prioritization control.

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: Keep visible rationale for priority changes and relevant stakeholder decisions.

C:

Stakeholders can view current priorities, completed items and blockers. This is evidence for ANOTHER case: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. The specific corrective response here is: Keep visible rationale for priority changes and relevant stakeholder decisions.

D:

The backlog contains small verifiable stories that can be completed during iteration. This is evidence for ANOTHER case: A team says each user story must be one entire quarter in duration and cannot be split. The specific corrective response here is: Keep visible rationale for priority changes and relevant stakeholder decisions.

Question 271

A postincident review considers: A product owner reorders the backlog but does not record why critical work moved below a cosmetic change. Which principle most directly accounts for the behavior?

  1. Adaptive controls need cross-team transparency when increments interact.
  2. A product backlog is a living planning and prioritization control.
  3. Adaptive controls use lightweight transparent artifacts rather than no artifacts.
  4. Scrum relies on defined accountabilities and self-management.

Explanation

Correct Answer

B:

A product backlog is a living planning and prioritization control. This explains the case: A product owner reorders the backlog but does not record why critical work moved below a cosmetic change. The targeted action is: Keep visible rationale for priority changes and relevant stakeholder decisions.

Incorrect Answers

A:

Adaptive controls need cross-team transparency when increments interact. This rationale better explains a DIFFERENT problem: A multi-site project has separate sprint boards that cannot show one shared release objective or integration issue. The key mechanism for the current situation is: A product backlog is a living planning and prioritization control.

C:

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: A product backlog is a living planning and prioritization control.

D:

Scrum relies on defined accountabilities and self-management. This rationale better explains a DIFFERENT problem: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management. The key mechanism for the current situation is: A product backlog is a living planning and prioritization control.

Question 272

What ongoing preventive practice would most reduce recurrence of: A product owner reorders the backlog but does not record why critical work moved below a cosmetic change.

  1. Include demonstrations in regular inspect-and-adapt events.
  2. Document appropriate metric interpretation for management.
  3. Review backlog rationale at stakeholder checkpoints.
  4. Document lifecycle choice at workstream level.

Explanation

Correct Answer

C:

Review backlog rationale at stakeholder checkpoints. This helps prevent recurrence of: A product owner reorders the backlog but does not record why critical work moved below a cosmetic change. The required evidence of effective control is: The updated backlog shows current order with clear decision ownership.

Incorrect Answers

A:

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: Review backlog rationale at stakeholder checkpoints.

B:

Document appropriate metric interpretation for management. That is a useful control for ANOTHER case: An agile portfolio dashboard equates all story points across unrelated teams as identical units of value. The current situation is better prevented by: Review backlog rationale at stakeholder checkpoints.

D:

Document lifecycle choice at workstream level. That is a useful control for ANOTHER case: A safety-critical pharmaceutical build has fixed validation gates but uncertain training content based on early users. The current situation is better prevented by: Review backlog rationale at stakeholder checkpoints.

Question 273

At a cross-functional software product team, the review identifies: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. Which response best addresses the specific project management problem?

  1. Define workflow policies and consistent criteria for moving work between stages.
  2. Use collaborative pair work with continuous review and shared understanding at the same task.
  3. Define a coherent inspect-and-adapt cadence suited to chosen framework.
  4. Establish explicit work stages and WIP limits to encourage completion flow.

Explanation

Correct Answer

A:

Define workflow policies and consistent criteria for moving work between stages. This addresses the fictional case: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. The project-management rationale is: Kanban transparency depends on explicit workflow definitions. Verify by: Each item has clear, observable status and acceptance conditions.

Incorrect Answers

B:

Use collaborative pair work with continuous review and shared understanding at the same task. This would address a DIFFERENT fictional project situation: A developer believes pair programming in XP means one person codes while the other does unrelated email. It is less directly applicable to: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means.

C:

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 Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means.

D:

Establish explicit work stages and WIP limits to encourage completion flow. This would address a DIFFERENT fictional project situation: A Kanban team does not display work-in-progress limits and has 25 concurrent tasks, none finished. It is less directly applicable to: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means.

Question 274

The project issue was: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. Which outcome demonstrates that its remedy worked?

  1. Daily work selections are made by the team and reviewed against the goal.
  2. Each item has clear, observable status and acceptance conditions.
  3. A common integration build passes before release planning.
  4. The sprint review demonstrates a coherent usable outcome against the planned goal.

Explanation

Correct Answer

B:

Each item has clear, observable status and acceptance conditions. This validates the selected response: Define workflow policies and consistent criteria for moving work between stages. The relevant management principle is: Kanban transparency depends on explicit workflow definitions.

Incorrect Answers

A:

Daily work selections are made by the team and reviewed against the goal. This is evidence for ANOTHER case: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management. The specific corrective response here is: Define workflow policies and consistent criteria for moving work between stages.

C:

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: Define workflow policies and consistent criteria for moving work between stages.

D:

The sprint review demonstrates a coherent usable outcome against the planned goal. This is evidence for ANOTHER case: A two-week sprint begins without a selected goal and developers start ten unrelated backlog items. The specific corrective response here is: Define workflow policies and consistent criteria for moving work between stages.

Question 275

For a cross-functional software product team, the documented failure was: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. Which explanation is most accurate?

  1. Adaptive planning requires structured feedback, not unmanaged change.
  2. Scrum planning depends on transparent product goals and backlog.
  3. Kanban transparency depends on explicit workflow definitions.
  4. Lifecycle tailoring can combine complementary methods without ignoring obligations.

Explanation

Correct Answer

C:

Kanban transparency depends on explicit workflow definitions. This explains the case: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. The targeted action is: Define workflow policies and consistent criteria for moving work between stages.

Incorrect Answers

A:

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: Kanban transparency depends on explicit workflow definitions.

B:

Scrum planning depends on transparent product goals and backlog. This rationale better explains a DIFFERENT problem: A Scrum team carries no ordered product backlog and creates its sprint goal from random requests. The key mechanism for the current situation is: Kanban transparency depends on explicit workflow definitions.

D:

Lifecycle tailoring can combine complementary methods without ignoring obligations. This rationale better explains a DIFFERENT problem: A digital product team declares it must use a single pure Scrum process even though a regulated commissioning phase has formal gate approvals. The key mechanism for the current situation is: Kanban transparency depends on explicit workflow definitions.

Question 276

Which recurring governance check best addresses the risk of repeating: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means.

  1. Add cross-team integration criteria to done rules.
  2. Track retrospective actions to completion.
  3. Define urgent defect handling in team working agreements.
  4. Revisit state policies when bottlenecks recur.

Explanation

Correct Answer

D:

Revisit state policies when bottlenecks recur. This helps prevent recurrence of: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. The required evidence of effective control is: Each item has clear, observable status and acceptance conditions.

Incorrect Answers

A:

Add cross-team integration criteria to done rules. That is a useful control for ANOTHER case: Two Scrum teams integrate code only at the final release despite frequent sprint demonstrations. The current situation is better prevented by: Revisit state policies when bottlenecks recur.

B:

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: Revisit state policies when bottlenecks recur.

C:

Define urgent defect handling in team working agreements. That is a useful control for ANOTHER case: A product manager treats sprint backlog as a static contract that cannot change even when a critical safety defect emerges. The current situation is better prevented by: Revisit state policies when bottlenecks recur.

Question 277

During a project review, stakeholders report: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal. What should the team do first?

  1. Consider severity, business risk and impact in the backlog ordering decision.
  2. Reprioritize the backlog around validated product outcomes and stakeholder needs.
  3. Reorder relevant backlog work according to the new risk and product ownership decision.
  4. Define a coherent inspect-and-adapt cadence suited to chosen framework.

Explanation

Correct Answer

B:

Reprioritize the backlog around validated product outcomes and stakeholder needs. This addresses the fictional case: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal. The project-management rationale is: Adaptive tasks should contribute to useful product increments, not arbitrary activity. Verify by: Completed stories can be traced to the agreed value objective.

Incorrect Answers

A:

Consider severity, business risk and impact in the backlog ordering decision. This would address a DIFFERENT fictional project situation: A product owner ranks bug fixes only by how many users complained, ignoring a low-volume critical security vulnerability. It is less directly applicable to: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal.

C:

Reorder relevant backlog work according to the new risk and product ownership decision. This would address a DIFFERENT fictional project situation: A sprint review identifies a serious data privacy issue but the team leaves the next iteration plan unchanged without evaluating risk. It is less directly applicable to: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal.

D:

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: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal.

Question 278

Following the proposed correction, what observation confirms success: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal.

  1. Representative users with assistive technology pass the acceptance test.
  2. The story passes authorized functional tests and is accepted.
  3. Completed stories can be traced to the agreed value objective.
  4. The sprint review demonstrates a coherent usable outcome against the planned goal.

Explanation

Correct Answer

C:

Completed stories can be traced to the agreed value objective. This validates the selected response: Reprioritize the backlog around validated product outcomes and stakeholder needs. The relevant management principle is: Adaptive tasks should contribute to useful product increments, not arbitrary activity.

Incorrect Answers

A:

Representative users with assistive technology pass the acceptance test. This is evidence for ANOTHER case: A product team accepts a report feature that fails accessibility needs because acceptance tests considered only functionality. The specific corrective response here is: Reprioritize the backlog around validated product outcomes and stakeholder needs.

B:

The story passes authorized functional tests and is accepted. This is evidence for ANOTHER case: An agile team marks a story done because coding finished even though its required customer acceptance test failed. The specific corrective response here is: Reprioritize the backlog around validated product outcomes and stakeholder needs.

D:

The sprint review demonstrates a coherent usable outcome against the planned goal. This is evidence for ANOTHER case: A two-week sprint begins without a selected goal and developers start ten unrelated backlog items. The specific corrective response here is: Reprioritize the backlog around validated product outcomes and stakeholder needs.

Question 279

Which underlying planning or business-analysis mechanism explains: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal.

  1. Adaptive prioritization is driven by value and risk rather than convenience alone.
  2. Consistent success criteria enable credible empirical planning.
  3. Extreme Programming emphasizes technical engineering practices supporting rapid change.
  4. Adaptive tasks should contribute to useful product increments, not arbitrary activity.

Explanation

Correct Answer

D:

Adaptive tasks should contribute to useful product increments, not arbitrary activity. This explains the case: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal. The targeted action is: Reprioritize the backlog around validated product outcomes and stakeholder needs.

Incorrect Answers

A:

Adaptive prioritization is driven by value and risk rather than convenience alone. This rationale better explains a DIFFERENT problem: Two backlog items compete for one iteration, and a sponsor picks the easier one while ignoring urgent user risk. The key mechanism for the current situation is: Adaptive tasks should contribute to useful product increments, not arbitrary activity.

B:

Consistent success criteria enable credible empirical planning. This rationale better explains a DIFFERENT problem: A team repeatedly splits stories after sprint completion to make velocity reports look favorable. The key mechanism for the current situation is: Adaptive tasks should contribute to useful product increments, not arbitrary activity.

C:

Extreme Programming emphasizes technical engineering practices supporting rapid change. This rationale better explains a DIFFERENT problem: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient. The key mechanism for the current situation is: Adaptive tasks should contribute to useful product increments, not arbitrary activity.

Question 280

For the previous project issue, select the best preventive control: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal.

  1. Review objective alignment during iteration planning.
  2. Audit metric incentives and changes to story boundaries.
  3. Review material risk as part of regular backlog refinement.
  4. Reconcile shared dependencies at regular integration reviews.

Explanation

Correct Answer

A:

Review objective alignment during iteration planning. This helps prevent recurrence of: Developers build every backlog request from one stakeholder without verifying whether it serves the approved product goal. The required evidence of effective control is: Completed stories can be traced to the agreed value objective.

Incorrect Answers

B:

Audit metric incentives and changes to story boundaries. That is a useful control for ANOTHER case: A team repeatedly splits stories after sprint completion to make velocity reports look favorable. The current situation is better prevented by: Review objective alignment during iteration planning.

C:

Review material risk as part of regular backlog refinement. That is a useful control for ANOTHER case: A product owner ranks bug fixes only by how many users complained, ignoring a low-volume critical security vulnerability. The current situation is better prevented by: Review objective alignment during iteration planning.

D:

Reconcile shared dependencies at regular integration reviews. That is a useful control for ANOTHER case: A multi-site project has separate sprint boards that cannot show one shared release objective or integration issue. The current situation is better prevented by: Review objective alignment during iteration planning.