PMP practice questions, with answers.
10 questions from the course’s free lessons, with no account needed. Pick your answer, then open the explanation. Every question in the course explains the right answer and why each wrong one is wrong.
Question 1A six-person team is joined by two more people. By how many does the number of two-way communication channels increase?
- 2
- 28
- 11
- 13
Show answer
Answer: D. Six people give 6 × 5 ÷ 2 = 15 channels; eight give 8 × 7 ÷ 2 = 28. The increase is 28 − 15 = 13, which is more than six times the headcount added.
Exam trap: Read whether the question asks for the total or the increase. Both numbers are available and only one is the answer.
Question 2A project manager responds to rising coordination overhead on a nine-person team by adding a second daily stand-up and a shared mailbox everyone monitors. Overhead increases further. What did the response overlook?
- Nine people is beyond the size at which any coordination mechanism helps.
- Both additions maintain every existing path rather than reducing how many need maintaining.
- Stand-ups are only effective for teams of seven or fewer.
- A shared mailbox should have replaced the stand-ups rather than supplementing them.
Show answer
Answer: B. Nine people carry 36 potential paths. Another meeting and another channel add ways to traverse those paths without reducing their number, so the surface stays the same and the time spent on it grows.
Exam trap: Adding a channel never reduces the coordination surface. Partitioning the work and defining the interface does.
Question 3A project acts on eleven of nineteen suggestions from a user group but never tells the group which were adopted. Submissions in the following round drop by two thirds. What best explains the drop?
- The second round was probably scheduled too soon after the first.
- Eleven of nineteen is too low an adoption rate to sustain engagement.
- The group had exhausted its suggestions in the first round.
- The group cannot distinguish acted-upon suggestions from ignored ones, so contributing appears futile.
Show answer
Answer: D. Acting is invisible without reporting back. From the group's side, a round where eleven suggestions were adopted silently looks identical to one where none were, and they respond to what they can observe.
Exam trap: Acting on feedback and closing the loop are separate steps. Doing the first without the second produces the same behaviour as doing neither.
Question 4During a requirements session a business analyst nods frequently, takes detailed notes, and asks two clarifying questions. Which additional behaviour would give the strongest evidence that he has understood the stakeholder correctly?
- Asking further clarifying questions until the stakeholder has nothing to add.
- Summarising the requirement back and asking the stakeholder to confirm or correct it.
- Recording the session so the wording can be checked later.
- Circulating his notes after the session for review.
Show answer
Answer: B. Restating is falsifiable in the room. The stakeholder either confirms the summary or corrects it, and either outcome is information he did not have a moment earlier.
Exam trap: Attention and comprehension look identical from outside. Only restatement makes the difference visible while it can still be corrected.
Question 5A report states that 90% of planned tasks are complete. The steering group asks what that means for the launch date. Why can the report not answer the question?
- Launch dates cannot be forecast from progress data in any case.
- Percentage complete should be weighted by effort rather than by task count.
- It counts tasks without saying what the remaining 10% contains or what depends on it.
- The reporting period is too long to support a date forecast.
Show answer
Answer: C. Ninety per cent is compatible with being finished next week or next quarter, depending entirely on whether the remaining tasks are cosmetic or the integration everything else waits on. The figure describes activity and omits the dependency.
Exam trap: Percentage complete is the most quoted and least informative status figure. What remains, and what waits on it, is the answer to almost every date question.
Question 6A delivery manager doubles a team's developers after complaints about slow delivery. Three months later output is unchanged and the queue of finished-but-unreviewed changes has grown. One senior engineer performs all reviews. What went wrong?
- Review is being performed too thoroughly and the standard should be relaxed.
- Capacity was added upstream of the constraint, so more work now waits at the same point.
- Doubling a team at once is too large a change to absorb.
- The new developers have not yet reached full productivity on the codebase.
Show answer
Answer: B. Review limits the system, so producing more changes only lengthens the queue in front of it. Output rises when review capacity rises, or when more people are qualified to review.
Exam trap: Look for what the work is waiting on. A queue growing at one point names the constraint, and adding capacity anywhere else feeds it.
Question 7A schedule assumes any of six engineers can perform a specialised migration task, and plans on the team's average productivity. Only two have done this kind of migration. What is the effect on the plan?
- It overstates total team capacity by two thirds.
- It has no practical effect, since the other four can be trained during the task.
- It hides a dependency on two named people that levelling will not respect.
- It understates the duration by exactly the ratio of experienced to total staff.
Show answer
Answer: C. Planning on an interchangeable pool conceals that this task actually requires one of two individuals. Levelling algorithms and reassignment decisions will treat the six as equivalent and produce a schedule nobody can staff.
Exam trap: Where a task genuinely needs a named individual, say so. A pool assumption produces a plan that resource levelling will happily break.
Question 8A team completes 10 items a fortnight and holds an average of 20 items in progress. A second team completes 10 a fortnight with 5 in progress. What differs between them?
- The first team is four times more productive per person.
- The first team's items take four times as long to emerge, at identical throughput.
- Nothing meaningful; both deliver the same number of items.
- The second team has spare capacity that could be used to raise throughput.
Show answer
Answer: B. Average time in progress equals work in progress divided by completion rate: 20/10 = 2 fortnights against 5/10 = half a fortnight. Same output, four times the wait per item.
Exam trap: Equal throughput with different work in progress is a cycle-time question, not a productivity one.
Question 9Resource demand exceeds supply in two overlapping months, and the project's finish date is contractually fixed. Which technique applies, and what is its limitation here?
- Either, since both preserve the finish date by definition.
- Smoothing, which redistributes work within existing float and fails if float is insufficient.
- Levelling, which resolves the conflict by extending the finish date.
- Neither, since a fixed finish date rules out schedule adjustment entirely.
Show answer
Answer: B. A fixed date rules out levelling, leaving smoothing — and smoothing can only move work into float that already exists. Where the overload sits on the critical path there is no float, and the conflict has to be resolved by adding capacity or reducing scope instead.
Exam trap: A fixed finish date is the signal that levelling is unavailable. Smoothing is what remains, and it runs out when float does.
Question 10Building a fraud-scoring engine internally would cost more than licensing one. The organisation expects fraud scoring to become central to how it competes over the next decade. What does this change about the make-or-buy decision?
- It settles the decision as build, since core capabilities are never licensed.
- It shifts the decision to procurement, as the licensing arrangement is now long-term.
- Nothing — cost comparison is the basis for make-or-buy decisions.
- Strategic control becomes a weighted factor, since the capability will outlive the project.
Show answer
Answer: D. A capability the organisation intends to compete on is a different decision from a one-off need. The extra build cost may buy control, adaptability, and freedom from a supplier's roadmap, and that has to be weighed rather than assumed either way.
Exam trap: Make-or-buy is not a spreadsheet comparison. Whether the capability should remain in the organisation afterwards frequently outweighs the price difference.
Keep going with the free preview.
Create a free account to study the complete free lessons, answer more questions and take a short preview test. No card, no time limit.