PMP Process: 737 practice questions
7-day money-back guarantee — full refund within 7 days of purchase if you've completed under 20% of the questions. See pricing →
Certifications Tools Flashcards Career Paths Exam Guides Blog Pricing For Teams About
Try 20 questions free →

PMP Process: 737 practice questions

PMP 737 questions 12 shown free

12 of the 737 Process questions in the Certsqill PMP bank, shown in full below. Each one carries an explanation for every option, not just the correct one — the wrong answers are where the marks go.

Preparing for PMP? Take the free 5-min readiness check →

1. Reorder software work and resolve the interface dependency: What should the project manager do next?

Medium
A renewable-energy installation uses adaptive delivery for monitoring software while construction follows fixed permits and engineering dependencies. The team has completed initial analysis of the next release. The product representative may reorder the software backlog, and the electrical lead owns resolution of the interface dependency. The permit sequence and safety testing remain fixed. Exhibit: software backlog—reorderable; permit inspections—fixed dates; interface specification—unresolved; safety testing—mandatory before field use. What should the project manager do next?
  1. Replace the adaptive software approach with a predictive schedule covering all remaining installation activities.
    The unresolved interface does not justify abandoning adaptive software delivery or imposing one lifecycle on the project.
  2. Authorize the dashboard feature first and defer interface clarification until field testing is complete.
    Advancing integration with a known unresolved dependency risks rework and could interfere with mandatory safety testing.
  3. Reorder software work and resolve the interface dependency. ✓
    This uses the authorized backlog flexibility while addressing the dependency before integration and preserving fixed permit and safety controls.
  4. Apply one sequencing method to software, permits, inspections, and safety testing.
    The project deliberately combines adaptive software work with fixed permitting and safety controls; one sequence would ignore those distinctions.
The trap
Confuses integrated delivery with identical sequencing. Uses a global lifecycle change to address a local dependency. Prioritizes feature value over an established dependency.

Reorder authorized software work while resolving the interface dependency and preserving fixed controls.

2. Agree traceable interfaces and acceptance criteria: What should the project manager do to prevent scope ambigu

Easy
A university is integrating admissions, finance, and identity systems through a hybrid project. During planning, analysts discover that each department uses a different definition of an “enrolled student.” The sponsor approved the business objective, but no interface requirements or acceptance measures exist. Configuration is scheduled to begin next month, and the university cannot afford extensive rework after interfaces are built. What should the project manager do to prevent scope ambiguity?
  1. Agree traceable interfaces and acceptance criteria with departments. ✓
    Shared definitions, traceable requirements, and measurable acceptance criteria align the departments before configuration begins.
  2. Ask the technical lead to select the definition that best fits the systems.
    Technical convenience cannot resolve a cross-department business definition without stakeholder agreement.
  3. Start configuration using the sponsor’s broad objective as the interface specification.
    A broad objective does not define interface behavior or measurable acceptance criteria.
  4. Reserve funds for possible interface redesign after configuration starts.
    A reserve does not prevent unclear requirements or later acceptance disputes and rework.
The trap
Delegates business scope to technical preference. Funds rework instead of preventing ambiguity. Treats an objective as detailed scope.

Define traceable interface requirements and acceptance criteria before configuration.

3. Ask the sponsor to confirm the benefit target and adoption: Which TWO actions should the project manager take?

Medium
A predictive telecommunications migration is six weeks from completion. The project sponsor owns the business benefit of reducing customer call transfers, while the technical lead manages configuration and the project manager coordinates delivery. Weekly reports show every migration batch completed, but call-transfer rates have not improved because the service desk has not adopted the new routing procedure. The sponsor asks what must change to realize value. Which TWO actions should the project manager take? Select TWO.

Select two. More than one option is correct — every correct one is ticked below.

  1. Ask the sponsor to confirm the benefit target and adoption measures. ✓
    The benefit owner must clarify the desired outcome and indicators beyond completed migration batches.
  2. Delay all remaining migrations until call-transfer rates improve.
    A blanket delay may waste capacity without defining or implementing the adoption intervention needed.
  3. Assign the service desk lead an adoption plan with training and measured rollout activities. ✓
    A responsible operational lead must execute adoption actions that connect delivered capability to realized benefit.
  4. Transfer benefit accountability to the project manager until closure.
    Coordination authority does not replace the sponsor’s ownership of the business benefit.
  5. Direct the technical lead to report additional completed migration batches.
    More output reporting would not address the evidenced service-desk adoption failure.
