Worth 41% of the PMI PMP (PMP) exam. CertClue has 369 questions on this objective.
EVM formula questions are some of the most reliably scored items on the exam if you know exactly what each formula measures and what a result above or below the neutral point means.
Exam tip. On formula questions, write out PV, EV, and AC for the scenario first, then plug into the formula; do not try to recall the answer from memory alone since a single wrong sign flips the interpretation.
Procurement questions often hinge on knowing which party bears the most risk under a given contract type, since that risk allocation is the entire reason different contract types exist.
Exam tip. When scope is well defined, expect fixed price contracts; when scope is uncertain or the work is exploratory, expect cost-reimbursable; T&M fills small, short-duration gaps.
Threats and opportunities are two sides of the same risk coin, and PMI expects you to know that each threat strategy has a mirrored opportunity strategy, with accept being the one strategy both sides share.
Exam tip. Accept is the only response strategy common to both threats and opportunities; every other strategy has a distinct threat version and opportunity version that mirror each other.
The exam expects you to pick a life cycle from evidence in the stem rather than from preference. The deciding factors are how well the requirements are understood, how likely they are to change, how often the customer can give feedback, and whether partial delivery has value. Hybrid is not a compromise for the indecisive; it is the correct answer when different parts of one project genuinely sit at different points on that scale.
Exam tip. If a stem mentions a regulator, a fixed-price contract or a hardware dependency, some part of the answer will be predictive.
When a stem says the project is behind and the end date cannot move, the exam is testing whether you know that both compression techniques have a price and neither changes scope. Crashing costs money. Fast tracking costs risk and usually rework. Neither is applied to activities off the critical path, because shortening those changes nothing.
Exam tip. Cost is not a constraint in the stem means crashing. Cost is fixed but some risk is acceptable means fast tracking.
Change questions are almost always about sequence. The single most common wrong answer is implementing a change because the requester is senior or the change is small. The project manager's job on receiving a request is to assess its impact across all constraints, then put it through the agreed process, and only then act on the decision.
Exam tip. Any option where the project manager implements first and informs later is wrong, however small or urgent the change appears.
Quality questions punish imprecise vocabulary more than any other area. Prevention and inspection, precision and accuracy, assurance and control, grade and quality are four pairs that appear repeatedly, and each pair contains one term candidates reach for by habit and one the stem is actually describing.
Exam tip. A stem describing a cheap product that works exactly as specified is describing low grade and acceptable quality, not a quality problem.
Free, with the answer and the reasoning. No account needed.
1. The Orbit Health development team automates its build, test, and deployment pipeline so that every approved code change can be released to production quickly and reliably, reducing batch size and integration risk. From a project management perspective, what is the primary benefit of this continuous delivery practice?
Continuous delivery reduces batch size and automates the release pipeline, which lowers the risk and cost associated with large, infrequent releases while enabling faster feedback loops, matching the described benefit. Option A overstates what pipeline automation does: shifting some testing earlier in the pipeline is a real practice, but it does not remove the ongoing need for manual testing on higher-risk changes. Option B overstates the reliability effect of the practice; smaller, more frequent releases lower risk, but they do not remove the need to keep monitoring production for defects. Option C confuses a technical delivery practice with a separate project management activity: automating releases does not update or replace the schedule baseline, which the project manager still maintains and reports against.
2. A program is in early initiation and only the next few months of work are well understood, while later phases depend on decisions not yet made. Which planning technique lets the team plan near-term work in detail while leaving far-term work at a summary level until more information becomes available?
Rolling wave planning is an iterative approach where near-term work is planned in detail and future work is planned at a higher summary level until it becomes clearer. Option A describes elaborating everything simultaneously, which contradicts the wave-by-wave nature of the technique. Option B describes critical chain scheduling, which addresses resource constraints and buffers rather than the level of planning detail over time. Option D describes fast tracking, which overlaps activities to compress schedule and is unrelated to progressively detailing future work.
3. An organization states that it is generally willing to pursue projects with schedule uncertainty, but it will not accept any project with more than a 15 percent chance of missing a regulatory deadline. Which two concepts are being described, in order?
The organization's general willingness to pursue schedule uncertainty describes its risk appetite, a broad, qualitative attitude toward risk taking, while the specific 15 percent limit that cannot be exceeded describes a risk threshold, a measurable point at which risk becomes unacceptable and triggers action. Options A and D are wrong because they reverse or misplace the order; threshold is the measurable trigger point, not the general willingness described first. Option C is wrong because risk tolerance describes the acceptable range of variation around an objective, a related but different concept from the broad general willingness described in the first part of the statement.
4. During sprint execution, the product owner asks the development team to add a new feature that is not part of the current sprint backlog, insisting it is urgent. What should the team do?
Agile frameworks protect the sprint scope from disruption once a sprint has started, so the team should educate the product owner on the impact and route new, non-emergency requests through backlog refinement for proper prioritization against other work. Adding the feature immediately undermines the sprint commitment and team focus. Flatly refusing to discuss it is dismissive rather than collaborative. Unilaterally removing scope without involving the product owner bypasses the person who owns backlog prioritization.
The full PMI PMP bank, the study notes behind these summaries, and a readiness score that tells you which objective to revise next. Free, no paid tier.
Take the free PMI PMP practice test