Project Management Professional (PMP) — All Questions

A project manager wants to confirm that the correct processes and standards are being followed during execution and to recommend improvements. Which activity accomplishes this?

• a.Updating the stakeholder register
• b.Conducting a quality audit✓
• c.Inspecting each finished deliverable
• d.Recalculating the schedule baseline

A quality audit is a structured, independent review confirming that project activities follow organizational and project policies, processes, and procedures, and it identifies improvements. Inspecting deliverables is quality control, while recalculating baselines and updating registers are unrelated to process assurance.

A PM discovers that the cost of preventing defects (training, reviews) is far lower than the cost of failures found by customers. This comparison is part of which concept?

• a.Earned value management
• b.Value analysis
• c.Reserve analysis
• d.Cost of quality✓

Cost of quality weighs prevention and appraisal (conformance) costs against internal and external failure (non-conformance) costs, showing that prevention is usually cheaper than failure. Earned value tracks performance, reserve analysis manages contingency, and value analysis targets cost reduction of functions.

During execution, a team completes an increment that the product owner accepts but stakeholders want changes based on what they saw. In agile, when are these changes best handled?

• a.By deferring all feedback until the project ends
• b.By rejecting them to preserve the original plan
• c.By adding them to the product backlog for prioritization in a future iteration✓
• d.By immediately inserting them into the current iteration so stakeholders see their feedback acted on right away

Agile welcomes feedback; stakeholder-requested changes become backlog items the product owner prioritizes for a future iteration. Inserting them mid-iteration disrupts commitment, deferring to the end forfeits agility's benefit, and rejecting feedback contradicts the empirical, adaptive approach.

A project manager notices that a milestone marked '0% or 100%' is being used to measure earned value for a work package. Which EV measurement method is this?

• a.Apportioned effort method
• b.Percent complete method
• c.Weighted milestone method
• d.Fixed-formula (e.g., 0/100) method✓

The fixed-formula method credits earned value at set points, such as 0% at start and 100% at completion (0/100), useful for short work packages. Weighted milestone credits value at multiple milestones, percent complete estimates ongoing progress, and apportioned effort ties value to another activity.

A PM must decide the delivery approach for a project with moderate requirement uncertainty, where some components are stable and others will evolve. Which approach is most suitable?

• a.No formal approach; let the team decide component by component in an ad hoc way as each piece of work happens to come up
• b.A hybrid approach applying predictive to stable parts and agile to evolving parts✓
• c.A fully predictive approach for all components
• d.A fully agile approach for all components

A hybrid approach applies predictive methods to stable, well-defined components and agile methods to uncertain, evolving ones, fitting the method to the work. Forcing everything into one mode ignores the mixed nature of the work, and an ad hoc approach lacks coherent governance.

A project's schedule is falling behind. The PM considers fast tracking. What is the primary risk the PM must weigh before applying it?

• a.Overlapping sequential activities can increase rework and coordination risk✓
• b.It requires obtaining formal customer approval for every overlapped activity before the parallel work can proceed
• c.It always increases direct costs significantly
• d.It reduces the project scope

Fast tracking overlaps activities normally done in sequence, which compresses schedule but raises the risk of rework and added coordination if early work changes. Unlike crashing, it does not necessarily add cost, and it does not reduce scope or require per-activity customer approval.

A PM must decide whether to crash or fast track to recover a slipping schedule. Budget is very tight, but some risk of rework is acceptable. Which technique fits best?

• a.Crashing, since it never adds cost
• b.Fast tracking, since it avoids added cost by overlapping activities✓
• c.Resource leveling, which shortens the overall schedule by smoothing resource demand across the critical activities
• d.Reducing quality standards to save time

With a tight budget but tolerance for some rework risk, fast tracking is preferable because overlapping activities compresses the schedule without necessarily adding cost. Crashing adds resources and cost, resource leveling typically lengthens the schedule, and cutting quality is not a legitimate compression method.

A project uses rolling wave planning. A distant phase currently has only high-level estimates. When should it be detailed?

• a.Immediately, in full detail, at project start
• b.As the phase approaches and more information becomes available✓
• c.Never; high-level estimates are sufficient throughout
• d.Only after the phase has already started