The trap
Stops delivery without assigning the adoption response. Confuses project coordination with benefit ownership. Measures activity rather than the missing outcome.

Confirm outcome measures with the benefit owner and assign operational adoption actions to the service desk.

4. Escalate the competing demand with schedule and compliance: Which TWO actions should the project manager take?

Medium
An insurance modernization project has an approved baseline requiring a claims-data architect for the next release. The architect is also requested by a regulatory reporting project. The portfolio office confirms the architect cannot support both critical activities concurrently. The modernization sponsor values the release date, while the reporting sponsor controls a fixed regulatory deadline. Both work packages need the same specialized skills, and adding junior analysts would not satisfy the interface design responsibility. Which TWO actions should the project manager take? Select TWO.

Select two. More than one option is correct — every correct one is ticked below.

  1. Promise the modernization release date and request the architect after reporting finishes.
    This assumes availability despite a fixed regulatory deadline and creates an unsupported commitment.
  2. Replace the architect with junior analysts and retain the baseline dates.
    The evidence states junior analysts cannot fulfill the specialized interface responsibility.
  3. Escalate the competing demand with schedule and compliance consequences to portfolio governance. ✓
    Governance must resolve the shared specialist allocation using documented project consequences and competing priorities.
  4. Move the architect informally between projects to preserve both schedules.
    Informal splitting obscures capacity limits and risks failing both critical assignments.
  5. Develop a resource-leveled alternative showing impacts on the approved baseline. ✓
    A leveled option makes tradeoffs visible before authorized baseline changes or commitments occur.
The trap
Creates an unauthorized allocation without solving capacity. Ignores the demonstrated competence constraint. Commits without resolving the actual resource conflict.

Escalate the shared-resource conflict and present a leveled alternative with explicit baseline consequences.

5. Obtain documented verification and acceptance first: What should the project manager do first?

Medium
A hybrid construction refurbishment project is moving from demolition to interior systems installation. A specialist vendor completed its contracted work, but the team has not verified fire-stopping records or accepted the area. The vendor requests release of its supervisor, while the next contractor is scheduled to mobilize in three days. The contract assigns acceptance to the project’s quality representative and requires documented handoff records before successor work begins. What should the project manager do first?
  1. Start successor work while the quality representative reviews records remotely.
    Starting before acceptance can obstruct verification and breach the required documented handoff.
  2. Ask the successor contractor to inspect the area informally before mobilization instead of obtaining formal acceptance.
    An informal successor inspection cannot replace the quality representative’s assigned contractual acceptance authority.
  3. Obtain documented verification and acceptance first. ✓
    The assigned quality representative’s acceptance and required records must precede vendor release and successor work.
  4. Release the vendor supervisor and collect the required records during installation.
    Delayed records weaken acceptance evidence and may conceal defects after access is restricted.
The trap
Lets schedule pressure bypass a handoff control. Transfers responsibility before acceptance. Substitutes unauthorized inspection for formal acceptance.

Obtain documented verification and acceptance first.

6. Have operations establish supervisor training: Which TWO actions should the project manager take?

Medium
A predictive pharmaceutical packaging project is on budget and reports 100% equipment installation. However, production operators are bypassing the new labeling workflow, and pilot adoption is 35% against the approved 80% target. The sponsor wants to declare success because installation is complete. Quality has confirmed the workflow meets validation requirements, while operations reports that shift supervisors were not trained. The project manager may coordinate training but cannot alter validated controls without quality approval. Which TWO actions should the project manager take? Select TWO.

Select two. More than one option is correct — every correct one is ticked below.

  1. Declare success because installation reached the approved deliverable target.
    Installation output does not demonstrate achievement of the explicit adoption target or business readiness.
  2. Have operations establish supervisor training and a measured adoption rollout. ✓
    Training and rollout address the evidenced adoption gap while preserving validated workflow controls.
  3. Change the validated workflow to make bypassing easier for operators.
    Changing validated controls without quality approval violates the stated governance constraint.
  4. Report adoption performance separately from installation and forecast remaining transition effort. ✓
    Separate measures prevent output completion from masking unmet adoption and resource needs.
  5. Use contingency funds to improve the reported adoption percentage.
    Funding cannot legitimately improve a metric without changing behavior and would obscure actual performance.
