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 5

Question 40

For the previous project issue, select the best preventive control: A two-week sprint begins without a selected goal and developers start ten unrelated backlog items.

  1. Require goal clarity in sprint planning.
  2. Refine oversized stories before iteration commitment.
  3. Identify risky interfaces during backlog refinement.
  4. Review expedited work frequency and impact.

Explanation

Correct Answer

A:

Require goal clarity in sprint planning. This helps prevent recurrence of: A two-week sprint begins without a selected goal and developers start ten unrelated backlog items. The required evidence of effective control is: The sprint review demonstrates a coherent usable outcome against the planned goal.

Incorrect Answers

B:

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: Require goal clarity in sprint planning.

C:

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: Require goal clarity in sprint planning.

D:

Review expedited work frequency and impact. That is a useful control for ANOTHER case: A Kanban team has urgent requests interrupting every task with no explicit expedite policy. The current situation is better prevented by: Require goal clarity in sprint planning.

Question 41

For a financial-services implementation team, a delivery problem is reported: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. Which action fits the situation?

  1. Establish a coordinated view of cross-team dependencies and release readiness while retaining team-level boards.
  2. Keep visible rationale for priority changes and relevant stakeholder decisions.
  3. Maintain a visible backlog, iteration board and meaningful delivery measures.
  4. Coordinate transparent replanning of work in accordance with the sprint goal and team governance.

Explanation

Correct Answer

C:

Maintain a visible backlog, iteration board and meaningful delivery measures. This addresses the fictional case: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. The project-management rationale is: Adaptive controls use lightweight transparent artifacts rather than no artifacts. Verify by: Stakeholders can view current priorities, completed items and blockers.

Incorrect Answers

A:

Establish a coordinated view of cross-team dependencies and release readiness while retaining team-level boards. This would address a DIFFERENT fictional project situation: A multi-site project has separate sprint boards that cannot show one shared release objective or integration issue. It is less directly applicable to: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts.

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: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts.

D:

Coordinate transparent replanning of work in accordance with the sprint goal and team governance. This would address a DIFFERENT fictional project situation: A product manager treats sprint backlog as a static contract that cannot change even when a critical safety defect emerges. It is less directly applicable to: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts.

Question 42

How should the project team verify a successful response to: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts.

  1. Burn-down reflects only genuinely finished backlog items.
  2. The impediment log shows actual closure evidence and responsible owner.
  3. Throughput metrics align with completed user value and actual acceptance evidence.
  4. Stakeholders can view current priorities, completed items and blockers.

Explanation

Correct Answer

D:

Stakeholders can view current priorities, completed items and blockers. This validates the selected response: Maintain a visible backlog, iteration board and meaningful delivery measures. The relevant management principle is: Adaptive controls use lightweight transparent artifacts rather than no artifacts.

Incorrect Answers

A:

Burn-down reflects only genuinely finished backlog items. This is evidence for ANOTHER case: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished. The specific corrective response here is: Maintain a visible backlog, iteration board and meaningful delivery measures.

B:

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: Maintain a visible backlog, iteration board and meaningful delivery measures.

C:

Throughput metrics align with completed user value and actual acceptance evidence. This is evidence for ANOTHER case: A team repeatedly splits stories after sprint completion to make velocity reports look favorable. The specific corrective response here is: Maintain a visible backlog, iteration board and meaningful delivery measures.

Question 43

A project team asks why this occurs: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. Which project management principle best explains it?

  1. Adaptive controls use lightweight transparent artifacts rather than no artifacts.
  2. Adaptive progress is best assessed using working outputs and accepted outcomes.
  3. Adaptive controls need cross-team transparency when increments interact.
  4. Adaptive decomposition emphasizes incremental value and feedback over component-only progress.

Explanation

Correct Answer

A:

Adaptive controls use lightweight transparent artifacts rather than no artifacts. This explains the case: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. The targeted action is: Maintain a visible backlog, iteration board and meaningful delivery measures.

Incorrect Answers

B:

Adaptive progress is best assessed using working outputs and accepted outcomes. This rationale better explains a DIFFERENT problem: A release review uses only a slide deck of planned stories and never demonstrates working product. The key mechanism for the current situation is: Adaptive controls use lightweight transparent artifacts rather than no artifacts.

C:

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: Adaptive controls use lightweight transparent artifacts rather than no artifacts.