Rolling wave planning progressively elaborates work as the phase nears and information matures, balancing planning effort with available detail. Detailing everything at the start wastes effort on uncertain work, while waiting until after the phase starts leaves the team without a plan.

A PM is developing the schedule and wants to identify the sequence of activities with the least scheduling flexibility that determines the project duration. Which method identifies this?

• a.Earned value analysis
• b.Monte Carlo simulation
• c.Resource leveling
• d.Critical path method✓

The critical path method identifies the longest path of dependent activities with zero float, which determines the shortest project duration. Resource leveling addresses resource constraints, Monte Carlo models uncertainty, and earned value tracks performance, none of which define the critical path itself.

A resource is overallocated across concurrent activities. The PM adjusts the schedule so the resource is not scheduled beyond capacity, which may extend the finish date. Which technique is this?

• a.Fast tracking
• b.Resource leveling✓
• c.Critical path shortening
• d.Crashing

Resource leveling adjusts start and finish dates so resource demand stays within capacity, which can lengthen the critical path and finish date. Fast tracking and crashing compress the schedule, and shortening the critical path is a goal, not the technique used to resolve overallocation.

A PM wants to keep the schedule the same but optimize resource usage within existing float, without changing the critical path. Which technique applies?

• a.Crashing
• b.Fast tracking
• c.Resource leveling
• d.Resource smoothing✓

Resource smoothing adjusts activities only within their available float so the critical path and finish date remain unchanged while demand is evened out. Resource leveling can change the critical path, and crashing and fast tracking are compression techniques, not float-based optimizations.

During procurement planning, the PM must decide whether to make a component in-house or buy it from a vendor. Which analysis supports this decision?

• a.Root-cause analysis
• b.Variance analysis
• c.Earned value analysis
• d.Make-or-buy analysis✓

Make-or-buy analysis compares the costs, risks, and capabilities of producing internally versus procuring externally to guide the sourcing decision. Earned value and variance analysis track performance, and root-cause analysis investigates defects, none of which decide make versus buy.

A seller has been selected and the PM is finalizing the agreement. Which document formally defines the exact goods or services the seller will provide?

• a.The project charter
• b.The risk register
• c.The stakeholder register
• d.The procurement statement of work (SOW)✓

The procurement statement of work precisely describes the goods or services to be procured so sellers can determine whether they can deliver. The charter authorizes the project, and the stakeholder and risk registers track people and risks, not procured scope.

During execution, the PM must gather work performance data, compare it to the plan, and produce work performance reports for stakeholders. This is part of which process group activity?

• a.Closing the project
• b.Planning the schedule
• c.Monitoring and controlling project work✓
• d.Initiating the project

Collecting work performance data, analyzing it against the plan, and issuing work performance reports are core to monitoring and controlling project work. Initiating authorizes the project, planning develops baselines, and closing finalizes and documents the project.

A project manager wants a concise visual that shows the project's major deliverables and completion events against time for executive reporting. Which tool is most appropriate?

• a.A milestone chart✓
• b.A detailed network diagram
• c.A resource histogram
• d.A WBS dictionary

A milestone chart displays major deliverables and key events against time in a simple format suited to executive audiences. A network diagram shows detailed dependencies, a WBS dictionary defines work packages, and a resource histogram shows resource usage, all too detailed for a high-level summary.

A team is starting an iteration and creates a plan for how to turn selected backlog items into a done increment during the sprint. Which artifact results from this?

• a.The release plan
• b.The sprint backlog✓
• c.The product roadmap
• d.The product backlog

The sprint backlog is the set of selected product backlog items plus the plan to deliver them as an increment during the sprint. The product backlog is the overall ordered list, while the roadmap and release plan span longer horizons than a single sprint.

A PM must forecast the total project cost when the original estimate is no longer valid because performance so far reflects a fundamental change. Which EAC approach is most appropriate?

• a.EAC = AC + (BAC - EV), assuming remaining work at plan
• b.EAC = a new bottom-up estimate to complete plus actual costs✓
• c.EAC = BAC/CPI only
• d.EAC = BAC (no change)

When the original estimate is fundamentally invalid, the most reliable EAC is a fresh bottom-up estimate to complete added to actual costs incurred. Formula-based EACs assume past patterns hold, which is inappropriate once conditions have fundamentally changed.