The trap
Addresses resistance by bypassing validation authority. Confuses deliverable completion with outcome adoption. Treats adoption measurement as a financial problem.

Implement measured supervisor training and report adoption separately from installation completion.

7. Compare safety: What should the project manager do?

Hard
A hospital is rolling out a hybrid patient-discharge service across six wards. Early testing meets the approved technical checklist, but nurses report two documentation steps that may increase discharge time. The sponsor wants the final two wards launched this month for staffing savings. Removing the steps saves four days but could increase medication-record errors. Acceptance criteria and the benefit target are documented. What should the project manager do?
  1. Launch now and document the medication-error concern for later support review.
    This knowingly defers an evidenced quality concern that may affect patient safety and benefit realization.
  2. Add every requested documentation step before assessing its value, risk, or feasibility.
    This expands scope without determining which steps address the quality concern or provide sufficient value.
  3. Ask the sponsor to approve launch because the technical checklist passed inspection.
    Technical inspection does not establish operational acceptance or show that the intended benefit remains achievable.
  4. Compare safety, acceptance, and benefit impacts with clinical stakeholders before recommending launch. ✓
    This evaluates the documented tradeoff with affected specialists before recommending whether deployment should proceed.
The trap
Prioritizes schedule over a documented safety concern. Confuses technical conformance with operational acceptance. Adds unprioritized scope without evaluating the tradeoff.

Compare safety, acceptance, and benefit impacts with clinical stakeholders before recommending launch.

8. Trace dependencies: What should the project manager do first?

Hard
A city transit project uses adaptive delivery for a passenger-information platform while station hardware follows fixed dependencies. A vendor forecasts a three-week delay for an interface that is not currently critical but feeds a later critical-path test. The team has capacity for only one additional integration stream, and overlap could create rework. What should the project manager do first?
  1. Reorder the entire backlog around the delayed interface and its dependencies.
    Backlog changes cannot replace integrated dependency analysis or authorize changes to fixed hardware sequencing.
  2. Trace dependencies, capacity, and overlap risk first. ✓
    This establishes whether intervention affects completion and supports comparison of feasible compression consequences before authorization.
  3. Classify the forecast as a baseline variance and seek sponsor approval for compression.
    A forecast is not necessarily a confirmed baseline variance, and approval should follow impact and feasibility analysis.
  4. Fast-track both activities before confirming the delay's effect.
    Immediate overlap may consume scarce capacity and create rework before the completion-date effect is established.
The trap
Treats a forecast as requiring immediate compression. Changes priorities without analyzing the whole schedule. Escalates before verifying impact and alternatives.

Trace dependencies, capacity, and overlap risk first.

9. Reconcile the accepted work and report the revised: The project manager must choose how to communicate status

Medium
A manufacturing automation project is operating under an approved predictive baseline. At month six, the status report shows 60% planned completion, 55% earned value, and actual cost equal to 50% of budget. The controls engineer reports that the dashboard excludes three accepted work packages because their records were uploaded late. The plant manager wants the project reported green to protect a production-window commitment. The project manager must choose how to communicate status while deciding whether the forecast requires corrective action.
  1. Have the controls engineer correct the records without noting the discrepancy.
    Correcting records helps, but concealing the discrepancy prevents transparent interpretation of the earlier report.
  2. Reconcile the accepted work and report the revised forecast. ✓
    Validated accepted work and reconciled artifacts provide the proper basis for performance interpretation and forecasting.
  3. Use the dashboard unchanged until the late records appear next month.
    Known omissions make the current report unreliable for status communication and corrective-action decisions.
  4. Report green because actual cost is below the approved budget.
    Favorable cost information does not establish schedule performance, completed scope, or reliable status evidence.
The trap
Presents known incomplete evidence as current. Repairs data while withholding material reporting context. Uses one favorable measure to override contradictory evidence.

