PMP Practice Test

What the PMP exam covers — and how to study it

The People domain rewards a servant-leadership mindset. Again and again the exam asks what a project manager should do when a team hits friction, and the 'best' answer is usually the one that empowers the team, removes their impediments, and addresses the root cause directly rather than escalating, avoiding, or dictating. Know the classic conflict-resolution modes (collaborating/problem-solving is generally preferred; forcing and avoiding are usually wrong), Tuckman's team stages (forming, storming, norming, performing, adjourning), and the motivation theories (McGregor's Theory X/Y, Maslow, Herzberg's hygiene factors vs. motivators). When two answers both sound reasonable, favor the one that talks with the people involved and builds consensus over the one that simply enforces a rule.

The Process domain is the technical heart of the exam. Understand the difference between predictive, agile, and hybrid life cycles and — crucially — when each fits: stable, well-defined scope favors predictive, while uncertain or evolving requirements favor an adaptive, iterative approach. Learn the meaning of the earned-value indicators conceptually (a cost variance or CPI below plan means over budget; a schedule variance or SPI below plan means behind schedule) without memorizing dollar figures — and practice reading them off a small table, because the current exam asks you to interpret charts and data rather than just recall a definition. Know the principle that quality is planned in and prevention beats inspection, how contract types shift risk between buyer and seller (fixed-price puts risk on the seller; cost-reimbursable puts more on the buyer), and how project finance works in practice: analyzing funding needs, quantifying contingency allocations, tracking spend across the life cycle, and managing reserves. On the agile side, be fluent in the ceremonies (sprint planning, daily standup, review, retrospective), the roles (product owner, scrum master, development team), and tools like the backlog and WIP limits.

The Business Environment domain is no longer the afterthought it once was. At 26% it is now more than a quarter of the exam, and it absorbed some of the most heavily tested material that used to sit in Process — so if you are studying from older material, this is where you are most likely to be under-prepared. Know the risk response strategies for threats (avoid, transfer, mitigate, accept) and for opportunities (exploit, share, enhance, accept), how a risk register and probability-impact analysis drive those choices, and the moment a risk stops being a risk and becomes an issue you have to work. Know the change control path — proposed change, impact analysis, decision, communication, then updated documentation — while remembering that in an adaptive context the same scope change may be an ordinary backlog conversation. Beyond that, expect governance (structure, escalation paths and thresholds, success metrics), compliance (identifying which requirements apply, classifying them, and the consequences of ignoring them), continuous improvement through lessons learned and updated organizational process assets, and external shifts — regulatory, technological, geopolitical, market — that force you to re-prioritize scope or backlog. Keep the big picture in mind: a project exists to deliver business value, not just to finish tasks, and value is measured after delivery. Distinguish a project from a program and a portfolio, know the supporting role of a PMO, and be ready to apply the PMI Code of Ethics — responsibility, respect, fairness, and honesty — which usually points to the transparent, accountable answer even when it is not the easiest one.

Preparing for the content is only half the work; the other half is learning how the questions are built. Almost every item is situational — a short scenario, then a question asking what the project manager should do — and typically more than one option is a reasonable thing to do eventually. The discriminator is the qualifier: first, next, best, or most appropriate. Read for it, then locate yourself in the story, because an answer that is right later is wrong now. A reliable habit is to understand the problem before acting on it: when a scenario presents a surprise, the credited response usually involves gathering the missing information, consulting the plan, or talking to the person closest to the issue, rather than immediately escalating to a sponsor, changing the baseline, or adding resources. Watch for the life cycle the scenario implies, since the same situation resolves differently in a predictive and an adaptive context — a scope change is a change request in one and an ordinary backlog conversation in the other. The current exam also changes the shape of that reading. Some items arrive as a case or scenario set — one detailed situation, sometimes with a chart, followed by several questions that build on it — and others are graphic-based, handing you a chart or diagram to interpret before you can answer at all. Practice pulling the decision-relevant facts out of a table or figure quickly: the reasoning is unchanged, but now you have to do the reading first, and under time pressure that is a separate skill. Above all, answer as a project manager who is accountable for the outcome, empowers the team, communicates proactively, and follows the process that the project has already agreed to.