PMP domain - 50% of the exam

Process

Process is 50% of the PMP exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

148
Practice questions
4
Objectives
74
Medium
74
Hard

Where people go wrong

  • Acting on a variance before finding its cause

    The wrong answers respond to a poor performance index with an action: adding resources, crashing the schedule, cutting scope, requesting more budget or re-baselining. Each treats a symptom before anyone knows what is driving it. Earned value indices show that a variance exists, not why, and a favourable cost index does not offset a poor schedule index. The correct first step is variance analysis, finding which work packages and root causes sit behind the variance, so that any later corrective action fits the real cause.

    See it in a sample question
  • Deciding on out-of-scope work before change control

    The wrong answers decide on a request outside the scope baseline without assessing it: keeping a helpful feature already built, acting on a sponsor's verbal request, updating the baseline to match the work, or refusing the request outright. A request, even from the sponsor and even a small one, is not an approved change, and it is not grounds for a flat refusal either. The correct answer records it as a change request and assesses the impact on scope, schedule, cost and risk through integrated change control before any decision.

    See it in a sample question
  • Inspecting for defects instead of preventing them

    When the same defect keeps recurring, the wrong answers add more inspectors, larger samples, faster rework or looser tolerances. Inspection finds defects only after the units are built, and rework repairs them one at a time, so the cost and delay continue. Prevention over inspection means analysing the process, finding the root cause and correcting it upstream, so the defect is not produced at all. Cost of quality points the same way: prevention is cheaper than repeated appraisal and the internal failure cost of rework.

    See it in a sample question
  • Confusing Control Quality with Validate Scope

    The wrong answers swap the two processes. Control Quality checks internally that a deliverable is correct against the requirements and produces verified deliverables. Validate Scope is the customer's formal acceptance of a deliverable that has already been verified. Wrong options treat acceptance as another correctness check, or seek customer sign-off on a module that has not yet been tested internally. The order is verify first, then validate.

    See it in a sample question
  • Mixing up residual and secondary risk

    The wrong answers swap risk-register terms for what follows a response. A residual risk is the exposure left over from the original threat after the planned response has been carried out. A secondary risk is a new risk created by implementing the response, such as a subcontractor's insolvency or a customs delay after work is transferred. A trigger is an early warning sign, and an issue is a risk that has already occurred.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleProcesshard

A predictive infrastructure project has a budget at completion (BAC) of GBP 800,000. At the current status date the planned value (PV) is GBP 300,000, the earned value (EV) is GBP 240,000, and the actual cost (AC) is GBP 320,000. The project manager has just calculated a cost performance index of 0.75 and a schedule performance index of 0.80. What should the project manager do FIRST?

  • ASubmit a change request for an extra GBP 266,667 to fund the forecast overrun and carry on with the plan unchanged.
  • BInvestigate the root causes of the cost and schedule variances before recommending any corrective action. Correct
  • CCrash the critical path by adding resources so that the schedule performance index is brought back up to 1.0.
  • DRe-baseline the schedule and budget so that future performance is measured against more achievable targets.
Unfavourable earned value indices call for variance root-cause analysis before any corrective action is chosen. A cost performance index of 0.75 and schedule performance index of 0.80 confirm the project is over budget and behind schedule, but the indices are diagnostic signals only. Acting before analysing the causes commits resources without knowing whether they address the real driver of the variance.

Why A is wrong: The forecast overrun figure is plausible because BAC divided by the cost performance index gives an estimate at completion of about GBP 1,066,667, but throwing budget at the problem before understanding its cause treats a symptom and is premature.

Why B is correct: Earned value indices signal that variances exist but not why; the correct first step is variance analysis to find the drivers, so that any later corrective action addresses the real cause rather than a symptom.

Why C is wrong: Crashing looks responsive to the poor schedule index, yet applying a corrective action before diagnosing why work is behind risks spending money on the wrong problem and worsening the cost overrun.

Why D is wrong: Re-baselining seems to restore control, but changing the baseline to hide a variance masks the problem and is a last resort reserved for approved changes, not an opening response to unexplained slippage.

Free sampleProcesshard

During execution of a hybrid project a developer adds an extra data-export feature that a stakeholder had requested informally, reasoning that it was quick and helpful. Control quality confirms the feature works, but it was never part of the approved scope baseline. What should the project manager do FIRST?

  • AAssess the impact of the change and route it through integrated change control before deciding whether to keep it. Correct
  • BAccept the feature into the product because it is already built, functions correctly, and pleased the stakeholder who wanted it.
  • CRemove the feature straight away so the delivered product stays strictly within the boundaries of the current scope baseline.
  • DWarn the developer that adding unrequested work is misconduct and record the incident in their performance review.
Unplanned scope additions must pass through integrated change control before being accepted or rejected. A change to the approved scope baseline is governed by integrated change control regardless of whether the work is already complete or well intentioned. Assessing impact and seeking a decision through that process is what distinguishes controlled change from scope creep.

Why A is correct: Any change to the scope baseline, even a helpful one already built, must be evaluated for its impact and approved or rejected through integrated change control before it becomes part of the product.