D:

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 controls use lightweight transparent artifacts rather than no artifacts.

Question 44

At a financial-services implementation team, the team wants to avoid repeating: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. Which safeguard should it retain?

  1. Audit status transitions against acceptance evidence.
  2. Review the usefulness of tracking tools each retrospective.
  3. Evaluate metrics against work-arrival patterns.
  4. Review cadence changes as process experiments rather than ad hoc demands.

Explanation

Correct Answer

B:

Review the usefulness of tracking tools each retrospective. This helps prevent recurrence of: An agile team claims it has no need for any progress artifacts because it avoids detailed Gantt charts. The required evidence of effective control is: Stakeholders can view current priorities, completed items and blockers.

Incorrect Answers

A:

Audit status transitions against acceptance evidence. That is a useful control for ANOTHER case: A sprint burndown looks healthy because completed tasks are removed before acceptance tests are finished. The current situation is better prevented by: Review the usefulness of tracking tools each retrospective.

C:

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: Review the usefulness of tracking tools each retrospective.

D:

Review cadence changes as process experiments rather than ad hoc demands. That is a useful control for ANOTHER case: An agile team changes sprint duration every week because a manager wants reports earlier. The current situation is better prevented by: Review the usefulness of tracking tools each retrospective.

Question 45

A CAPM-level project coordinator sees: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management. What is the best next approved step?

  1. Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices.
  2. Define a coherent inspect-and-adapt cadence suited to chosen framework.
  3. Select the needed controls and approach based on product uncertainty and contract dependencies.
  4. Clarify Scrum accountabilities and enable the developers to organize their work within the sprint goal.

Explanation

Correct Answer

D:

Clarify Scrum accountabilities and enable the developers to organize their work within the sprint goal. This addresses the fictional case: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management. The project-management rationale is: Scrum relies on defined accountabilities and self-management. Verify by: Daily work selections are made by the team and reviewed against the goal.

Incorrect Answers

A:

Incorporate automated testing, continuous integration and appropriate refactoring as mutually reinforcing practices. This would address a DIFFERENT fictional project situation: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient. It is less directly applicable to: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management.

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 team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management.

C:

Select the needed controls and approach based on product uncertainty and contract dependencies. This would address a DIFFERENT fictional project situation: A fixed-price hardware deployment has stable component specifications, but leadership insists on adaptive ceremonies to avoid documenting delivery dependencies. It is less directly applicable to: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management.

Question 46

For a university infrastructure office, what is the strongest acceptance evidence after addressing: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management.

  1. Daily work selections are made by the team and reviewed against the goal.
  2. Cross-team dependencies and program-level planning are explicitly managed.
  3. Participating teams can trace work to an agreed release objective.
  4. The security defect receives the appropriate priority with documented rationale.

Explanation

Correct Answer

A:

Daily work selections are made by the team and reviewed against the goal. This validates the selected response: Clarify Scrum accountabilities and enable the developers to organize their work within the sprint goal. The relevant management principle is: Scrum relies on defined accountabilities and self-management.

Incorrect Answers

B:

Cross-team dependencies and program-level planning are explicitly managed. This is evidence for ANOTHER case: A product team assumes SAFe is merely running one Scrum team's sprint with extra management meetings. The specific corrective response here is: Clarify Scrum accountabilities and enable the developers to organize their work within the sprint goal.

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: Clarify Scrum accountabilities and enable the developers to organize their work within the sprint goal.

D:

The security defect receives the appropriate priority with documented rationale. This is evidence for ANOTHER case: A product owner ranks bug fixes only by how many users complained, ignoring a low-volume critical security vulnerability. The specific corrective response here is: Clarify Scrum accountabilities and enable the developers to organize their work within the sprint goal.

Question 47

A postincident review considers: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management. Which principle most directly accounts for the behavior?

  1. Agile frameworks differ in cadence and work management.
  2. Scrum relies on defined accountabilities and self-management.
  3. Product inspection and team-process inspection serve distinct purposes.
  4. Excessive parallel work can reduce flow and predictability.

Explanation

Correct Answer

B:

Scrum relies on defined accountabilities and self-management. This explains the case: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management. The targeted action is: Clarify Scrum accountabilities and enable the developers to organize their work within the sprint goal.

Incorrect Answers

A:

