12 real CAPM sample questions, each with a worked explanation and a rationale for every option, right and wrong. No account, no card. This is the reasoning the CAPM tests: knowing why the tempting answer is wrong, not just spotting the right one.
The real CAPM is 150 (135 scored) questions in 180 minutes. For a domain-by-domain breakdown and a study plan, read the CAPM study guide. The full bank has 286 questions.
lock_openFree sampleProject Management Fundamentals and Core Conceptseasy
The Harbourline mobile banking programme has stable, well-understood requirements, a fixed regulatory deadline, and a client who wants the full scope defined and signed off before any build starts. The sponsor asks which development approach best fits these conditions. Which approach should the project manager recommend?
- AA predictive approach, planning scope, schedule, and cost in detail before execution beginscheck_circle Correct
- BAn adaptive approach, so the team can reprioritise the backlog every iteration as feedback arrives
- CAn incremental approach, so a usable subset of features is released at the end of each short cycle
- DA hybrid approach, combining predictive planning with adaptive delivery for the same requirements
A predictive life cycle suits work whose scope and requirements are well understood and fixed before execution begins. A predictive approach front-loads detailed planning of scope, schedule, and cost because the requirements are known and stable, which lets the team commit to a plan and a fixed deadline with confidence.
Why A is correct: Predictive life cycles fit stable, clearly defined requirements planned in full before work starts, which matches the fixed scope, signed-off requirements, and fixed deadline described here.
Why B is wrong: Adaptive approaches suit volatile requirements and frequent change, but this programme has stable, well-understood scope defined up front, so the flexibility adds overhead without benefit.
Why C is wrong: Incremental delivery is tempting because of the fixed deadline, but it is chosen to get working functionality into users' hands early, not because requirements are fully known and fixed at the outset.
Why D is wrong: Hybrid is useful when parts of the work are uncertain and parts are stable, but nothing here is described as uncertain, so blending approaches introduces complexity the situation does not call for.
lock_openFree sampleProject Management Fundamentals and Core Conceptseasy
On the Meridian analytics platform, the team paints a rough version of the whole dashboard first, then repeats the work over several cycles, refining and improving that same product each time based on user feedback until it is polished. Which development approach does this describe?
- AAn incremental approach, delivering a different finished feature slice at the end of each cycle
- BAn iterative approach, repeating cycles that successively refine a single evolving productcheck_circle Correct
- CA predictive approach, executing a single detailed plan produced before the work started
- DA hybrid approach, running predictive and adaptive elements in parallel on the product
Iterative development repeats cycles to refine and improve one evolving product, unlike incremental delivery of separate finished pieces. Iteration improves the correctness of a single product through repeated passes that incorporate feedback, so the same deliverable becomes more complete and accurate each cycle rather than growing by discrete finished chunks.
Why A is wrong: Incremental delivery adds new completed pieces each cycle, but the scenario repeatedly refines one whole product rather than shipping separate finished slices, so this misreads the pattern.
Why B is correct: Iterative development revisits and improves the same product across repeated cycles to increase its correctness, which matches refining the whole dashboard over successive passes.
Why C is wrong: Predictive work follows one up-front plan through to completion, whereas the team here reworks the product across multiple feedback cycles, so it is not predictive.
Why D is wrong: Hybrid mixes distinct approaches for different parts of the work, but this scenario shows one consistent pattern of repeated refinement, so labelling it hybrid is inaccurate.
lock_openFree sampleProject Management Fundamentals and Core Conceptseasy
The Calder logistics project is delivered in a fixed sequence of phases where planning is completed in full and formally approved before any construction work begins, and each phase is finished before the next starts. Which characteristic most accurately describes this life cycle?
- ARequirements are expected to change often, so detailed scope is deferred until each phase begins
- BWorking product is released to users at the end of short cycles for early value
- CScope, schedule, and cost are planned in detail early and executed through sequential phasescheck_circle Correct
- DThe backlog is reprioritised continuously so the team can respond to new information
A predictive life cycle plans scope, schedule, and cost in detail up front and runs through sequential, gated phases. In a predictive life cycle the major planning is completed and baselined before execution, and phases proceed in sequence, so change is managed against a fixed baseline rather than absorbed continuously.
Why A is wrong: Frequent change and deferred scope describe adaptive work, which contradicts the up-front, formally approved planning stated in the scenario.
Why B is wrong: Early releases each cycle describe incremental delivery, but this project runs sequential phases with construction only after planning is approved, not repeated user releases.
Why C is correct: Detailed up-front planning executed through a fixed phase sequence is the defining trait of a predictive life cycle, which matches the completed and approved planning before construction described here.
Why D is wrong: A continuously reprioritised backlog is an adaptive trait, whereas this project fixes and approves the plan before execution, so it does not apply.
lock_openFree sampleBusiness Analysis Frameworksmedium
At the Meridian Loyalty project, a sponsor tells the business analyst that the organisation should build a mobile rewards app because a competitor just launched one. Before any solution is chosen, what should the business analyst do first as part of the needs assessment?
- ADraft the solution requirements for the mobile app so developers can begin estimating the build effort.
- BIdentify and document the underlying business problem or opportunity the organisation is trying to address.check_circle Correct
- CSchedule the competitor's app for a feature-by-feature teardown so the new app can match it exactly.
- DEstimate the project budget and timeline so the sponsor can approve funding at the next steering meeting.
A needs assessment starts by defining the underlying business need, the problem or opportunity, before any solution is selected. The needs assessment exists to establish why change is warranted. Defining the business problem or opportunity first ensures every later decision, including whether an app is even the right solution, traces back to a real organisational gap rather than to a sponsor's assumption.
Why A is wrong: Writing solution requirements assumes the mobile app is the right answer, which skips the needs assessment and commits to a solution that has not yet been justified by a defined business need.
Why B is correct: A needs assessment begins by defining the business need, the actual problem or opportunity, before any solution is considered, so the response is grounded in a real gap rather than a copied competitor feature.
Why C is wrong: Copying a competitor feature by feature is tempting when a sponsor names a rival, but it substitutes imitation for analysis and never establishes whether the organisation shares the same business need.
Why D is wrong: Budget and timeline estimates matter later in the business case, but producing them before the business need is defined prices a solution that has not been shown to address a genuine problem.
lock_openFree sampleBusiness Analysis Frameworksmedium
On the Harbourline billing project, the business analyst is drafting a situation statement to anchor the needs assessment. Which element belongs in a well-formed situation statement?
- AA ranked list of candidate solutions with the recommended option highlighted for the sponsor.
- BThe detailed acceptance criteria that the delivered billing solution will be tested against.
- CA neutral description of the problem or opportunity together with its effect on the organisation.check_circle Correct
- DThe full stakeholder register, including each stakeholder's contact details and reporting line.
A situation statement neutrally describes the problem or opportunity and its impact, without naming a solution. The situation statement frames the need for the whole assessment. By stating the problem or opportunity and its organisational impact without prescribing a fix, it keeps stakeholders aligned on what must be solved before debating how to solve it.
Why A is wrong: Ranking candidate solutions is solution evaluation work, and putting it in the situation statement presumes an answer before the problem itself has been neutrally described.
Why B is wrong: Acceptance criteria describe how a chosen solution will be verified, which is a much later activity and has no place in a statement whose job is to frame the current problem.
Why C is correct: A situation statement objectively states the problem or opportunity and the impact it has, keeping the focus on the need itself and deliberately avoiding any solution language.
Why D is wrong: A stakeholder register is a separate output of stakeholder analysis, and although it is useful, it is not the content of a situation statement, which describes the problem and its impact.
lock_openFree sampleBusiness Analysis Frameworksmedium
The Cascade Warehouse project team has defined the business need and now wants a document that justifies the investment by weighing costs, benefits, and risks so leaders can decide whether to proceed. Which business analysis deliverable meets this purpose?
- AThe requirements traceability matrix, linking each requirement back to its source and forward to a test.
- BThe stakeholder engagement plan, describing how each stakeholder group will be communicated with.
- CThe solution scope statement, listing the capabilities and boundaries of the eventual solution.
- DThe business case, presenting the costs, benefits, and risks of pursuing the identified need.check_circle Correct
The business case justifies pursuing a defined need by presenting its costs, benefits, and risks for a go decision. After the need is defined, the business case is the deliverable that lets leaders decide whether to invest. It consolidates costs, benefits, and risks into one justification, which is why it is produced during the needs assessment rather than after a solution is chosen.
Why A is wrong: A traceability matrix tracks requirements through delivery, which is valuable, but it does not weigh costs, benefits, and risks to support an invest-or-not decision.
Why B is wrong: An engagement plan governs stakeholder communication during delivery and is easy to confuse with early planning artefacts, but it does not justify the investment itself.
Why C is wrong: A solution scope statement defines what a chosen solution will and will not include, so it assumes the go decision has already been made rather than supporting that decision.
Why D is correct: The business case assembles the costs, benefits, and risks of addressing the business need so decision-makers can judge whether the investment is justified before the project is authorised.
lock_openFree sampleAgile Frameworks/Methodologiesmedium
The Meridian mobile-banking team has a signed 40-page requirements document, but during the first two-week iteration the client watches the working login flow and asks for three material changes. The team lead argues that the contract fixes the scope and the changes should wait for a formal change request. Which position best reflects the values of the Agile Manifesto?
- ADefer the changes to a later release, because the signed requirements document is the team's contract and must govern the current iteration.
- BWelcome the client's changes now, because responding to change is valued over following a fixed plan when it delivers a better product.check_circle Correct
- CReject the changes outright, because customer collaboration tends to matter most at the start of the project when the scope is first agreed.
- DAccept the changes only after the client raises a formal written change request through the document-control process.
The Agile Manifesto values responding to change over following a plan when adaptation yields a better outcome for the customer. Agile treats requirements as emergent; feedback from a working increment is a signal to adapt, and the Manifesto explicitly ranks responding to change above following a fixed plan, which is why welcoming the change is the best position.
Why A is wrong: This treats comprehensive documentation and the plan as fixed authority, which inverts the Manifesto value that prioritises responding to change, so it is wrong.
Why B is correct: The Manifesto value 'responding to change over following a plan' supports adapting to the emerging requirement rather than deferring to the original scope document, so this is correct.
Why C is wrong: It is tempting because early scoping does matter, but the Manifesto values ongoing customer collaboration throughout delivery, not just at kickoff, so this is wrong.
Why D is wrong: A heavyweight change-control gate favours process and documentation over individuals and interactions and responding to change, so although it feels disciplined it conflicts with the values here.
lock_openFree sampleAgile Frameworks/Methodologiesmedium
On the Aurora analytics project the scrum master notices developers are blocked waiting for test-environment access and are unsure how to split a large story. A junior team member asks the scrum master to simply assign the remaining tasks and decide the split. Consistent with the agile mindset, how should the scrum master respond?
- AAssign each developer a fixed task list and dictate the story split, since a scrum master is accountable for the team hitting the sprint target.
- BEscalate both issues to the functional manager so that the manager can allocate the tasks and approve the split.
- CRemove the environment-access impediment and coach the team to split the story themselves, serving the team rather than directing it.check_circle Correct
- DTell the team to resolve the access problem on their own while the scrum master decides how the story is broken down.
A scrum master acts as a servant leader who removes impediments and coaches self-organisation rather than assigning work. Servant leadership means the scrum master serves the team by clearing obstacles and building the team's capability to organise its own work, so the correct action pairs impediment removal with coaching, not directive task assignment.
Why A is wrong: This casts the scrum master as a command-and-control boss assigning work, which contradicts the self-organising, servant-leadership model, so it is wrong.
Why B is wrong: Handing decisions to a functional manager is tempting for speed but undermines team self-management and the scrum master's facilitation role, so it is wrong.
Why C is correct: Clearing impediments and coaching self-organisation is the servant-leader role of the scrum master, which is why this is the correct response.
Why D is wrong: This ignores the impediment the scrum master should remove and takes over a decision the team should own, mixing up the responsibilities on both counts, so it is wrong.
lock_openFree sampleAgile Frameworks/Methodologiesmedium
The Cobalt e-commerce team runs two-week iterations, and at the end of each one it demonstrates a small but usable increment to stakeholders and adjusts the plan based on what it learns. A new sponsor asks why the team does not simply build the whole system and deliver it once at the end. Which principle of the Agile Manifesto best explains the team's approach?
- ABuilding projects around motivated individuals and giving them the environment and support they need to get the job done.
- BEnsuring that the sponsors, developers, and users can maintain a constant pace of work indefinitely throughout the project.
- CFront-loading the most detailed design work so the full solution can be released in a single planned handover.
- DDelivering working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.check_circle Correct
Frequent delivery of working software in short timescales is the Agile Manifesto principle behind iterative incremental delivery. Delivering usable increments every couple of weeks lets the team gather feedback and adapt, and the Manifesto principle favouring frequent delivery of working software on the shorter timescale is what underpins this iterative pattern.
Why A is wrong: This is a genuine Manifesto principle about people, but it addresses team environment rather than why the team delivers in short increments, so it does not best explain the approach.
Why B is wrong: Sustainable pace is a real principle, but it concerns workload rhythm, not the reason for frequent incremental delivery, so it is the wrong fit here.
Why C is wrong: A single big-bang release with heavy up-front design is a predictive practice and is not an Agile Manifesto principle at all, so it is wrong.
Why D is correct: Frequent delivery of working software in short timescales is a named Agile Manifesto principle and directly explains the iterative increments, so this is correct.
lock_openFree samplePredictive, Plan-Based Methodologieshard
A small project network has five activities. Activity A (3 days) and Activity B (6 days) both start the project. Activity C (8 days) follows A. Activity D (4 days) follows B. Activity E (5 days) starts only after both C and D finish, and E ends the project. Which path is the project's critical path?
- AA to C to E, with a total duration of 16 dayscheck_circle Correct
- BB to D to E, with a total duration of 15 days
- CA to C to E, with a total duration of 11 days
- DB to D to E, with a total duration of 18 days
The critical path is the longest continuous path through the network, which determines the earliest possible project finish. Adding activity durations along each complete path gives A to C to E at 16 days and B to D to E at 15 days. The longest of these, 16 days, is the critical path because any delay to its activities delays the whole project.
Why A is correct: The critical path is the longest continuous path through the network. A to C to E sums to 3 plus 8 plus 5, which is 16 days, longer than the only other path B to D to E at 15 days, so it sets the earliest project finish and its activities have zero total float.
Why B is wrong: B to D to E is the near-critical path at 15 days and carries only 1 day of total float. It is tempting because it starts with the longest single activity, B at 6 days, but a longer path exists, so it is not critical.
Why C is wrong: This correctly names the longest path but miscalculates its length, most likely by dropping activity E from the sum. The path A to C to E actually totals 16 days, not 11, so the duration stated here is wrong.
Why D is wrong: This selects the near-critical path and also overstates its length, probably by adding an activity that is not on it. B to D to E totals 15 days, and in any case it is not the longest path, so it is not the critical path.
lock_openFree samplePredictive, Plan-Based Methodologieshard
A scheduler has completed both the forward pass and the backward pass on a predictive project schedule and now wants to explain to the team what the critical path actually represents. Which statement correctly describes the critical path?
- AIt is the sequence of activities with the greatest total float, which gives the schedule its maximum flexibility.
- BIt is the longest path through the network, and its activities have zero total float.check_circle Correct
- CIt is the path that contains the single longest-duration activity in the whole schedule.
- DIt is the shortest path through the network, along which any delay is absorbed by available float.
Critical path activities lie on the longest network path and carry zero total float, so any delay to them delays the project. The forward and backward passes reveal that the longest path has identical early and late dates, producing zero total float. That absence of slack is what makes those activities critical and defines the project's shortest possible duration.
Why A is wrong: This inverts the concept. Activities with large total float can be delayed without affecting the finish date, so they are the least constraining, not the critical path. Critical activities have the least float, not the most.
Why B is correct: The critical path is the longest duration path from start to finish, so it drives the earliest completion date. Because there is no slack anywhere along it, each of its activities has zero total float, meaning any delay pushes the project end out.
Why C is wrong: A long individual activity may sit on a short path, while many shorter activities in sequence can form a longer path. Critical path length comes from the sum along a path, not from any one activity, so this is a common trap.
Why D is wrong: This reverses the definition. The shortest path has the most slack and delays there are indeed absorbed by float, which is exactly why it is not critical. The critical path is the longest path and has no float to absorb delay.
lock_openFree samplePredictive, Plan-Based Methodologieshard
Activity Q has an early finish on day 12. Its only successor, activity R, has an early start on day 15. Activity Q does not lie on the critical path, and the backward pass gives Q a late finish on day 18. Based on these figures, what are Q's free float and total float?
- AFree float of 6 days and total float of 3 days
- BFree float of 3 days and total float of 3 days
- CFree float of 3 days and total float of 6 dayscheck_circle Correct
- DFree float of 0 days and total float of 6 days
Free float uses a successor's early start while total float uses an activity's own late finish, so the two values often differ. Free float equals the earliest start of the successor minus the early finish of the activity, 15 minus 12 equals 3. Total float equals the activity's late finish minus its early finish, 18 minus 12 equals 6. Different reference points produce different amounts of slack.
Why A is wrong: This swaps the two values. Free float looks at the successor's early start and equals 3 days, while total float uses the late finish and equals 6 days. The larger number is total float, so the figures are reversed here.
Why B is wrong: Treating free float and total float as equal is a frequent error. They coincide only when an activity's delay would immediately push its successor, which is not the case here, so the two values differ.
Why C is correct: Free float is the successor's early start minus Q's early finish, 15 minus 12, giving 3 days. Total float is Q's late finish minus its early finish, 18 minus 12, giving 6 days. The two measures answer different questions and correctly differ here.
Why D is wrong: Assuming free float is zero because Q is off the critical path is wrong. Free float is the successor early start minus Q's early finish, 15 minus 12, which is 3 days, not zero.
Examworthy is not affiliated with or endorsed by PMI. All questions are original, blueprint-aligned practice material. We never reproduce live exam items. CAPM and related marks belong to their respective owners.