Why B is wrong: Keeping working functionality feels efficient, but admitting unapproved work without assessing its effect is scope creep and bypasses the change control the baseline exists to protect.

Why C is wrong: Protecting the baseline is a valid instinct, but discarding the work before evaluating its impact and value is as premature as accepting it, and may throw away something worth formally approving.

Why D is wrong: Undisciplined scope changes are a real concern, but leading with blame is a command-and-control response that ignores the immediate decision of what to do about the feature itself.

Free sampleProcesshard

On a predictive manufacturing project, control quality has caught the same defect in three consecutive production batches, each time after the units were built, and the resulting rework is consuming schedule and cost. The project manager wants to stop the defect recurring rather than keep detecting it late. Which action best reflects sound quality management here?

  • AIncrease the frequency and sample size of final inspections so more defective units are caught before shipping.
  • BInvestigate the process to find and remove the root cause so the defect is prevented before units are built. Correct
  • CWiden the acceptance tolerances so the affected units pass the existing quality checks without any rework.
  • DEscalate the defect to the sponsor and pause production until senior management decides how to proceed.
Sound quality management prevents defects by removing their root cause rather than relying on more inspection after the fact. Prevention keeps errors out of the process and is cheaper than inspection, which only detects defects after they are produced, so eliminating the root cause is the sound quality response to recurring rework.

Why A is wrong: More inspection is tempting because it catches defects, but inspection detects problems only after they occur and does not prevent them, so the costly rework continues.

Why B is correct: Quality management favours prevention over inspection; finding and eliminating the root cause stops the defect being produced at all, cutting the recurring rework, cost, and schedule impact.

Why C is wrong: Relaxing tolerances is tempting as a quick fix, but it lowers the agreed quality standard instead of solving the problem and risks non-conforming product reaching the customer.

Why D is wrong: Escalating and pausing may feel decisive, but the cause sits within the team's own process to fix, so halting production and escalating before any root-cause analysis is disproportionate.

Free sampleProcesshard

A software module has finished internal testing, and control quality has confirmed it meets every documented requirement without defects. The project manager now arranges a session where the client works through the module against the acceptance criteria and formally signs off that it is what they wanted. Which process is the project manager carrying out in that session, and why is it distinct from the testing already done?

  • AControl quality, because the session re-checks the module for correctness against the technical requirements before release.
  • BControl quality, because obtaining a signature confirms the deliverable conforms to the organisation's quality standards.
  • CValidate scope, because the session identifies remaining defects in the module so the team can correct them before delivery.
  • DValidate scope, because the client formally accepts the completed deliverable, which is separate from the internal correctness check. Correct
Separate validate scope, formal customer acceptance of deliverables, from control quality, the internal check for correctness. Validate scope formalises customer acceptance of completed deliverables and is concerned with whether the customer agrees the work is done, while control quality checks the deliverable for correctness and conformance to requirements. Control quality is normally performed first, feeding accepted-as-correct deliverables into validate scope.

Why A is wrong: Control quality verifies correctness against requirements and was already completed. It is tempting because both processes examine the deliverable, but a client sign-off is about acceptance, not another correctness check, so this is validate scope.

Why B is wrong: Conformance to internal quality standards is the concern of control quality, which is already done. A customer signature records acceptance of the deliverable rather than an internal conformance verdict, so the process here is validate scope.

Why C is wrong: The validate scope label is right but the reason is wrong. Finding and fixing defects is the purpose of control quality; validate scope concerns formal customer acceptance, not defect detection, so this rationale misstates the process.

Why D is correct: Validate scope is the process of formalising customer acceptance of completed deliverables. It is distinct from control quality, which checks correctness internally; here the client is accepting the deliverable, not testing it.

Free sampleProcesshard

A predictive data-centre migration project logged a threat that a legacy database might corrupt records during cut-over. The team carried out its agreed mitigation, adding automated validation checks, and afterwards a small chance of minor corruption still remains. How should the project manager classify the exposure that is left once the planned response has been executed?

  • AA residual risk, being the exposure that remains after the planned response has been implemented. Correct
  • BA secondary risk, since it continues to sit against the same activity in the risk register.
  • CA trigger condition, because it warns the team that the mitigation may not have fully worked.
  • DA fallback risk, given that the team may still need a backup plan if corruption occurs.
Residual risk is the exposure that remains after a planned risk response has been implemented. A response reduces but rarely eliminates a threat; the exposure still present after the response has been executed is termed residual risk and is tracked so the team can judge whether it is within tolerance.

Why A is correct: Correct, because residual risk is precisely the exposure that persists once a chosen response has been carried out and cannot be economically reduced further.

Why B is wrong: Tempting because both terms relate to risk responses, but a secondary risk is a brand-new risk created by implementing a response, not the leftover portion of the original threat.

Why C is wrong: Tempting as it sounds like ongoing monitoring, but a trigger is an early warning sign that a risk is about to occur, not the remaining exposure itself.

Why D is wrong: Tempting because backup plans exist, but there is no risk category called a fallback risk; a fallback plan is a type of response, not a name for the remaining exposure.

Other domains in this exam

See also the PMP cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by PMI. Original, blueprint-aligned practice material only.