Agile frameworks differ in cadence and work management. This rationale better explains a DIFFERENT problem: A manager orders every team to run fixed-length sprints even though one support service has unpredictable continuous ticket arrivals. The key mechanism for the current situation is: Scrum relies on defined accountabilities and self-management.

C:

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: Scrum relies on defined accountabilities and self-management.

D:

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: Scrum relies on defined accountabilities and self-management.

Question 48

What ongoing preventive practice would most reduce recurrence of: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management.

  1. Track test quality and technical debt in retrospectives.
  2. Assess collaboration effectiveness in technical retrospectives.
  3. Coach managers on servant leadership and boundaries.
  4. Review material risk as part of regular backlog refinement.

Explanation

Correct Answer

C:

Coach managers on servant leadership and boundaries. This helps prevent recurrence of: A team uses Scrum but assigns all daily task decisions to a line manager, undermining team self-management. The required evidence of effective control is: Daily work selections are made by the team and reviewed against the goal.

Incorrect Answers

A:

Track test quality and technical debt in retrospectives. That is a useful control for ANOTHER case: An XP team avoids automated tests and refactoring because leaders believe continuous integration is sufficient. The current situation is better prevented by: Coach managers on servant leadership and boundaries.

B:

Assess collaboration effectiveness in technical retrospectives. That is a useful control for ANOTHER case: A developer believes pair programming in XP means one person codes while the other does unrelated email. The current situation is better prevented by: Coach managers on servant leadership and boundaries.

D:

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: Coach managers on servant leadership and boundaries.

Question 49

At a construction planning unit, the review identifies: An agile team marks a story done because coding finished even though its required customer acceptance test failed. Which response best addresses the specific project management problem?

  1. Complete the agreed acceptance criteria and definition of done before counting the story delivered.
  2. Reorder relevant backlog work according to the new risk and product ownership decision.
  3. Prioritize using product value, risk and dependencies under the product owner's agreed role.
  4. Define testable acceptance criteria for backlog items before completion decisions.

Explanation

Correct Answer

A:

Complete the agreed acceptance criteria and definition of done before counting the story delivered. This addresses the fictional case: An agile team marks a story done because coding finished even though its required customer acceptance test failed. The project-management rationale is: A completed task must satisfy accepted outcome criteria, not just coding effort. Verify by: The story passes authorized functional tests and is accepted.

Incorrect Answers

B:

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: An agile team marks a story done because coding finished even though its required customer acceptance test failed.

C:

Prioritize using product value, risk and dependencies under the product owner's agreed role. This would address a DIFFERENT fictional project situation: Two backlog items compete for one iteration, and a sponsor picks the easier one while ignoring urgent user risk. It is less directly applicable to: An agile team marks a story done because coding finished even though its required customer acceptance test failed.

D:

Define testable acceptance criteria for backlog items before completion decisions. This would address a DIFFERENT fictional project situation: A sprint review shows features built but no acceptance criteria agreed with stakeholders. It is less directly applicable to: An agile team marks a story done because coding finished even though its required customer acceptance test failed.

Question 50

The project issue was: An agile team marks a story done because coding finished even though its required customer acceptance test failed. Which outcome demonstrates that its remedy worked?

  1. Throughput metrics align with completed user value and actual acceptance evidence.
  2. The story passes authorized functional tests and is accepted.
  3. The test scenario proves whether the story fulfills the requested behavior.
  4. Cycle time and work-in-progress decrease while throughput stabilizes.

Explanation

Correct Answer

B:

The story passes authorized functional tests and is accepted. This validates the selected response: Complete the agreed acceptance criteria and definition of done before counting the story delivered. The relevant management principle is: A completed task must satisfy accepted outcome criteria, not just coding effort.

Incorrect Answers

A:

Throughput metrics align with completed user value and actual acceptance evidence. This is evidence for ANOTHER case: A team repeatedly splits stories after sprint completion to make velocity reports look favorable. The specific corrective response here is: Complete the agreed acceptance criteria and definition of done before counting the story delivered.

C:

The test scenario proves whether the story fulfills the requested behavior. This is evidence for ANOTHER case: A team starts implementation from a vague user story with no expected behavior or acceptance criteria. The specific corrective response here is: Complete the agreed acceptance criteria and definition of done before counting the story delivered.

D:

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: Complete the agreed acceptance criteria and definition of done before counting the story delivered.