Given BAC = $300,000, EAC = $360,000, what is the variance at completion (VAC), and what does it signal?

• a.$60,000; the project will finish under budget
• b.$360,000; the project is complete
• c.$300,000; the project has no variance
• d.-$60,000; the project is forecast to finish over budget✓

VAC = BAC - EAC = 300,000 - 360,000 = -$60,000, and a negative VAC forecasts a budget overrun of that amount at completion. A positive VAC would indicate an expected underrun; here the project is projected to exceed its budget.

A stakeholder analysis reveals a group with low power but high interest in the project. What is the recommended engagement approach for them?

• a.Merely monitor them with minimal effort
• b.Keep them informed with adequate information✓
• c.Ignore them since they lack power
• d.Manage them closely as key players

In the power/interest grid, low-power, high-interest stakeholders should be kept informed, as they care about outcomes and can be valuable advocates. Managing them closely overinvests, while merely monitoring or ignoring them neglects their genuine interest and potential support.

During planning, the PM identifies that two teams share a scarce specialist, creating a resource dependency across their schedules. How should this be managed?

• a.Ignore it and let the teams compete for the specialist
• b.Remove the specialist's tasks from both schedules
• c.Coordinate the schedules and apply resource optimization so the specialist is not overallocated✓
• d.Duplicate the specialist role by assigning untrained staff to cover the shared work across both team schedules

A shared scarce resource requires coordinated scheduling and resource optimization (leveling or smoothing) so the specialist is not overallocated. Letting teams compete causes conflict, assigning untrained staff risks quality, and removing needed tasks is not a legitimate option.

A project manager wants to ensure the project produces deliverables that meet requirements and are fit for use, balancing grade and quality. Which statement is accurate?

• a.Low grade may be acceptable, but low quality is generally a problem✓
• b.Low grade is always a quality problem
• c.Grade and quality are identical concepts, so a higher grade will always guarantee a higher level of quality as well
• d.High grade always means high quality

Grade is a category of features while quality is conformance to requirements and fitness for use; a low-grade product can be acceptable if it meets its requirements, but low quality is generally a problem. Grade and quality are distinct, so high grade does not guarantee high quality.

During a project, a team member proposes a small process tweak that could prevent a category of future errors. There is no immediate defect. What kind of change request is this?

• a.A defect repair
• b.A scope change
• c.A corrective action
• d.A preventive action✓

A preventive action reduces the probability of future negative outcomes before any defect occurs, which fits proposing a tweak to prevent future errors. Defect repair fixes an existing flaw, corrective action realigns performance to the plan, and a scope change alters deliverables.

A project's requirements were gathered mainly from one department, and now other affected groups say their needs were missed, forcing rework. What planning practice would have prevented this?

• a.Deferring requirements until execution
• b.Locking the scope baseline sooner
• c.Reducing the total number of requirements gathered so the scope stays small and less likely to be missed later on
• d.Engaging all relevant stakeholders during requirements collection✓

Comprehensive requirements collection engages all relevant stakeholders so needs are captured early, preventing costly gaps and rework. Locking scope sooner without complete input freezes an incomplete picture, fewer requirements omit needs, and deferring gathering delays the very analysis needed up front.

A PM is deciding sprint length for a new agile team facing high uncertainty and wanting frequent feedback. Which choice aligns with agile principles?

• a.A short sprint (e.g., one to two weeks) to enable frequent inspection and adaptation✓
• b.No fixed sprint length; deliver whenever ready
• c.A single sprint whose length matches the total project duration so the team plans and delivers everything just once
• d.A twelve-week sprint to minimize overhead

Short iterations of one to two weeks maximize opportunities for inspection, feedback, and adaptation under high uncertainty. Very long sprints delay learning, no fixed length removes cadence and predictability, and a single project-length sprint eliminates iteration altogether.

During execution, the sponsor requests weekly earned value reports, but the PM currently reports only actual costs. What must the PM add to enable earned value reporting?

• a.Only the planned value (PV) each period
• b.Planned value, earned value, and actual cost measurements against the baseline✓
• c.Only the actual cost (AC) each period, since the spending to date is enough to judge overall project performance
• d.A stakeholder engagement assessment

