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 20

Question 190

For a university infrastructure office, what is the strongest acceptance evidence after addressing: A release backlog lists capabilities with no ordering although customer value and dependencies differ widely.

  1. The next iteration selects high-value feasible work from an ordered backlog.
  2. The completed increment passes agreed user-visible checks.
  3. Emergency work is handled without obscuring the impact on originally planned outcomes.
  4. The story passes authorized functional tests and is accepted.

Explanation

Correct Answer

A:

The next iteration selects high-value feasible work from an ordered backlog. This validates the selected response: Collaborate with product ownership to prioritize by value, risk and dependency. The relevant management principle is: Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order.

Incorrect Answers

B:

The completed increment passes agreed user-visible checks. This is evidence for ANOTHER case: A sprint review shows features built but no acceptance criteria agreed with stakeholders. The specific corrective response here is: Collaborate with product ownership to prioritize by value, risk and dependency.

C:

Emergency work is handled without obscuring the impact on originally planned outcomes. This is evidence for ANOTHER case: A product manager treats sprint backlog as a static contract that cannot change even when a critical safety defect emerges. The specific corrective response here is: Collaborate with product ownership to prioritize by value, risk and dependency.

D:

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: Collaborate with product ownership to prioritize by value, risk and dependency.

Question 191

A postincident review considers: A release backlog lists capabilities with no ordering although customer value and dependencies differ widely. Which principle most directly accounts for the behavior?

  1. Iteration planning must account for known blockers and uncertainty.
  2. Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order.
  3. Adaptive decomposition emphasizes incremental value and feedback over component-only progress.
  4. Scaling requires shared direction and integration, not meetings alone.

Explanation

Correct Answer

B:

Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order. This explains the case: A release backlog lists capabilities with no ordering although customer value and dependencies differ widely. The targeted action is: Collaborate with product ownership to prioritize by value, risk and dependency.

Incorrect Answers

A:

Iteration planning must account for known blockers and uncertainty. This rationale better explains a DIFFERENT problem: A backlog item depends on a vendor decision next month but is pulled into this week's sprint as if fully ready. The key mechanism for the current situation is: Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order.

C:

Adaptive decomposition emphasizes incremental value and feedback over component-only progress. This rationale better explains a DIFFERENT problem: A traditional WBS describes all application components, but a team cannot identify any user-facing incremental delivery. The key mechanism for the current situation is: Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order.

D:

Scaling requires shared direction and integration, not meetings alone. This rationale better explains a DIFFERENT problem: A program team adopts scaled ceremonies but retains conflicting product priorities across four component teams. The key mechanism for the current situation is: Adaptive planning uses ongoing prioritization rather than fixed arbitrary task order.

Question 192

What ongoing preventive practice would most reduce recurrence of: A release backlog lists capabilities with no ordering although customer value and dependencies differ widely.

  1. Define urgent defect handling in team working agreements.
  2. Use recent throughput as a planning input.
  3. Revisit prioritization when new evidence arrives.
  4. Evaluate metrics against work-arrival patterns.

Explanation

Correct Answer

C:

Revisit prioritization when new evidence arrives. This helps prevent recurrence of: A release backlog lists capabilities with no ordering although customer value and dependencies differ widely. The required evidence of effective control is: The next iteration selects high-value feasible work from an ordered backlog.

Incorrect Answers

A:

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 prioritization when new evidence arrives.

B:

Use recent throughput as a planning input. That is a useful control for ANOTHER case: A Scrum team schedules six weeks of work in a two-week sprint despite its recent capacity being stable and lower. The current situation is better prevented by: Revisit prioritization when new evidence arrives.

D:

Evaluate metrics against work-arrival patterns. That is a useful control for ANOTHER case: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day. The current situation is better prevented by: Revisit prioritization when new evidence arrives.

Question 193

At a construction planning unit, the review identifies: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished. Which response best addresses the specific project management problem?

  1. Align progress metrics to agreed done criteria and accepted outcomes.
  2. Assess completed user-value outcomes alongside estimates and quality evidence.
  3. Establish explicit work stages and WIP limits to encourage completion flow.
  4. Translate scope components into prioritized, testable outcomes and backlog stories.

Explanation

Correct Answer

A:

Align progress metrics to agreed done criteria and accepted outcomes. This addresses the fictional case: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished. The project-management rationale is: Agile transparency depends on consistent completion definitions. Verify by: Burn-down reflects only genuinely finished backlog items.

