CAPM® Prep Hub — Free Certified Associate PM Practice Questions, Case Studies & Mock Exams
CAPM® Prep Hub is a free, all-in-one preparation tool for the Certified Associate in Project Management (CAPM)® exam, with 1,500 ECO-aligned practice questions, active-recall flashcards, 50 applied case studies, and 5 full-length mock exams across PM Fundamentals & Concepts (36%), Predictive Plan-Based Methodologies (17%), Agile Frameworks (20%), and Business Analysis Frameworks (27%). Every question maps to a task and enabler in the CAPM® Examination Content Outline (2023). This content is loaded interactively; the summary below is provided for search engines and readers without JavaScript. Last reviewed: 2026-09-13.
Exam at a glance
- Questions: 150 (including some unscored pretest items)
- Time: 3 hours (180 minutes)
- Domains & weight: PM Fundamentals & Concepts 36% · Predictive Plan-Based 17% · Agile Frameworks 20% · Business Analysis 27%
- Eligibility: Secondary degree + 23 hours of project management education
- Renewal: 15 PDUs every 3-year cycle
The 19 CAPM® ECO tasks (2023)
PM Fundamentals & Concepts (36%, 5 tasks)
- D1T1 — Demonstrate an understanding of project life cycles & processes: Distinguish between a project, program, and a portfolio; Distinguish between a project and operations; Distinguish between predictive and adaptive approaches (and more).
- D1T2 — Demonstrate an understanding of project management planning: Describe the purpose and importance of cost, quality, risk, schedule, etc.; Distinguish between the different deliverables of a project management plan versus product management plan; Distinguish differences between a milestone and a task duration (and more).
- D1T3 — Demonstrate an understanding of project roles & responsibilities: Compare and contrast the roles and responsibilities of project managers and project sponsors; Compare and contrast the roles and responsibilities of the project team and the project sponsor; Explain the importance of the role project managers play (initiator, negotiator, listener, coach, working member, facilitator) (and more).
- D1T4 — Determine how to follow & execute planned strategies or frameworks: Review the appropriate processes based on the framework, methodology, and/or practices; Determine the components of a change management plan based on a scenario; Review a benefits management plan for a given situation (and more).
- D1T5 — Demonstrate an understanding of common problem-solving tools & techniques: Evaluate the effectiveness of a meeting; Explain the purpose of focus groups, standup meetings, brainstorming, etc.; Apply root cause analysis techniques (5 Whys, fishbone/Ishikawa diagram) (and more).
Predictive Plan-Based (17%, 3 tasks)
- D2T1 — Explain when it is appropriate to use a predictive, plan-based approach: Identify the suitability of a predictive, plan-based approach for the organizational structure (e.g., virtual, colocation, matrix, hierarchical, etc.); Determine the activities within each process; Give examples of typical activities within each process (and more).
- D2T2 — Demonstrate an understanding of a project management plan schedule: Apply critical path methods; Calculate schedule variance; Explain work breakdown structures (WBS) (and more).
- D2T3 — Determine how to document project controls of predictive, plan-based projects: Identify artifacts that are used in predictive, plan-based projects; Calculate cost and schedule variances.
Agile Frameworks (20%, 5 tasks)
- D3T1 — Explain when it is appropriate to use an adaptive approach: Compare the pros and cons of adaptive and predictive, plan-based projects; Identify the suitability of adaptive approaches for the organizational structure (e.g., virtual, colocation, matrix structure, hierarchical, etc.); Identify organizational process assets and enterprise environmental factors that facilitate the use of adaptive approaches.
- D3T2 — Determine how to plan project iterations: Distinguish the logical units of iterations; Interpret the pros and cons of the iteration; Translate this WBS to an adaptive iteration (and more).
- D3T3 — Determine how to document project controls for an adaptive project: Identify artifacts that are used in adaptive projects.
- D3T4 — Explain the components of an adaptive plan: Distinguish between the components of different adaptive methodologies (e.g., Scrum, Extreme Programming (XP), Scaled Agile Framework (SAFe®), Kanban, etc.).
- D3T5 — Determine how to prepare and execute task management steps: Interpret success criteria of an adaptive project management task; Prioritize tasks in adaptive project management.
Business Analysis (27%, 6 tasks)
- D4T1 — Demonstrate an understanding of BA roles & responsibilities: Distinguish between stakeholder roles (e.g., process owner, process manager, product manager, product owner, etc.); Outline the need for roles and responsibilities (Why do you need to identify stakeholders in the first place?); Differentiate between internal and external roles.
- D4T2 — Determine how to conduct stakeholder communication: Recommend the most appropriate communication channel/tool (e.g., reporting, presentation, etc.); Demonstrate why communication is important for a business analyst between various teams (features, requirements, etc.).
- D4T3 — Determine how to gather requirements: Match tools to scenarios (e.g., user stories, use cases, etc.); Identify the requirements gathering approach for a situation (e.g., conduct stakeholder interviews, surveys, workshops, lessons learned, etc.); Explain a requirements traceability matrix/product backlog.
- D4T4 — Demonstrate an understanding of product roadmaps: Explain the application of a product roadmap; Determine which components go to which releases.
- D4T5 — Determine how project methodologies influence BA processes: Determine the role of a business analyst in adaptive and/or predictive, plan-based approaches.
- D4T6 — Validate requirements through product delivery: Define acceptance criteria (the action of defining changes based on the situation); Determine if a project/product is ready for delivery based on a requirements traceability matrix/product backlog.
Sample CAPM® practice questions
Which of the following best defines a 'project'? (PM Fundamentals & Concepts — Demonstrate an understanding of project life cycles & processes)
Answer: A temporary endeavor undertaken to create a unique product, service, or result
A project is specifically defined as a temporary endeavor with a unique output — not an ongoing repetitive activity (that describes operations), not an arbitrary grouping, and not a permanent department.
Why is it genuinely important for a project management plan to explicitly address cost, schedule, quality, and risk together, rather than considering each in complete isolation? (PM Fundamentals & Concepts — Demonstrate an understanding of project management planning)
Answer: These elements are genuinely interrelated, and a change in one (e.g., schedule) can meaningfully affect the others (e.g., cost or quality), so integrated planning helps produce a more realistic overall plan
These elements are genuinely interrelated (a schedule change can affect cost or quality), making integrated planning valuable — a substantive practice (not mere formality), these elements are not unrelated, and this concern applies regardless of a formal PMO's existence.
Which of the following BEST describes the PRIMARY role of a project sponsor, as distinct from a project manager? (PM Fundamentals & Concepts — Demonstrate an understanding of project roles & responsibilities)
Answer: A project sponsor typically provides funding, high-level organizational backing, and resolves issues escalated beyond the project manager's own authority
A sponsor typically provides funding, organizational backing, and resolves escalated issues — day-to-day execution and detailed schedule management (option B) is the project manager's role, these are genuinely distinct roles, and performing specific technical work (option D) is typically the project team's role.
Why should a project team review and follow processes genuinely appropriate to the specific framework or methodology selected for their project (e.g., predictive versus agile)? (PM Fundamentals & Concepts — Determine how to follow & execute planned strategies or frameworks)
Answer: Different frameworks genuinely have different underlying processes and practices, so following the appropriate processes for the selected framework helps ensure the project is executed consistently and effectively
Different frameworks genuinely have different underlying processes, so following the appropriate ones supports consistent, effective execution — a substantive practice (not mere formality), frameworks aren't identical in their processes, and this concern applies across industries, not solely technology.
Which of the following is a genuine, common indicator that a project meeting was effective? (PM Fundamentals & Concepts — Demonstrate an understanding of common problem-solving tools & techniques)
Answer: The meeting had a clear, genuine agenda and objective, and concluded with defined action items and owners
A clear agenda, objective, and defined action items with owners are genuine, standard indicators of meeting effectiveness — meeting duration, including every possible stakeholder, or a fixed daily schedule regardless of actual need are not genuine effectiveness indicators.
Which organizational structure genuinely gives the project manager the MOST authority, making it especially well-suited to a predictive, plan-based approach for large, complex projects? (Predictive Plan-Based — Explain when it is appropriate to use a predictive, plan-based approach)
Answer: A projectized organizational structure, where the project manager genuinely holds high authority and team members report directly to the project manager
A projectized structure gives the project manager high authority, with staff reporting directly to the PM — this genuinely supports the detailed, centralized planning and control typical of a predictive approach. Weak matrix and functional structures give the PM limited authority, and 'no defined reporting relationships' is not a genuine organizational structure.
What is the GENUINE definition of the critical path in a project schedule network diagram? (Predictive Plan-Based — Demonstrate an understanding of a project management plan schedule)
Answer: The genuinely longest sequence of dependent activities from project start to finish, which determines the shortest possible total project duration
The critical path is genuinely the longest sequence of dependent activities, determining the minimum possible project duration — it is not the shortest path, critical path activities genuinely have zero total float (not positive float), and staff seniority has no bearing on this definition.
Which artifact genuinely serves as a chronological record documenting problems that have already occurred on a project and require formal resolution? (Predictive Plan-Based — Determine how to document project controls of predictive, plan-based projects)
Answer: The issue log
The issue log genuinely tracks problems that have already occurred and require resolution — the risk register tracks future uncertain events, the stakeholder register tracks stakeholder information, and the lessons-learned register captures knowledge gained.
Which of the following is a genuine, key PRO of an adaptive approach compared to a predictive approach? (Agile Frameworks — Explain when it is appropriate to use an adaptive approach)
Answer: Genuinely greater flexibility to accommodate evolving requirements and incorporate frequent stakeholder feedback throughout the project
Greater flexibility to accommodate evolving requirements and frequent feedback is a genuine, defining pro of adaptive approaches — upfront cost/schedule certainty and fixed scope are actually genuine pros of predictive approaches instead, and adaptive approaches genuinely require MORE (not less) ongoing stakeholder engagement.
Which of the following BEST describes a 'sprint' as a genuine logical unit of iteration in Scrum? (Agile Frameworks — Determine how to plan project iterations)
Answer: A genuine, fixed-length time-box (typically one to four weeks) during which a genuine, potentially releasable product increment is created
A sprint is genuinely a fixed-length time-box (commonly 1-4 weeks) producing a potentially releasable increment — it is not open-ended, is not synonymous with the entire project duration, and is not a single administrative day.
Which artifact genuinely represents an ordered, prioritized list of all known work (features, requirements, fixes) that may genuinely need to be delivered for a product? (Agile Frameworks — Determine how to document project controls for an adaptive project)
Answer: The product backlog
The product backlog genuinely is the ordered, prioritized list of all known potential product work — the burndown chart tracks progress, the Definition of Done defines completion criteria, and a team charter documents team norms, none of which are the prioritized work list itself.
Which of the following is a genuine, defining component of the Scrum framework? (Agile Frameworks — Explain the components of an adaptive plan)
Answer: Fixed-length sprints, each concluding with a genuine sprint review and sprint retrospective
Fixed-length sprints concluding with review and retrospective ceremonies are genuine, defining Scrum components — continuous flow with no iteration boundaries describes Kanban instead, paired programming describes XP instead, and a fixed five-year unrevisable roadmap contradicts adaptive principles entirely.
Which of the following BEST describes the genuine purpose of documented 'acceptance criteria' for a specific user story? (Agile Frameworks — Determine how to prepare and execute task management steps)
Answer: Acceptance criteria genuinely define the specific, measurable conditions that must genuinely be satisfied for the story to be considered acceptable by the stakeholder or product owner
Acceptance criteria genuinely define specific, measurable conditions for a story's acceptance — this isn't a budget-allocation tool, doesn't eliminate the need for a sprint review demonstration, and is genuinely relevant to adaptive (not predictive) task management.
Which role genuinely holds primary accountability for a specific business process's overall design and end-to-end outcomes, rather than its day-to-day daily execution? (Business Analysis — Demonstrate an understanding of BA roles & responsibilities)
Answer: The process owner
The process owner is genuinely accountable for a specific process's overall design and outcomes ('is this process working as intended, end to end?') — the process manager instead handles day-to-day execution, while product owner and product manager both focus on product (not process) accountability.
A business analyst needs to deliver a concise, high-level overview of key findings and recommendations to a senior executive with limited time. Which communication tool is MOST genuinely appropriate? (Business Analysis — Determine how to conduct stakeholder communication)
Answer: An executive summary
An executive summary genuinely provides a concise, high-level overview suited to a time-constrained senior executive — a detailed RTM, a multi-hour workshop, and an undocumented hallway chat are all genuinely mismatched to this specific audience and need.
Key project management terms
- Project: A temporary endeavor undertaken to create a unique product, service, or result, with a defined beginning and end.
- Program: A group of related projects, subsidiary programs, and program activities managed in a coordinated way to obtain benefits not available from managing them individually.
- Portfolio: Projects, programs, and operations grouped together to achieve strategic business objectives, even if not directly related to one another.
- Operations: Ongoing, repetitive work that sustains the business, as distinct from a project's temporary, unique effort.
- Predictive (Plan-Based) Approach: A delivery approach where scope, schedule, and cost are largely planned in detail upfront, suited to stable, well-understood requirements.
- Adaptive (Agile) Approach: A delivery approach using short, iterative cycles that embrace evolving requirements and frequent stakeholder feedback.
- Hybrid Approach: A delivery approach blending predictive and adaptive elements within different components or phases of the same project.
- Work Breakdown Structure (WBS): A hierarchical decomposition of the total project scope into manageable work packages.
- Milestone: A significant point in time in a schedule, representing zero duration, such as completion of a major deliverable.
- Critical Path: The longest sequence of dependent activities that determines the shortest possible project duration.
- Risk Register: A living document capturing identified risks, their probability, impact, owner, and planned response.
- Stakeholder Register: A record of identified stakeholders including their role, interest, influence, and communication preference.
- RACI Matrix: A responsibility-assignment chart clarifying who is Responsible, Accountable, Consulted, and Informed for each activity.
- Root Cause Analysis: A structured technique (e.g., 5 Whys, fishbone/Ishikawa diagram) for tracing a problem to its underlying cause.
- Project Charter: The document that formally authorizes a project and gives the project manager authority to apply resources.
- Scrum: An agile framework organizing work into fixed-length sprints with defined roles, events, and artifacts.
- Sprint: A fixed-length time-box (typically one to four weeks) in Scrum during which a potentially releasable increment is created.
- Product Backlog: An ordered, evolving list of everything that might be needed in the product, continuously refined and re-prioritized.
- Definition of Done: A shared, agreed set of criteria an increment must meet to be considered complete.
- Velocity: The average amount of work an agile team completes per iteration, used to forecast capacity.
- Kanban Board: A visual board with columns representing workflow stages, used to make work state and flow immediately apparent.
- WIP Limit: A cap on work-in-progress at a stage or level that encourages finishing before starting and improves flow.
- Burndown Chart: A visual showing work remaining over time within an iteration or release.
- Business Analyst (BA): The role responsible for eliciting, analyzing, documenting, and validating requirements on behalf of stakeholders.
- Requirements Elicitation: The activity of drawing out requirements from stakeholders through interviews, workshops, surveys, and observation.
- Requirements Traceability Matrix (RTM): A tool linking requirements to their source and to related design, test, and delivery artifacts.
- Product Roadmap: A visual summary mapping product features and priorities over time, connecting the backlog to organizational goals.
- Acceptance Criteria: Specific, testable conditions that confirm whether a requirement or user story has been satisfied.
- User Story: A concise unit of desired functionality (As a..., I want..., so that...), typically elaborated with acceptance criteria.
- Earned Value Management (EVM): A technique integrating scope, schedule, and cost to measure performance using Planned Value, Earned Value, and Actual Cost.
- Change Control Board (CCB): A group with authority to review, approve, or reject proposed changes to project baselines.
- Servant Leadership: A leadership style focused on removing impediments and enabling the team's success rather than directing in detail.
- Tuckman's Model: The team-development stages Forming, Storming, Norming, Performing (and Adjourning).
- 5 Whys: An iterative questioning technique that repeatedly asks 'why' to trace a symptom back to its root cause.
- Force Field Analysis: A decision-making technique that identifies driving forces supporting a change and restraining forces opposing it.
- Cost-Benefit Analysis: A technique comparing the expected costs of an initiative against its expected benefits to judge whether it is justified.
- Contingency Reserve: Budget or time set aside for identified risks (known-unknowns), typically controlled by the project manager.
- Issue Log: A document tracking problems that have already occurred and require resolution, distinct from future, uncertain risks.
- Product Owner: The role accountable for maximizing product value and prioritizing the product backlog in agile delivery.
- Project Sponsor: The individual or group that provides funding, organizational backing, and resolves issues beyond the project manager's authority.
Frequently asked questions
How many questions are on the CAPM exam?
The CAPM exam has 150 questions (including some unscored pretest items) to be completed in 3 hours (180 minutes).
What are the four CAPM domains and their weights?
PM Fundamentals & Concepts 36%, Predictive Plan-Based Methodologies 17%, Agile Frameworks 20%, and Business Analysis Frameworks 27%, per the 2023 Examination Content Outline.
What are the eligibility requirements for the CAPM?
A secondary degree (high school diploma, associate's degree, or global equivalent) plus 23 hours of project management education completed before the exam.
How many PDUs are required to renew the CAPM?
15 PDUs every 3-year cycle in project management topics, plus the renewal fee.
Is the CAPM Prep Hub free?
Yes. All 1,500 practice questions, flashcards, 50 case studies, and 5 mock exams are free to use in any modern browser, with progress saved locally on your device.
How should I study for the CAPM exam?
Study by ECO domain, task, and enabler, drill the practice bank with detailed explanations, use flashcards for active recall, review case studies, and take full-length timed mock exams until you consistently score around 75% or higher.
CAPM, PMP, PMI-ACP, PMI-RMP, PMI-PBA and PMI are registered marks of the Project Management Institute, Inc. This is an independent study resource and is not affiliated with or endorsed by PMI.