Earned value analysis requires PV, EV, and AC measured against the performance measurement baseline to compute variances and indices. Reporting AC alone, or PV alone, gives no efficiency picture, and a stakeholder assessment is unrelated to cost/schedule performance measurement.

A project manager wants to validate that the product meets business needs and delivers intended value after deployment, not just that it was built correctly. Which perspective is this?

• a.Quality control inspection
• b.Verification that each deliverable was built to its documented specification and passes inspection at handoff
• c.Validation that the solution meets business needs (fitness for use)✓
• d.Configuration management

Validation confirms the solution is fit for use and meets business needs, whereas verification confirms it was built to specification. Quality control inspects deliverables and configuration management controls versions, but neither answers whether the delivered product achieves the intended business value.

An agile team wants a simple visual that shows remaining work in the sprint declining toward zero over time. Which chart is this?

• a.A cumulative flow diagram of the whole project
• b.A Pareto chart
• c.A sprint burndown chart✓
• d.A control chart

A sprint burndown chart plots remaining work against time, ideally trending down to zero by sprint end, giving a quick read on progress. A control chart tracks process variation, a cumulative flow diagram shows work states across a longer horizon, and a Pareto chart ranks defect causes.

A PM tracks total scope delivered growing toward the release target over multiple iterations. Which chart best communicates cumulative progress toward a release?

• a.A sprint burndown chart
• b.A release burnup chart✓
• c.A fishbone diagram
• d.A responsibility assignment matrix

A burnup chart shows cumulative completed work rising toward the scope line, making it ideal for tracking progress toward a release and visualizing scope changes. A sprint burndown focuses on one iteration's remaining work, and fishbone diagrams and RAMs serve entirely different purposes.

A project manager realizes the change control board keeps approving changes without checking impacts across scope, schedule, cost, quality, and risk. What is the risk of this practice?

• a.Stakeholders will gradually lose interest in the project because approvals keep happening without their involvement
• b.Approved changes may cause unmanaged ripple effects across baselines✓
• c.The change log will become too detailed
• d.Changes will be implemented too slowly

Integrated change control exists precisely to assess a change's ripple effects across all baselines; skipping this leads to unmanaged consequences and conflicting baselines. The concern is not speed, log detail, or stakeholder interest but the integrity of the interrelated project constraints.

A PM must decide when to release a product: predictive plans a single release at the end, while the customer could benefit from value sooner. What agile-inspired option should the PM consider?

• a.Delay the release even further to add more scope so the first version is as complete as possible before launch
• b.Release a minimum viable product early, then iterate with additional increments✓
• c.Release only if every feature is complete
• d.Cancel the remaining scope

Releasing a minimum viable product early delivers value sooner and enables learning, after which further increments add capability. Waiting for every feature delays benefits, adding scope postpones value further, and canceling remaining scope forfeits planned value without justification.

During risk identification, a PM organizes potential risk sources into hierarchical categories such as technical, external, organizational, and project management. Which tool is this?

• a.A decision tree
• b.A work breakdown structure (WBS)
• c.A probability and impact matrix
• d.A risk breakdown structure (RBS)✓

The risk breakdown structure hierarchically categorizes risk sources, helping ensure comprehensive identification across categories. A WBS decomposes deliverables, a probability and impact matrix prioritizes identified risks, and a decision tree evaluates choices, none of which categorize risk sources.

A risk is beyond the project's authority to address and would be better handled at the program or organizational level. What is the appropriate response?

• a.Escalate the risk to the appropriate level of authority✓
• b.Ignore it since the project cannot control it
• c.Accept the risk within the project
• d.Mitigate it using project contingency reserves

Escalation moves a risk to the level of the organization that has the authority and ability to respond, and it is then owned outside the project. Accepting or mitigating within the project overreaches its authority, and ignoring the risk leaves it unmanaged entirely.

During execution, the PM finds that stakeholders receive conflicting status updates from different team members. What should the PM implement to fix this?

• a.Increase the frequency of all reports
• b.Ask all team members to stop communicating with stakeholders directly so that only one channel of updates remains
• c.A single source of truth and defined reporting responsibilities per the communications plan✓
• d.Route every message through the sponsor