Incorrect Answers

B:

Assess completed user-value outcomes alongside estimates and quality evidence. This would address a DIFFERENT fictional project situation: A scrum team reports velocity increasing after splitting every story into many identical subtask points without improving delivery. It is less directly applicable to: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished.

C:

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 sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished.

D:

Translate scope components into prioritized, testable outcomes and backlog stories. This would address a DIFFERENT fictional project situation: A traditional WBS describes all application components, but a team cannot identify any user-facing incremental delivery. It is less directly applicable to: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished.

Question 194

The project issue was: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished. Which outcome demonstrates that its remedy worked?

  1. The dashboard shows aging and delivery rate of individual items.
  2. Burn-down reflects only genuinely finished backlog items.
  3. The impediment log shows actual closure evidence and responsible owner.
  4. The pair validates code and both understand the implemented change.

Explanation

Correct Answer

B:

Burn-down reflects only genuinely finished backlog items. This validates the selected response: Align progress metrics to agreed done criteria and accepted outcomes. The relevant management principle is: Agile transparency depends on consistent completion definitions.

Incorrect Answers

A:

The dashboard shows aging and delivery rate of individual items. This is evidence for ANOTHER case: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day. The specific corrective response here is: Align progress metrics to agreed done criteria and accepted outcomes.

C:

The impediment log shows actual closure evidence and responsible owner. This is evidence for ANOTHER case: A team closes every blocker on its board when a manager acknowledges it, even though the dependency is unresolved. The specific corrective response here is: Align progress metrics to agreed done criteria and accepted outcomes.

D:

The pair validates code and both understand the implemented change. This is evidence for ANOTHER case: A developer believes pair programming in XP means one person codes while the other does unrelated email. The specific corrective response here is: Align progress metrics to agreed done criteria and accepted outcomes.

Question 195

For a construction planning unit, the documented failure was: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished. Which explanation is most accurate?

  1. Adaptive controls need cross-team transparency when increments interact.
  2. Story-point scales are relative and team-dependent.
  3. Agile transparency depends on consistent completion definitions.
  4. Adaptive prioritization is driven by value and risk rather than convenience alone.

Explanation

Correct Answer

C:

Agile transparency depends on consistent completion definitions. This explains the case: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished. The targeted action is: Align progress metrics to agreed done criteria and accepted outcomes.

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: Agile transparency depends on consistent completion definitions.

B:

Story-point scales are relative and team-dependent. This rationale better explains a DIFFERENT problem: An agile portfolio dashboard equates all story points across unrelated teams as identical units of value. The key mechanism for the current situation is: Agile transparency depends on consistent completion definitions.

D:

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: Agile transparency depends on consistent completion definitions.

Question 196

Which recurring governance check best addresses the risk of repeating: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished.

  1. Evaluate metrics against work-arrival patterns.
  2. Review the usefulness of tracking tools each retrospective.
  3. Refine oversized stories before iteration commitment.
  4. Audit status transitions against acceptance evidence.

Explanation

Correct Answer

D:

Audit status transitions against acceptance evidence. This helps prevent recurrence of: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished. The required evidence of effective control is: Burn-down reflects only genuinely finished backlog items.

Incorrect Answers

A:

Evaluate metrics against work-arrival patterns. That is a useful control for ANOTHER case: A continuous-flow team copies Scrum's sprint burndown even though work arrives independently throughout each day. The current situation is better prevented by: Audit status transitions against acceptance evidence.

B:

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: Audit status transitions against acceptance evidence.

C:

Refine oversized stories before iteration commitment. That is a useful control for ANOTHER case: A team says each user story must be one entire quarter in duration and cannot be split. The current situation is better prevented by: Audit status transitions against acceptance evidence.

Question 197

During a project review, stakeholders report: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient. What should the team do first?

  1. Maintain a product-owner-managed backlog to support coherent sprint planning.
  2. Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices.
  3. Select continuous-flow Kanban policies where they better fit the service than forced sprint batching.
  4. Select realistic sprint scope from empirical velocity and available capacity.

Explanation

Correct Answer

B:

Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices. This addresses the fictional case: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient. The project-management rationale is: Extreme Programming emphasizes technical engineering practices supporting rapid change. Verify by: Changes pass repeatable tests and code remains maintainable.

Incorrect Answers

A:

Maintain a product-owner-managed backlog to support coherent sprint planning. This would address a DIFFERENT fictional project situation: A Scrum team carries no ordered product backlog and creates its sprint goal from random requests. It is less directly applicable to: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient.

C:

Select continuous-flow Kanban policies where they better fit the service than forced sprint batching. This would address a DIFFERENT fictional project situation: A manager orders every team to run fixed-length sprints even though one support service has unpredictable continuous ticket arrivals. It is less directly applicable to: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient.

D:

Select realistic sprint scope from empirical velocity and available capacity. This would address a DIFFERENT fictional project situation: A Scrum team schedules six weeks of work in a two-week sprint despite its recent capacity being stable and lower. It is less directly applicable to: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient.

Question 198

Following the proposed correction, what observation confirms success: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient.

  1. Work is reviewed regularly and the plan adapts based on evidence.
  2. Emergency items move predictably without making all work urgent.
  3. Changes pass repeatable tests and code remains maintainable.
  4. The change is prioritized transparently with known displacement or escalation.

Explanation

Correct Answer

C:

Changes pass repeatable tests and code remains maintainable. This validates the selected response: Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices. The relevant management principle is: Extreme Programming emphasizes technical engineering practices supporting rapid change.

Incorrect Answers

A:

Work is reviewed regularly and the plan adapts based on evidence. This is evidence for ANOTHER case: A delivery group calls every requested change a new sprint without fixed review points or learning cycles. The specific corrective response here is: Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices.

B:

Emergency items move predictably without making all work urgent. This is evidence for ANOTHER case: A Kanban team has urgent requests interrupting every task with no explicit expedite policy. The specific corrective response here is: Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices.

D:

The change is prioritized transparently with known displacement or escalation. This is evidence for ANOTHER case: A stakeholder adds an urgent request mid-sprint and the team accepts it without evaluating its impact on the sprint goal. The specific corrective response here is: Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices.

Question 199

Which underlying planning or business-analysis mechanism explains: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient.

  1. Adaptive planning requires structured feedback, not unmanaged change.
  2. Scaling frameworks address coordination beyond one team's iteration mechanics.
  3. Organizational process assets can facilitate an adaptive lifecycle.
  4. Extreme Programming emphasizes technical engineering practices supporting rapid change.

Explanation

Correct Answer

D:

Extreme Programming emphasizes technical engineering practices supporting rapid change. This explains the case: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient. The targeted action is: Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices.

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: Extreme Programming emphasizes technical engineering practices supporting rapid change.

B:

Scaling frameworks address coordination beyond one team's iteration mechanics. This rationale better explains a DIFFERENT problem: A product team assumes SAFe is merely running one Scrum team's sprint with extra management meetings. The key mechanism for the current situation is: Extreme Programming emphasizes technical engineering practices supporting rapid change.

C:

Organizational process assets can facilitate an adaptive lifecycle. This rationale better explains a DIFFERENT problem: An organization has strong retrospective culture and automated tests but selects a rigid one-year scope baseline for an exploratory service. The key mechanism for the current situation is: Extreme Programming emphasizes technical engineering practices supporting rapid change.

Question 200

For the previous project issue, select the best preventive control: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient.

  1. Track test quality and technical debt in retrospectives.
  2. Revisit state policies when bottlenecks recur.
  3. Tailor method to demand and delivery characteristics.
  4. Apply lightweight readiness criteria before selection.

Explanation

Correct Answer

A:

Track test quality and technical debt in retrospectives. This helps prevent recurrence of: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient. The required evidence of effective control is: Changes pass repeatable tests and code remains maintainable.

Incorrect Answers

B:

Revisit state policies when bottlenecks recur. That is a useful control for ANOTHER case: A Kanban board contains no explicit entry or completion rules and stakeholders disagree on what In Review means. The current situation is better prevented by: Track test quality and technical debt in retrospectives.

C:

Tailor method to demand and delivery characteristics. That is a useful control for ANOTHER case: A manager orders every team to run fixed-length sprints even though one support service has unpredictable continuous ticket arrivals. The current situation is better prevented by: Track test quality and technical debt in retrospectives.

D:

Apply lightweight readiness criteria before selection. That is a useful control for ANOTHER case: A team estimates a story as small yet repeatedly discovers hidden dependencies after sprint commitment. The current situation is better prevented by: Track test quality and technical debt in retrospectives.