Practice PMI CAPM with free sample questions, timed mock exams, and detailed explanations in PM Mastery.
CAPM is PMI’s entry-level project-management certification for candidates building core planning, delivery, stakeholder, and business-analysis judgment. If you are searching for CAPM sample exam questions, a practice test, or an exam simulator, this is the main PM Mastery page to start on web and continue on iOS or Android with the same PM Mastery account.
Start a practice session for PMI Certified Associate in Project Management (CAPM) below, or open the full app in a new tab. For the best experience, open the full app in a new tab and navigate with swipes/gestures or the mouse wheel—just like on your phone or tablet.
Open Full App in a New TabA small set of questions is available for free preview. Subscribers can unlock full access by signing in with the same app-family account they use on web and mobile.
Use on iPhone or Android too: PM Mastery on the App Store or PM Mastery on Google Play using the same PM Mastery account you use on web. The same PM Mastery subscription works across web and mobile.
Free diagnostic: Try the 150-question CAPM full-length practice exam before subscribing.
Official source check: Last checked May 5, 2026 against PMI's public CAPM certification page.
PMI's public page lists 150 questions, 180 minutes, 15 unscored pretest questions, and the four CAPM content areas used below. Confirm current appointment rules and eligibility directly with PMI before booking.
CAPM rewards best-next-step thinking. Strong performance usually comes from choosing the right artifact, sequence, escalation path, or delivery approach for the situation rather than just recalling isolated definitions.
| Domain | Weight | Target items |
|---|---|---|
| Project Management Fundamentals and Core Concepts | 36% | 54 |
| Predictive, Plan-Based Methodologies | 17% | 26 |
| Agile Frameworks/Methodologies | 20% | 30 |
| Business Analysis Frameworks | 27% | 40 |
Use these filters when an answer choice sounds familiar but you are not sure which project approach the prompt expects. CAPM usually rewards the best next step for the situation, not the most advanced-sounding term.
| Scenario signal | First check | Strong answer usually… | Weak answer usually… |
|---|---|---|---|
| The work is predictable and scope is stable | What baseline, plan, artifact, or approval controls the next step? | Uses the right plan, sequence, change process, or stakeholder communication. | Skips planning because the answer sounds more agile. |
| The work is uncertain or evolving | What feedback loop or backlog decision is needed? | Uses iterative refinement, collaboration, review, and adaptation. | Freezes detailed scope too early. |
| A stakeholder need is unclear | What requirement, acceptance criterion, or business-analysis artifact is missing? | Clarifies the need, confirms value, and traces it to deliverables or backlog items. | Starts solution design before understanding the requirement. |
| A risk, issue, or change appears | Is this a risk, issue, change request, impediment, or defect? | Classifies the situation and follows the right response path. | Uses one generic escalation answer for every problem. |
| Team communication is breaking down | What information is missing, delayed, or misunderstood? | Improves transparency, working agreements, stakeholder engagement, or communication flow. | Adds meetings without fixing the underlying information gap. |
Use this map after a timed set. CAPM readiness improves when you can name the project-management reason behind the answer, not just the definition.
| Domain | What the exam is really testing | What PM Mastery practice should force you to decide | Common wrong-answer trap |
|---|---|---|---|
| Project fundamentals | Whether you understand core roles, artifacts, constraints, governance, and project life cycles | Which artifact, role, process, or stakeholder action fits the situation | Choosing a term you recognize without checking the scenario |
| Predictive methods | Whether you can apply plan-driven sequencing and control | When to baseline, estimate, manage change, report variance, or follow a plan | Treating every change as informal adaptation |
| Agile methods | Whether you can use feedback, backlog refinement, team ownership, and incremental delivery | When to inspect, adapt, prioritize, review, or adjust working agreements | Using agile words while still choosing command-and-control behavior |
| Business analysis | Whether requirements connect to value and acceptance | How to elicit, analyze, trace, validate, and prioritize requirements | Jumping from stakeholder request directly to solution design |
| Window | What to do | What not to do |
|---|---|---|
| Days 7-5 | Complete a mixed timed set or the full-length diagnostic, then classify misses by fundamentals, predictive, agile, business analysis, or timing. | Do not only reread definitions; write the project situation that controlled the answer. |
| Days 4-3 | Drill the two weakest domains and compare similar concepts such as risk vs issue, requirement vs solution, backlog vs WBS, and change request vs impediment. | Do not keep repeating your strongest domain because it feels comfortable. |
| Days 2-1 | Review recurring traps: wrong life-cycle assumption, premature solutioning, unmanaged change, vague stakeholder communication, and process words without context. | Do not start a huge new set if fatigue will make basic reading mistakes more likely. |
| Exam day | Identify the life cycle, role, artifact, and next decision before choosing the answer. | Do not choose an answer just because it contains a familiar PMI or agile term. |
The goal is not to memorize every foundational question. The goal is to build enough project judgment that you can classify a new scenario and choose the next best action.
If you can complete several varied timed attempts at 75% or higher, explain why each missed answer was a better fit for a different situation, and switch between predictive, agile, and business-analysis reasoning without hesitation, it is usually time to sit the exam rather than repeating questions you already recognize.
These are original PM Mastery practice questions aligned to CAPM project fundamentals, predictive planning, agile/adaptive delivery, and business-analysis decisions. They are not PMI exam items, are not copied from any exam sponsor, and should be used to practice foundational project-management judgment rather than memorize exact wording. Use them to check your readiness here, then continue in PM Mastery with mixed sets, topic drills, and timed mocks.
Topic: Domain 3: Agile Frameworks/Methodologies
A cross-functional agile team has completed three sprints. Retrospectives repeatedly identify unclear handoffs and too many work-in-progress (WIP) items. The scrum master says the team is “improving,” but the project sponsor wants evidence that the team is capturing lessons learned continuously and actually updating how it works.
Which artifact best validates this behavior?
Best answer: B
Explanation: Continuous lessons learned in agile are typically surfaced in retrospectives and should result in explicit changes to how the team collaborates. The strongest validation is an artifact that shows both the insights and the concrete, adopted updates to team behaviors. A dated, version-controlled record of working agreement updates provides direct evidence of that loop.
The concept being tested is the inspect-and-adapt feedback loop: teams identify what to improve (lessons learned) and then change their operating norms so the improvement is visible and repeatable. In an agile context, lessons learned are not just notes-they should lead to updated team working agreements (e.g., WIP limits, handoff rules, definitions of ready/done, meeting norms) that the team follows.
The best validating evidence is an artifact that demonstrates:
Charts about delivery output can improve while collaboration problems persist, so they do not directly validate that lessons learned are being incorporated into working agreements.
Topic: Domain 3: Agile Frameworks/Methodologies
A project team is using Scrum to build a new customer self-service portal. The sponsor approved a high-level scope statement with three capabilities: account management, billing, and support chat. Constraints: the team has only two weeks to prepare for Sprint 1 planning, stakeholders disagree on what to deliver first, and the product owner wants a single list the team can continuously refine.
What is the BEST next action to break down the scope into a prioritized backlog?
Best answer: C
Explanation: In Scrum, approved high-level scope should be elaborated into a product backlog that can be refined over time. The best way to do this quickly and transparently is to capture the capabilities as epics, decompose them into smaller features and user stories, and then prioritize the resulting backlog with key stakeholders to resolve disagreements on order.
A prioritized backlog is created by progressively breaking down scope from large to small and then ordering the work for value and risk. With only high-level capabilities and stakeholder disagreement, the product owner needs a single product backlog that is detailed enough to support near-term planning and flexible enough to evolve.
A practical sequence is:
This produces one continuously refined list that supports Sprint 1 planning without requiring predictive baselining; the sprint backlog is then selected from the top of the prioritized product backlog.
Topic: Domain 1: Project Management Fundamentals and Core Concepts
A project has an approved communications management plan that calls for a weekly one-page status report to all stakeholders and a biweekly steering committee meeting for decisions. Midway through execution, a new operations manager (key stakeholder) says they feel “out of the loop” and asks for daily updates. The sponsor does not want to add meetings, and the next steering committee is in 2 days.
What is the BEST next action to keep stakeholders informed and aligned?
Best answer: A
Explanation: The best way to keep stakeholders informed and aligned is to use the established status reporting mechanism and the planned governance cadence for decisions. Sending the status report early addresses the immediate information gap, and framing decision needs for the steering committee uses the existing forum for alignment without adding meetings.
Status reporting provides timely visibility into progress, issues, risks, and next steps, while governance cadence (for example, a steering committee) is where decisions and alignment are formally obtained. In this scenario, the communications plan already defines a weekly status report for broad visibility and a biweekly steering committee for decisions, and the sponsor does not want additional meetings.
The best next step is to:
This keeps communication consistent with the plan while using the next scheduled governance touchpoint to maintain alignment.
Topic: Domain 1: Project Management Fundamentals and Core Concepts
You are the project manager for a hybrid customer self-service portal project. During execution, a new regulation requires additional security controls that would add about 6 weeks and 15% cost. The sponsor set tolerance at +/-2 weeks and +/-5% cost.
In addition, Marketing and Operations are deadlocked on which features must be included in the next release; you facilitated two alignment workshops, but they still cannot agree and a decision is needed this week.
Which TWO actions best reflect the purpose of a steering committee/governance body and when escalation is needed? Select TWO.
Best answers: C, E
Explanation: A steering committee/governance body provides oversight and makes decisions that affect strategy, funding, scope, and major priorities. Escalation is appropriate when impacts exceed approved tolerances or when the project manager and stakeholders cannot resolve a decision within the project’s authority and time constraints. Here, both the regulatory impact and the cross-functional deadlock require governance direction.
A steering committee (or governance body) exists to provide oversight, ensure alignment with business objectives, and make timely decisions on high-impact matters the project cannot resolve within its authority. Typical triggers for escalation include:
In this scenario, the regulatory change exceeds both schedule and cost tolerances, so it requires a governance decision on trade-offs (approve additional funding/time, de-scope elsewhere, or change release strategy). Separately, the unresolved Marketing vs. Operations priority conflict has already resisted facilitation and needs an authoritative decision to protect delivery.
Topic: Domain 3: Agile Frameworks/Methodologies
A Scrum Team has missed its sprint goal for three sprints. Daily scrums feel like status reports to the Scrum Master, who frequently reassigns tasks during the meeting and asks team members to get approval before trying new solutions. In retrospectives, most people stay quiet and the same impediments remain open sprint after sprint.
What is the most likely underlying cause of the performance problem?
Best answer: C
Explanation: Agile teams perform best when leaders act as servant leaders-coaching, enabling, and removing impediments rather than directing tasks. The clues show the Scrum Master is controlling how work is done and discouraging autonomy, which reduces ownership and psychological safety. That leadership behavior is the primary issue driving the repeated missed goals and lack of improvement.
Servant leadership in agile focuses on serving the team so it can self-manage and continuously improve. In the scenario, the Scrum Master turns the daily scrum into a status meeting, reassigns work, and requires approvals before experimentation-signals of command-and-control behavior. This reduces autonomy and ownership and makes people less willing to speak up, which explains the quiet retrospectives and recurring impediments.
Effective servant leader behaviors include:
When servant leadership is missing, teams often repeat the same problems sprint after sprint even if the ceremonies occur.
Topic: Domain 2: Predictive, Plan-Based Methodologies
A project team is delivering a customer portal using a hybrid approach. The quality management plan defines (1) a biweekly process quality audit using a checklist and (2) planned inspections and functional tests of completed features against documented quality metrics and acceptance criteria. Several defects were found in the last increment.
Which TWO actions should the project manager take to follow the planned quality approach and document results? (Select TWO)
Best answers: A, C
Explanation: The quality management plan already specifies which quality activities to perform and what evidence to capture. Performing the scheduled quality audit and the planned inspections/tests applies the defined quality approach. Documenting the audit findings and test/inspection results provides objective records of quality performance and nonconformities.
A planned quality management approach means executing the quality activities defined in the quality management plan (not improvising or changing standards as a first step) and capturing objective evidence of results. In this scenario, the plan explicitly calls for a periodic process audit (quality assurance) and inspections/functional testing of completed work (quality control).
To apply the plan:
Taking corrective action may follow, but it should be based on documented results and tracked through appropriate logs and plans.
Topic: Domain 4: Business Analysis Frameworks
A project team is gathering requirements for a new internal expense-reimbursement application. The following stakeholders are involved:
Who is the primary decision maker for requirements approval in this scenario?
Best answer: B
Explanation: A decision maker is the stakeholder with the authority to approve or reject requirements and commit the organization to a course of action. In the scenario, only one person is stated to have final approval over the requirements baseline and funding. That authority is the decisive factor for identifying the decision maker.
In business analysis, stakeholders often include end users, SMEs, and decision makers, and the key differentiator is the type of contribution they make. End users primarily provide needs and usability feedback because they will use the product in day-to-day work. SMEs provide specialized knowledge (policy, regulatory, technical, or process expertise) to ensure requirements are correct and feasible. Decision makers are accountable for approving requirements (or a requirements baseline) and authorizing the investment or direction.
Here, the scenario explicitly states who has final authority to approve the requirements baseline and funding, which is the defining characteristic of the decision-maker role. Others may strongly influence decisions, but influence is not the same as approval authority.
Topic: Domain 1: Project Management Fundamentals and Core Concepts
You are managing a predictive project to roll out new point-of-sale software to 40 stores. Midway through execution, the Operations director emails you asking to add an offline mode, saying it is “mandatory,” while the Finance manager replies that no additional funding will be approved. Before you decide whether to proceed, what should you clarify first?
Best answer: D
Explanation: The situation contains conflicting direction, so the first step is to determine which stakeholder role has legitimate decision authority over scope and funding. Stakeholder influence depends on their power and accountability (for example, sponsor or designated change approval body). Once authority is clear, you can evaluate impacts and route the request appropriately.
When stakeholders give competing instructions, the project manager should not treat the loudest voice as the decision-maker. First, clarify stakeholder roles and influence: who is accountable for project funding and who is authorized to approve changes to scope, schedule, and cost (often the project sponsor and/or a defined change control authority). In this scenario, Operations is asserting a requirement while Finance is constraining funding; the correct next move is to confirm who has final approval rights and the escalation path. After that, you can gather estimates, document the change request, and facilitate a decision consistent with governance and stakeholder influence. The key takeaway is to verify decision authority before analyzing or committing to change work.
Topic: Domain 2: Predictive, Plan-Based Methodologies
A predictive software project has started executing its risk responses. The team implemented a mitigation for the risk of “test environment instability” by adding daily environment health checks. Two weeks later, a new risk is identified: a key vendor may change their API with only 10 days’ notice.
Which artifact best provides evidence to validate risk response effectiveness over time while also recording newly identified risks?
Best answer: D
Explanation: The risk register is the primary repository for documenting newly identified risks and monitoring existing risks after responses are implemented. By updating risk status, current probability/impact (or risk score), and residual risk, it provides the best evidence of whether responses are working over time.
In predictive projects, the risk register is a key control document used throughout the project to both capture new risks and monitor existing ones. To validate response effectiveness, the register is updated with response implementation status and results (for example, updated probability/impact, residual risk, risk score trend, triggers observed, and any secondary risks). This creates an auditable record showing whether the mitigation (daily health checks) is reducing the “test environment instability” risk and ensures the newly identified vendor API-change risk is formally recorded, owned, and planned.
Other project documents may reference risk-related work, but they do not provide the consolidated, time-based view of risk exposure and response performance that the risk register is designed to maintain.
Topic: Domain 2: Predictive, Plan-Based Methodologies
You have just taken over as an associate project manager on a predictive infrastructure upgrade project. The sponsor says, “We’re behind schedule and I need a clear picture for the steering committee.” Team members disagree about whether the project is actually off track.
Before you decide what to communicate and whether escalation is needed, what should you obtain first to monitor and control the project objectively?
Best answer: B
Explanation: To monitor and control a predictive project, you first need objective performance information compared to the approved baselines. A current status report summarizes actual progress and highlights variances so you can determine whether the project is truly behind schedule and what level of communication or escalation is appropriate.
In predictive projects, monitoring and controlling relies on comparing actual performance to the approved baselines (for example, schedule and cost baselines). When stakeholders claim the project is “behind” but the team disagrees, the first step is to obtain an artifact that reports current performance and/or variances so you can make an evidence-based determination.
A status report is designed to provide a snapshot of where the project stands (completed work, remaining work, key milestones, and issues/risks as applicable) and can show progress against the schedule baseline. With that information, you can then decide what message to send to the steering committee and whether deeper analysis (such as a detailed variance report) or escalation is warranted. The key takeaway is to start with objective performance reporting, not historical references or administrative preferences.
Topic: Domain 4: Business Analysis Frameworks
A project team is delivering a new internal expense-reporting feature in two-week iterations. Before releasing the next increment, the business analyst wants to ensure requirements are both built correctly and solve the business need.
Which statement is INCORRECT about verification and validation in this situation?
Best answer: B
Explanation: Verification is about conformance to documented requirements (built correctly), while validation is about fitness for intended use (built the right thing). In iterative delivery, teams typically verify via reviews and acceptance-criteria checks and validate via user evaluation of the working increment. Using a demo mainly to prove completeness/consistency mixes up these two concepts.
Verification answers “Did we build it right?” by checking the deliverable against specified requirements, acceptance criteria, and traceability (e.g., reviews, inspections, and test-case-to-requirement coverage). Validation answers “Did we build the right thing?” by confirming with stakeholders/end users that the delivered increment works for their real workflows and intended use (e.g., demos, UAT, pilot use).
Both are needed because you can produce a deliverable that perfectly matches written requirements (verified) yet still fails to solve the actual business problem (not validated), or users may like it (validated) but it may not meet agreed specifications or be fully traceable (not verified). The key is not to swap the purpose of demos versus verification activities.
Topic: Domain 1: Project Management Fundamentals and Core Concepts
You are supporting a predictive infrastructure project that just entered execution. The project manager says a risk management plan is in place to define how the team will identify, analyze, respond to, and report risks. The sponsor asks for objective evidence that project risks are being tracked and managed over time.
Which artifact best validates this?
Best answer: D
Explanation: The risk management plan explains the approach, roles, and cadence for managing risk, but the day-to-day tracking happens in the risk register. A risk register that is updated over time (with owners, responses, and current status) provides the strongest evidence that risks are actively being monitored and controlled. It shows both what was planned for risk management and what is happening in practice.
The risk management plan’s purpose is to define how risk management will be performed on the project (for example, methodology, roles and responsibilities, probability/impact definitions, reporting, and review cadence). To track risks over time, teams maintain a risk register (risk log) and keep it current during risk reviews.
A well-maintained risk register provides auditable evidence of ongoing risk work, such as:
A calendar entry or a high-level count may indicate activity, but it does not demonstrate that specific risks are being analyzed and managed to closure.
Topic: Domain 4: Business Analysis Frameworks
A hybrid project is implementing a new customer self-service portal. The sponsor says the go-live date is fixed due to a marketing campaign, and the project budget is capped.
During iteration reviews, Sales repeatedly asks to “just add” new features that were not in the approved scope, and the team has started doing small items informally to keep Sales happy. As the business analyst (BA), what should you do to best support scope definition and avoid scope creep while respecting the constraints?
Best answer: A
Explanation: A BA helps prevent scope creep by making scope and requirements explicit, traceable, and governed. The best response is to document requested additions, analyze schedule/budget impacts against the fixed constraints, and route them through the agreed change control/decision process. This preserves transparency and lets the sponsor make informed tradeoffs rather than allowing informal scope growth.
Scope creep happens when work is added without being evaluated and authorized. In a hybrid environment, a BA supports scope definition by eliciting and documenting requirements, clarifying acceptance criteria, maintaining traceability, and ensuring changes follow the agreed governance.
In this scenario, the fixed go-live date and capped budget make “small informal adds” especially risky. The BA should capture each new request as a requirement (or backlog item), assess impacts (schedule, cost, risks, dependencies), and submit it through formal change control so an authorized decision-maker can approve, defer, or trade off other scope. Key takeaway: prevent creep by making changes visible, analyzed, and approved before execution.
Topic: Domain 1: Project Management Fundamentals and Core Concepts
A hybrid project team is struggling to identify solutions for repeated handoff delays between design and development. You plan to run a brainstorming session and then organize ideas using affinity grouping. Before selecting the facilitation approach and materials, what should you ask for or verify FIRST?
Best answer: A
Explanation: Brainstorming and affinity grouping work best when everyone has the same understanding of what problem they are solving and what is in or out of bounds. Verifying the problem statement and scope boundaries ensures the team generates relevant options and can cluster them into actionable themes.
Brainstorming is used to quickly generate a wide set of options, and affinity grouping organizes those options into themes based on natural relationships. To facilitate these tools effectively, the team must start from a shared, well-defined prompt; otherwise, ideas will be scattered, duplicates will increase, and grouping will mix unrelated topics (for example, process issues vs. staffing vs. tooling).
Before the session, confirm:
With a clear prompt and boundaries, you can run brainstorming and then cluster outputs into affinity groups that support follow-up actions.
Topic: Domain 1: Project Management Fundamentals and Core Concepts
You are the project manager on a hybrid software project. Two key team members are in conflict and meetings are becoming unproductive.
Exhibit: Issue log entry (excerpt)
ID: ISS-022
Summary: UX lead and developer arguing in backlog refinement
Impact: Decisions delayed; team hesitant to speak up
Notes: UX lead says "my input is ignored"; developer says "scope keeps shifting"
Observed: Raised voices; interruptions; defensive tone
Owner: Project manager
Status: Open
Which next action best demonstrates emotional intelligence (EQ) to improve communication and manage this conflict?
Best answer: A
Explanation: EQ in conflict management emphasizes self-control, empathy, and skilled communication to understand what is driving the disagreement. The exhibit shows emotional escalation and unmet needs (feeling ignored and perceived shifting scope). Private check-ins followed by a facilitated conversation helps de-escalate and restore constructive dialogue while clarifying underlying concerns.
Emotional intelligence (EQ) is the ability to recognize and manage your own emotions and to recognize and respond effectively to others’ emotions. In the exhibit, the conflict is showing clear emotional cues (raised voices, interruptions, defensiveness) and underlying needs (wanting to be heard; frustration with perceived scope change). An EQ-based next step is to first regulate the situation (calm, respectful tone) and build understanding through empathy and active listening.
A practical approach is:
This improves communication and reduces conflict by making it safe to speak, clarifying expectations, and addressing root causes rather than only the symptoms.
Topic: Domain 3: Agile Frameworks/Methodologies
A company is starting a new product enhancement project using two-week iterations with a distributed team. The project manager’s objective is to enable an adaptive way of working quickly while staying within existing organizational constraints (only company-approved tools may be used and security policies must be followed).
Which option best optimizes fast, compliant adoption of an adaptive approach by leveraging appropriate organizational process assets (OPAs) and enterprise environmental factors (EEFs)?
Best answer: C
Explanation: The best choice uses OPAs (existing agile templates/checklists) to reduce startup time and uses an EEF (the organization’s approved, provisioned tool environment) to stay compliant. Together, these factors directly facilitate an adaptive approach without creating avoidable delays or introducing noncompliant tooling.
OPAs are internal, reusable assets such as policies, procedures, templates, checklists, and lessons learned repositories that help teams execute work consistently and faster. EEFs are conditions outside the project team’s direct control-such as organizational culture, governance constraints, and available infrastructure/tools-that influence how the project can operate.
In this scenario, fast adoption of adaptive delivery is best supported by:
The key takeaway is to tailor agile ways of working by reusing internal assets and working within environmental constraints rather than creating new ones that slow delivery.
Topic: Domain 2: Predictive, Plan-Based Methodologies
A predictive project is in Executing. A previously identified risk (late delivery from a key supplier) occurred, and the team implemented the planned mitigation, but the delivery is still trending two weeks late. During the same status meeting, the procurement lead also identifies a new potential risk: a pending regulation could require additional documentation.
What is the best next step for the project manager?
Best answer: C
Explanation: The project manager should first keep the risk register current by adding the newly identified risk and updating the existing risk entry to reflect that the planned response is not effective. This supports ongoing risk monitoring and provides the documented basis for deciding whether additional responses or formal changes are needed.
In a predictive project, the risk register is updated throughout the project to document newly identified risks and to track each risk’s status, response actions, and response effectiveness. In the scenario, there is (1) a new potential regulation risk that must be recorded and analyzed and (2) an existing supplier-delay risk whose planned mitigation is proving ineffective and therefore should be updated to reflect current conditions (e.g., updated probability/impact, response status, and any needed additional or contingency actions). Once the risk register reflects the latest information, the project team can determine whether a new response plan is required and whether any resulting impacts require formal change control. The key idea is to update the risk register before jumping to rebaselining or escalation.
Topic: Domain 2: Predictive, Plan-Based Methodologies
A predictive project has delivered all scope items, and operations has started using the product. When the project manager initiates closing, the sponsor refuses to sign the project completion document and finance will not release final payment. The sponsor says, “I don’t see documented evidence that acceptance criteria were verified and formally accepted.”
What is the most likely underlying cause of this closing problem?
Best answer: B
Explanation: In predictive projects, closing depends on verifying completion and obtaining formal, documented acceptance of deliverables against agreed acceptance criteria. The sponsor’s specific concern is the absence of evidence that acceptance was verified and approved, which blocks final sign-off and related administrative closure actions like final payment.
A key closing activity in a predictive project is to confirm the work is complete and obtain formal acceptance of the final product, service, or result. This is typically demonstrated through documented verification (e.g., test results, inspection records) and a signed acceptance or completion document from the authorized customer/sponsor. Without that documentation, the organization may be unable to finalize administrative closure steps such as issuing final invoices/payments, completing handover, and formally closing the project or phase. The symptom here (no sign-off and no final payment) directly ties to the stated missing acceptance evidence, making lack of documented formal acceptance the root cause rather than a reporting or communication issue.
Topic: Domain 4: Business Analysis Frameworks
A hybrid project is building an internal HR self-service portal. During sprint 2, the sponsor asks for a dashboard to track PTO usage. The product owner wants the team to start development immediately, but the benefits owner says the dashboard’s expected value and success measures are unclear. The team has limited capacity this sprint and cannot afford rework.
As the project manager, what is the BEST next action to clarify responsibilities and move forward?
Best answer: D
Explanation: The project needs business clarification (value, success measures, and acceptance criteria) before consuming scarce sprint capacity. Those activities align with business analyst responsibilities such as eliciting and analyzing requirements and defining acceptance criteria to reduce rework. The project manager should ensure the right role leads that work and that the team does not commit prematurely.
Business analysts focus on understanding the business problem/opportunity, eliciting and analyzing requirements, and defining clear acceptance criteria and measures of value. Project managers focus on enabling delivery by coordinating work, managing constraints, and ensuring appropriate governance and decision-making.
In this scenario, the dashboard request is not ready because its value and success measures are unclear and capacity is constrained. The best next step is to have the business analyst work with stakeholders to:
Once that analysis is complete, the team can make an informed prioritization and commitment decision with reduced risk of rework.
Topic: Domain 3: Agile Frameworks/Methodologies
You are supporting a Scrum team and reviewing its sprint dashboard.
Exhibit: Sprint dashboard (story points)
Sprint plan (Day 1): 30 points
Burndown (remaining): Day 1=30, Day 5=22, Day 10=12
Last 3 sprint velocities (completed): 28, 26, 27
Which interpretation is best supported by the exhibit?
Best answer: A
Explanation: Velocity is the amount of work completed per iteration, typically measured in story points. The burndown shows how much work remains over time and whether the team is trending to finish the sprint backlog. Here, 12 points remain at the end of the sprint, so completion is 18 points-below the recent average velocity of about 27.
Velocity tracks how many story points a team actually completes in an iteration and is commonly used to forecast how much work the team can likely pull into future sprints based on recent performance. A sprint burndown tracks remaining work each day; a burndown that ends above zero indicates work was not fully completed.
From the exhibit:
A burndown helps visualize progress within the sprint, while velocity supports forecasting across sprints.
Topic: Domain 2: Predictive, Plan-Based Methodologies
You are reviewing a small predictive project schedule to confirm the critical path.
Exhibit: Activity list (durations in days)
ID Dur Predecessor(s)
A 2 -
B 4 A
C 3 A
D 5 B
E 2 C, D
F 1 E
Based on the exhibit, which sequence is the critical path?
Best answer: C
Explanation: The critical path is the longest path through the network considering activity dependencies. Because E cannot start until both C and D finish, the controlling branch into E is the longer one that ends with D. Adding the durations along that branch from start to finish yields the longest total duration.
Critical path method identifies the start-to-finish path with the greatest total duration (and typically zero total float). From the exhibit, E has two predecessors (C and D), so E’s earliest start is controlled by whichever predecessor chain finishes later.
Therefore, the sequence through B and D into E and then F is the critical path; the shorter chain through C has float because it finishes earlier than D.
Topic: Domain 3: Agile Frameworks/Methodologies
A Scrum team says they “do a retrospective every sprint,” but the same problems (unfinished work carrying over and recurring defects) continue for three sprints. As the project practitioner supporting the team, you want to help ensure improvement actions are actually implemented.
What should you ask to verify first before recommending changes?
Best answer: A
Explanation: Retrospectives only drive improvement when the team turns insights into actionable items that are owned, tracked, and revisited. Before changing practices, first confirm whether the team has a concrete mechanism to capture action items and ensure they are carried into and checked during subsequent iterations.
In agile, a retrospective is effective when it produces specific improvement actions and the team inspects progress on those actions in later iterations. If the same issues repeat, the first clarifying check is whether action items are being made visible (for example, in an improvement backlog), assigned to an owner, given a target timeframe, and explicitly reviewed in the next sprint (often during planning and/or in the next retrospective). Without this control loop, “doing retrospectives” can become a discussion ritual with no implementation, so recommending new techniques is premature until the team’s action tracking and follow-up are understood.
Topic: Domain 4: Business Analysis Frameworks
A company is delivering a customer self-service portal using a hybrid approach (a fixed regulatory release date, but features can be delivered iteratively). Stakeholders are challenging why “passwordless login” is scheduled ahead of “chat support,” and you have been asked to communicate the prioritization decision and its rationale.
The current documentation lists the features but does not show how priorities were determined. What should you ask for or obtain FIRST before explaining the prioritization to stakeholders?
Best answer: D
Explanation: To communicate prioritization decisions credibly, you must first confirm the agreed criteria and method used to set priority and where it is recorded. In agile/hybrid environments this is often reflected in backlog ordering and a roadmap/release plan; in predictive contexts it may be in requirements documentation and change control decisions. Without an agreed basis, any explanation is just opinion and will not resolve stakeholder challenges.
Prioritization rationale should be communicated through the artifact that fits the delivery approach (e.g., ordered product backlog and release plan/roadmap in iterative delivery, or prioritized requirements documentation aligned to baselines and approved changes in plan-based work). Before you can explain “why this feature first,” you need the explicit, agreed prioritization criteria and decision method (such as compliance urgency, customer value, risk reduction, dependencies, cost of delay) that the team and stakeholders are using. Once confirmed, you can point to how the chosen criteria drove the ordering and update the appropriate artifact so the rationale is transparent going forward. The key takeaway is that methodology influences both how priorities are set and which artifact is used to communicate them.
Topic: Domain 3: Agile Frameworks/Methodologies
A Scrum team is struggling with too much work started at once, frequent context switching, and unclear status during the sprint. The project manager wants evidence that the team is visualizing workflow and actively managing work in progress during daily coordination.
Which artifact best validates this?
Best answer: B
Explanation: The most direct validation is a task board that displays work items moving through workflow states (for example, To Do/In Progress/Done) and highlights WIP against agreed limits. This provides transparent, real-time evidence of progress and supports decisions to stop starting and start finishing.
In adaptive delivery, a task board (physical or electronic) is a primary information radiator used to visualize workflow and manage work in progress. By showing each work item’s current state and making WIP limits and blockers visible, the team can quickly validate whether work is flowing toward “Done” and adjust daily behaviors (swarming, rebalancing, unblocking) to reduce multitasking and queues.
Evidence on a task board typically includes:
Measures like effort hours or backlog size don’t show flow or WIP control, which is the core problem described.
Use this map after the sample questions to connect individual items to project management fundamentals, predictive planning, agile concepts, business analysis basics, and delivery-process decisions these PM Mastery samples test.
flowchart LR
S1["Project fundamentals scenario"] --> S2
S2["Identify process role artifact or approach"] --> S3
S3["Assess scope schedule cost risk or quality cue"] --> S4
S4["Apply predictive agile or business-analysis concept"] --> S5
S5["Choose best next project action"] --> S6
S6["Document lesson result or update"]
| Cue | What to remember |
|---|---|
| Foundations | Know project, program, portfolio, operations, lifecycle, phase, deliverable, and constraint distinctions. |
| Predictive basics | Scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholders interact. |
| Agile basics | Backlogs, increments, iteration, feedback, and team collaboration support adaptive work. |
| Business analysis | Requirements, acceptance criteria, traceability, and stakeholder needs shape scope. |
| Exam logic | Choose disciplined next steps, not heroic shortcuts or undocumented action. |
If you want concept-first reading before heavier simulator work, use the companion PMI CAPM Study Guide on PMExams.com. Then return here for timed mocks, topic drills, explanations, and the full PM Mastery practice route.
Use these child pages when you want focused PM Mastery practice before returning to mixed sets and timed mocks.