Conflicting updates are resolved by establishing a single source of truth and clearly assigning who communicates what, as defined in the communications plan. Silencing team members or funneling everything through the sponsor is impractical, and more frequent reports do not fix inconsistency.

A project manager wants to confirm the team understands each person's role for key deliverables to avoid gaps and overlaps. Which tool clarifies who is Responsible, Accountable, Consulted, and Informed?

• a.A precedence network diagram that maps activity dependencies
• b.A RACI (responsibility assignment) matrix✓
• c.A Gantt chart
• d.A control chart

A RACI matrix maps deliverables or activities to roles as Responsible, Accountable, Consulted, and Informed, preventing gaps and overlaps. Gantt charts and network diagrams show schedule, and control charts show process variation, none of which clarify role responsibilities.

A PM is planning quality and wants to define the specific quality standards relevant to the project and how the project will demonstrate compliance. Which document captures this?

• a.The procurement plan
• b.The quality management plan✓
• c.The scope statement
• d.The stakeholder register

The quality management plan defines the applicable standards, quality objectives, roles, and how compliance will be achieved and demonstrated. The scope statement defines deliverables, while the stakeholder register and procurement plan address different knowledge areas.

During execution, a PM measures a completed deliverable against its documented requirements and finds it conforms. Which process was just performed?

• a.Plan quality management
• b.Control quality✓
• c.Define scope
• d.Validate scope

Measuring a deliverable against requirements to confirm conformance is control quality, which produces verified deliverables. Validate scope then obtains customer acceptance, define scope establishes the deliverables, and plan quality sets the standards, none of which is the inspection itself.

A project manager on an agile team notices no one is accountable for maximizing the value of the product and ordering the backlog. Which role fills this need?

• a.The product owner✓
• b.The Scrum Master
• c.The project sponsor
• d.The development team lead

The product owner is accountable for maximizing product value and managing and ordering the product backlog. The Scrum Master serves the process and removes impediments, the development team builds the increment, and the sponsor funds and champions the project.

A PM must integrate all subsidiary plans (scope, schedule, cost, quality, risk, etc.) into one coherent document that guides execution. What is this document?

• a.The statement of work
• b.The project charter
• c.The project management plan✓
• d.The business case

The project management plan integrates all subsidiary management plans and baselines into a single coherent guide for executing, monitoring, and controlling the project. The charter authorizes the project, the business case justifies it, and the SOW describes procured work, none of which integrate all plans.

A project's schedule shows activity float being consumed steadily on a near-critical path until it has almost none left. What should the PM do?

• a.Immediately crash all activities on it
• b.Remove those activities from the schedule
• c.Ignore it because it is not yet the critical path
• d.Monitor the near-critical path closely, as it may become critical✓

A near-critical path with dwindling float can become the critical path, so the PM should monitor it closely and be ready to act. Ignoring it risks a surprise slip, crashing prematurely wastes resources, and removing activities is not a valid response to shrinking float.

A PM is planning procurements and drafts evaluation criteria to select among competing sellers. Which factor set is most appropriate to include?

• a.Only the lowest bid price, regardless of the seller's technical capability, past performance, or delivery risk
• b.Whichever seller responds first
• c.Technical capability, past performance, price, and risk, weighted per project needs✓
• d.Only the seller closest to the PM's office

Sound source selection weighs technical capability, past performance, price, and risk according to the project's priorities, not price alone. Choosing solely on price, proximity, or response speed ignores capability and value, which can lead to poor delivery and higher total cost.

During execution, the PM identifies that a deliverable will not meet a quality standard unless rework is done, and rework will affect the schedule. What should the PM do first?

• a.Assess the impact and process the rework as a change request through integrated change control✓
• b.Ship the deliverable as-is to protect the schedule
• c.Silently absorb the resulting delay without informing any stakeholders so the schedule appears to remain on track
• d.Lower the quality standard to avoid rework

Rework that affects the schedule is a change that must be assessed and authorized through integrated change control, keeping baselines aligned. Shipping substandard work, hiding delays, or unilaterally lowering standards compromises quality and transparency.

A PM wants to ensure lessons are captured continuously, not just at closeout, so the current project can improve as it runs. What supports this?