Reconcile accepted work and communicate the resulting status and forecast honestly.

10. Transfer ownership: What should the project manager do?

Medium
A predictive logistics-network project completed routing-software installation at all distribution centers. The sponsor confirms contractual deliverables are complete, but operations leaders request a final fuel-savings dashboard and a refresher for night-shift dispatchers. The approved closure plan includes knowledge transfer, contract closure, and benefit ownership; no project funds remain for new feature development. The benefits owner can measure fuel use for six months after handover. What should the project manager do?
  1. Transfer ownership, track benefits, and complete planned closure tasks. ✓
    This hands off continuing measurement and follow-up while completing knowledge transfer, contract closure, and benefit ownership.
  2. Close the project after deliverable acceptance alone.
    Acceptance alone does not complete the approved closure obligations or establish benefit ownership and readiness.
  3. Add the dashboard and refresher to project scope and extend the schedule.
    These requests should not become project scope without appropriate authorization and funding.
  4. Obtain new funding for every improvement before closing the project.
    New enhancements need not block closure when follow-up ownership and benefit measurement are transferred.
The trap
Equates contractual completion with complete closure. Converts stakeholder requests into unauthorized scope. Treats all post-project requests as closure prerequisites.

Transfer ownership, track benefits, and complete planned closure tasks.

11. Restrict the confidential file and obtain product-owner: What should the project manager do first?

Easy
A logistics company is developing a route-optimization service using adaptive delivery. The team uses an artificial-intelligence tool to suggest route rules from historical shipment data. The tool was given a confidential customer file, and its latest suggestion would reduce miles but exclude rural deliveries that have contractual service commitments. The product owner has not reviewed the suggestion. A developer proposes placing the rule directly into the next iteration because the forecasted savings are attractive. What should the project manager do first?
  1. Ask the developer to implement the rule while the product owner reviews the contractual effects during the iteration.
    Implementation would precede validation and could violate contractual service commitments.
  2. Delete the suggestion and prohibit further use of the artificial-intelligence tool.
    The facts require controlled data handling and human validation, not an automatic ban on potentially useful analysis.
  3. Anonymize the file after implementation and compare the resulting savings with the forecast.
    Data protection and validation must precede implementation, not follow it.
  4. Restrict the confidential file and obtain product-owner validation before implementation. ✓
    The project manager should immediately control further use or disclosure of the confidential data and ensure accountable business validation before the rule enters delivery.
The trap
Uses adaptive delivery to justify deploying an unvalidated rule. Places confidentiality and governance controls after deployment. Overreacts instead of applying proportionate controls.

Control the confidential data and obtain accountable product-owner validation before implementation.

12. Choose the exception report for traceability acceptance: The project manager must choose which alternative bes

Easy
A food manufacturer is implementing a predictive traceability system. The approved scope requires recording supplier, lot, and recall-event data for every finished product. An AI analysis suggests adding farm-level soil data, while quality inspectors request a simpler exception report that can be validated against regulatory records. The sponsor allows only one enhancement before the fixed audit date, and the product scope statement does not include soil analytics. The project manager must choose which alternative best supports approved scope and acceptance.
  1. Deliver both by reducing supplier and lot validation.
    Reducing mandatory validation would undermine approved traceability and audit evidence.
  2. Choose the exception report for traceability acceptance. ✓
    The report directly supports required traceability and provides evidence that can be checked against regulatory records.
  3. Choose soil analytics for future value.
    Potential future value does not outweigh the feature's absence from approved scope and the limited time before audit acceptance.
  4. Reject both because approved predictive scope cannot change.
    An authorized enhancement can be evaluated when it supports approved outcomes and fits the constraint.
The trap
Prioritizes speculative value over approved requirements. Treats predictive planning as an absolute ban on controlled change. Creates capacity by weakening required acceptance work.

Choose the exception report because it strengthens approved traceability and audit acceptance.

725 more Process questions

The remaining 725 questions in this domain are part of the full PMP bank — 1799 questions, every option explained. Start with the free five-minute check and see your score per domain.

Test your PMP readiness — free

Other PMP domains

Part of the Certsqill PMP question bank · Process · Every answer, right and wrong, comes with its own explanation.