• a.Delegating all learning to the PMO
• b.Recording lessons only after a significant failure occurs, since routine work rarely yields insights worth capturing
• c.Maintaining a lessons learned register updated throughout the project✓
• d.Waiting until the final closeout meeting

A lessons learned register maintained throughout the project lets the team apply improvements immediately and feeds the final repository at closeout. Waiting until closeout, recording only after failures, or delegating entirely to the PMO forfeits in-flight learning.

A project has PV = $120,000, EV = $100,000, AC = $110,000. What is the schedule variance (SV), and what does it mean?

• a.-$20,000; the project is behind schedule✓
• b.$10,000; the project is under budget
• c.-$10,000; the project is over budget
• d.$20,000; the project is ahead of schedule

SV = EV - PV = 100,000 - 120,000 = -$20,000, and a negative schedule variance means less value has been earned than planned, so the project is behind schedule. Cost status is measured by CV = EV - AC, not by SV.

An agile team repeatedly finishes items but stakeholders only see progress at the end. To improve transparency, what should the PM encourage?

• a.Frequent demonstrations of working increments and information radiators visible to all✓
• b.Reporting progress only in percentage complete
• c.Restricting stakeholder access to the team's board so progress is shared only in carefully controlled summaries
• d.Detailed weekly text reports only

Agile transparency comes from frequently demonstrating working increments and using information radiators (visible boards and charts) that anyone can inspect. Text-only reports, hidden boards, or abstract percentages provide far less insight than seeing real, working results.

A PM is deciding how much contingency reserve to set aside based on the identified risks and their expected impacts. Which technique determines the reserve amount?

• a.Make-or-buy analysis comparing in-house production against vendor cost
• b.Critical path method
• c.Reserve analysis based on quantitative risk assessment✓
• d.Pareto analysis

Reserve analysis, informed by quantitative risk assessment such as EMV, establishes contingency reserves sized to the identified risk exposure. Make-or-buy addresses sourcing, the critical path method addresses schedule, and Pareto analysis ranks defect causes, none of which sizes reserves.

A project manager needs to confirm the delivery approach at the outset. Requirements are volatile, feedback is essential, and the customer can collaborate frequently. Which factor most supports choosing agile?

• a.A fixed, unchangeable scope
• b.A one-time deployment with no feedback needed
• c.A customer who is unavailable to collaborate
• d.High requirement volatility with frequent customer feedback✓

High requirement volatility, the need for frequent feedback, and an available, collaborative customer are strong signals that agile is appropriate. Fixed scope, no feedback needs, or an unavailable customer point instead toward predictive delivery.

A project's WBS is complete. The PM now needs to define the specific activities required to produce each work package. What process is this?

• a.Estimate activity durations
• b.Define activities✓
• c.Sequence activities
• d.Develop schedule

Define activities decomposes work packages into the specific scheduled activities needed to produce them. Sequencing arranges those activities, duration estimating assigns time, and develop schedule integrates everything into the schedule model, each occurring after activities are defined.

During monitoring, a PM detects that the project's actual progress varies from the plan and wants to understand the magnitude and cause of the difference. Which technique should be applied?

• a.Brainstorming
• b.Variance analysis✓
• c.Expert judgment only
• d.Benchmarking

Variance analysis compares actual performance against the baseline to quantify deviations and investigate their causes, guiding corrective action. Brainstorming and benchmarking generate ideas or comparisons, and expert judgment alone does not systematically quantify the deviation.

A PM wants to prevent unauthorized changes to project deliverables and ensure only approved versions are used. Which system supports this?

• a.A configuration management system✓
• b.The risk register
• c.The communications plan
• d.The stakeholder engagement plan

A configuration management system controls the versions and specifications of deliverables, ensuring only approved configurations are used. The risk register, stakeholder plan, and communications plan manage other aspects and do not control deliverable versions and specifications.

An agile team wants to keep the product backlog healthy: items well-defined, estimated, and ordered for upcoming sprints. Which ongoing activity accomplishes this?

• a.The sprint retrospective
• b.Backlog refinement (grooming)✓
• c.The daily standup
• d.The sprint review

Backlog refinement is the ongoing activity of adding detail, estimates, and order to backlog items so they are ready for future sprints. The retrospective improves the process, the standup coordinates daily work, and the review inspects the increment, none of which maintain the backlog.