PMPRocket
PMP Practice QuestionsQuality Management
Process Domain

Quality Management PMP Practice Questions

Test yourself with 18 free, scenario-based PMP practice questions on quality management, drawn from the Process domain of the exam and aligned to PMBOK 8. Work through each scenario before revealing the answer — every question includes an explanation of why the correct choice is right. For randomized, interactive practice across all topics, use the practice question tool.

Question 1 of 18

A quality audit reveals that 12% of deliverables in the last three iterations failed acceptance testing due to the same defect type. What should you do FIRST?

  1. A.Increase the testing phase duration for all future deliverables — more testing time reduces the rate of defects that escape to production and demonstrates commitment to quality improvement.
  2. B.Accept the defects and document them as known issues, deferring fixes to a planned maintenance cycle after the current delivery is complete and accepted by stakeholders.
  3. C.Assign accountability to the developer responsible for the defect category — clear individual accountability for recurring quality failures deters similar errors in future deliverables.
  4. D.Perform a root cause analysis to identify and eliminate the underlying cause of the recurring defect
Show answer and explanation

Correct answer: D

Quality management emphasizes prevention over inspection. Root cause analysis — such as a fishbone diagram or 5-Whys — identifies and eliminates the systemic cause. Extending testing is a control measure, not prevention. Accepting defects violates quality standards. Assigning blame is counterproductive and does not fix the process.

Question 2 of 18

A project manager is analyzing defects found after product release and wants to identify which defect category causes the most problems. Which quality tool should be used FIRST?

  1. A.Control chart — to determine if the defect rate is within statistical control limits
  2. B.Fishbone diagram — to identify the root cause of each defect type
  3. C.Pareto chart — to identify which defect categories account for the majority of problems
  4. D.Scatter diagram — to find correlation between defect rates and production volume
Show answer and explanation

Correct answer: C

A Pareto chart ranks defect categories by frequency and applies the 80/20 rule — typically 80% of defects come from 20% of causes. Using it first identifies where to focus improvement efforts. Once the top defect categories are identified, a fishbone (Ishikawa) diagram would then be used to drill into the root cause of the highest-frequency category. Control charts monitor process stability over time. Scatter diagrams assess correlations.

Question 3 of 18

A control chart shows that 8 consecutive data points are all above the mean but within the upper control limit. What does this indicate?

  1. A.The process is in statistical control since no data points have exceeded either control limit — trending within the limits is expected natural variation that requires no corrective action.
  2. B.Recalibrate the upper control limit to reflect the new performance data — control limits that are tighter than actual process capability generate unnecessary alarms and wasteful corrective interventions.
  3. C.The data indicates a trend toward the upper specification limit, confirming a direction that should be monitored — but as long as no point exceeds a control limit, no immediate action is required.
  4. D.The process exhibits a non-random pattern (rule of seven) and should be investigated even though no point has exceeded a control limit.
Show answer and explanation

Correct answer: D

The 'rule of seven' states that seven or more consecutive points on the same side of the mean — even within control limits — indicates a non-random (assignable) cause affecting the process. Eight consecutive points above the mean is a rule-of-seven violation. This is a signal the process has shifted and must be investigated before a defect occurs. The process is NOT in control despite points being within limits. Control limits and specification limits are different concepts.

Question 4 of 18

What is the difference between Quality Assurance (QA) and Quality Control (QC)?

  1. A.QA audits processes and evaluates whether quality standards are being followed; QC inspects deliverables and identifies defects in outputs.
  2. B.QA inspects deliverables for defects after production; QC audits the processes that produce those deliverables to ensure they conform to defined standards and prevent future quality failures.
  3. C.QA is performed by the customer during formal acceptance testing; QC is performed by the project team during internal reviews to catch defects before submission to the customer.
  4. D.QA applies primarily in manufacturing and regulated industries where process compliance is auditable; QC applies across all industries to any delivered product or service.
Show answer and explanation

Correct answer: A

QA is a proactive, process-oriented activity — it evaluates processes, standards, and systems to prevent defects from occurring. QC is a reactive, product-oriented activity — it inspects completed work to identify defects and nonconformances. QA = 'Are we building it right?' QC = 'Did we build it right?' Both are performed by the project team and quality department, not the customer. Both apply across all industries.

Question 5 of 18

An agile team has been delivering features that pass sprint review but are later found to have quality issues during integration testing. What practice would BEST prevent this from recurring?

  1. A.Add a dedicated testing sprint at the end of each release — separating integration testing from feature sprints gives testers the focus needed to catch cross-feature defects systematically.
  2. B.Strengthen the Definition of Done to include integration testing criteria that must pass before a story is accepted.
  3. C.Reduce sprint length to two weeks — shorter iterations compress the feedback loop so integration defects are caught and corrected before they accumulate across multiple sprint cycles.
  4. D.Assign a quality manager to review all code before the sprint review — dedicated quality oversight ensures consistent standards are applied across all team members' outputs.
Show answer and explanation

Correct answer: B

The Definition of Done (DoD) defines the quality criteria that must be met before any story is considered complete. Strengthening the DoD to include integration testing means quality is built in — not tested in after the fact. A 'hardening sprint' is an anti-pattern in agile that indicates the team is not building quality continuously. Reducing sprint length does not address the root cause. A quality manager gatekeeper creates a bottleneck and undermines team ownership of quality.

Question 6 of 18

A team is investigating why a critical piece of manufacturing equipment keeps failing. They use a structured approach to categorize causes into categories: People, Methods, Machines, Materials, Measurement, and Environment. What tool are they using?

  1. A.Pareto chart — displays defect frequency by category in descending order, making it easy to identify the vital few causes that account for most of the quality failures.
  2. B.Control chart — tracks a quality metric over time against statistical control limits, helping distinguish between random variation and assignable causes in the defect data.
  3. C.Cause-and-effect (Ishikawa/fishbone) diagram
  4. D.Flowchart — maps the steps in a process to identify where defects are introduced, making it useful for visualizing the sequence of activities that leads to quality failures.
Show answer and explanation

Correct answer: C

The cause-and-effect diagram, also known as the Ishikawa or fishbone diagram, organizes potential causes of a problem into major categories — commonly the 6Ms: Man (People), Method, Machine, Material, Measurement, and Mother Nature (Environment). The shape resembles a fish skeleton, with the problem as the head and branches representing cause categories. This tool helps teams systematically explore all potential root causes. Pareto charts rank causes by frequency; control charts monitor process variation over time.

Question 7 of 18

A project manager implements a quality audit to assess whether the team is following the defined quality standards. The audit reveals several process deviations. What should happen next?

  1. A.Disciplinary action should be taken against team members responsible for deviations
  2. B.The quality audit should be reclassified as a quality control inspection
  3. C.The quality standards should be revised to match current team practices
  4. D.The deviations should be documented, root causes analyzed, and corrective actions developed and tracked
Show answer and explanation

Correct answer: D

Quality audits are a QA activity focused on process improvement, not blame. When deviations are found, the project manager should: document findings, perform root cause analysis to understand why deviations occurred, develop corrective actions, and track their implementation. Disciplinary action may be appropriate in rare cases of willful non-compliance but should not be the first response. Revising standards to match poor practices lowers the quality bar. Reclassifying the audit is irrelevant.

Question 8 of 18

A project manager calculates the cost of quality. Which of the following is an example of 'cost of nonconformance'?

  1. A.Reworking a defective deliverable after it fails acceptance testing
  2. B.Training team members on quality standards
  3. C.Conducting inspections and testing during production
  4. D.Purchasing quality measurement equipment
Show answer and explanation

Correct answer: A

Cost of quality is divided into: Cost of Conformance (doing things right) and Cost of Nonconformance (failing to do things right). Rework is a nonconformance cost — specifically an internal failure cost that results from catching defects before delivery. External failure costs occur when defects reach the customer (warranty claims, liability). Training and inspections/testing are conformance costs (prevention and appraisal respectively). Measurement equipment is also a conformance/appraisal cost. Prevention costs are the most valuable: preventing defects is cheaper than finding and fixing them.

Question 9 of 18

Over the last three sprints, a project manager notices that the same data-validation defect type has appeared in several increments delivered by the agile team. What is the BEST first response?

  1. A.Write a root cause report for the team and assign each developer the fixes for the defects found in their own stories.
  2. B.Have the product owner add a backlog item for every validation defect and rank each one for repair as it is reported.
  3. C.Raise the defect trend in the retrospective so the team can analyze the cause and update its Definition of Done.
  4. D.Plan a hardening sprint before the release in which testers find and remove the validation defects in one pass.
Show answer and explanation

Correct answer: C

The same defect type recurring across increments points to a process gap, and in an agile team the retrospective is where the team itself inspects causes and adapts its practices, such as strengthening the Definition of Done. Writing the root cause report alone and assigning fixes by developer takes ownership away from a self-organizing team and leans toward blame. Adding a backlog item for every defect fixes symptoms one by one without preventing the next occurrence. A hardening sprint relies on late inspection and delays feedback instead of building quality into each increment.

Question 10 of 18

During customer acceptance testing on a predictive project, several deliverables fail because each of the three delivery teams interpreted the same requirements differently. Which action BEST addresses the root cause?

  1. A.Facilitate a session with the teams and customer to clarify the ambiguous requirements and their acceptance criteria.
  2. B.Submit a change request to relax the acceptance criteria, letting the current deliverables pass the next customer test round.
  3. C.Tell the test lead to add acceptance test cases that cover each delivery team's interpretation of the requirements.
  4. D.Escalate to the sponsor for a decision on which team's reading of the requirements the customer should accept.
Show answer and explanation

Correct answer: A

The failures come from ambiguous requirements, so the root cause is removed by getting the teams and the customer to a shared understanding of the requirements and acceptance criteria; any resulting baseline change then goes through change control. Requesting a change to relax the acceptance criteria lowers quality to fit the defect instead of fixing its cause. Adding test cases for every interpretation only detects the divergence and does not settle what the customer actually needs. Escalating to the sponsor is premature because clarifying requirements is within the project manager's authority.

Question 11 of 18

A quality audit on a hybrid project shows that two of the teams have been skipping the peer reviews agreed in the quality management plan for the past month. What is the BEST first response?

  1. A.Report the skipped peer reviews to the functional managers for follow-up in the teams' upcoming performance reviews.
  2. B.Remove peer reviews from the quality management plan and replace them with a lighter self-check done by each developer.
  3. C.Add a final inspection gate before each release to catch the defects that the skipped peer reviews would have found.
  4. D.Meet with both teams to understand why the peer reviews are being skipped and agree on how to make them more workable.
Show answer and explanation

Correct answer: D

Before acting on an audit finding, the project manager should understand why the agreed process is not being followed; the cause may be time pressure, an unworkable review format or unclear expectations. Reporting the teams to functional managers jumps to enforcement and blame before the cause is known. Replacing peer reviews with individual self-checks changes an agreed process without analysis and weakens a prevention activity. A final inspection gate replaces prevention with late detection and leaves the process gap in place.

Question 12 of 18

An agile team's increments consistently pass inspection and meet the Definition of Done, yet end-user satisfaction scores have stayed low for two releases. What is the BEST first response?

  1. A.Tighten the inspection thresholds in the Definition of Done and hold the next increments to a higher technical standard.
  2. B.Work with the product owner to gather direct feedback from end users and learn what value the increments are missing.
  3. C.Request the product owner's formal acceptance of the increments and close out both of the last two releases as complete.
  4. D.Schedule a full end-user satisfaction survey after the final release to learn which features caused the low scores.
Show answer and explanation

Correct answer: B

Passing inspection shows conformance to the agreed criteria, but low satisfaction means the criteria or the backlog do not reflect what users value, so the first step is to learn from users directly with the product owner. Tightening inspection thresholds raises technical conformance without addressing the gap in value. Seeking formal acceptance and closing out the releases because the increments meet the Definition of Done ignores clear evidence that customers are not satisfied. Waiting for a survey after the final release delays feedback that agile delivery is meant to gather early and often.

Question 13 of 18

On a predictive manufacturing project, the project manager added two more test cycles last quarter, but the volume of rework has kept rising. A Pareto analysis with the team shows that most of the rework comes from inconsistent tooling setup at the machining step. What should the project manager do NEXT?

  1. A.Have the process engineer standardize the machining tooling setup procedure and train the operators on it.
  2. B.Add a third extra test cycle before each milestone so the remaining defects are caught before they reach the customer.
  3. C.Extend the Pareto analysis to every other production step before acting on the findings about the machining setup.
  4. D.Submit a change request for more testers who can detect and correct the growing rework faster at each milestone.
Show answer and explanation

Correct answer: A

The Pareto analysis has already located the main source of rework, so the next step is to remove that cause by standardizing the tooling setup at the machining step and training the operators who perform it. Adding a third test cycle repeats the inspection approach that has already failed to reduce rework and raises the cost of quality. Extending the Pareto analysis to every other step delays action on a cause the data has clearly identified. Requesting more testers through a change request only finds and corrects defects faster instead of preventing them.

Question 14 of 18

A hybrid project's first deliverables pass every check against the approved technical specifications, but key business stakeholders say the results are not what they expected. After reviewing the requirements with the stakeholders, the project manager finds that a key approval workflow was never captured in the approved specifications. What should the project manager do NEXT?

  1. A.Present the passed specification checks to the stakeholders and request their formal sign-off on the first deliverables.
  2. B.Direct the team to modify the deliverables right away to match what the stakeholders described in their feedback.
  3. C.Submit a change request to add the missing approval workflow to the approved specifications and the baselined scope.
  4. D.Schedule a full re-validation of all requirements with the stakeholders and pause deliverable work until it is complete.
Show answer and explanation

Correct answer: C

The review has already identified the cause: a needed approval workflow is missing from the approved specifications, so adding it is a scope change that should go through the change control the hybrid project uses for its baselined work. Requesting sign-off on the first deliverables ignores a confirmed gap in what the stakeholders need. Modifying the deliverables right away bypasses that change control and leaves the specifications and baseline out of date. Pausing deliverable work for a full re-validation of every requirement stalls delivery and delays acting on a gap that has already been found.

Question 15 of 18

An agile team publishes defect density and escaped-defect charts every sprint, but the project manager sees that nobody refers to them when planning or improving work. What is the MOST appropriate action?

  1. A.Add cycle time and code coverage to the sprint dashboard so the team has a more complete picture of quality trends.
  2. B.Bring the charts into the retrospective and help the team choose the few measures it will use to drive improvements.
  3. C.Send the sprint quality charts to the sponsor as well and invite leadership to comment on the quality trends at each review.
  4. D.Stop publishing the defect charts and drop them from the sprint routine until the team asks to see them again.
Show answer and explanation

Correct answer: B

Metrics only add value when the team uses them to inspect and adapt, so the project manager should help the team connect a small set of meaningful measures to its retrospective improvements. Adding more measures to a dashboard nobody uses increases noise rather than use. Sending the charts to the sponsor relies on external pressure instead of team ownership and may encourage gaming the numbers. Stopping the charts discards useful data before understanding why the team is not using it.

Question 16 of 18

A supplier on a predictive construction project has met every delivery date, but incoming inspections show the concrete mixes vary in strength from one shipment to the next. What is the BEST first response?

  1. A.Recommend that procurement terminate the contract for cause and source the concrete from the backup supplier instead.
  2. B.Assign project staff to test every incoming shipment and send back each batch of concrete that fails the inspection.
  3. C.Accept the shipments for now and note the strength variation for discussion at the contract's next scheduled review.
  4. D.Ask the supplier to correct the strength variation, citing the inspection results and the contract's quality terms.
Show answer and explanation

Correct answer: D

The contract defines quality requirements as well as dates, so the project manager should use the inspection evidence and contract terms to have the supplier find and correct the cause of the variation. Terminating the contract is premature before the supplier has been given the chance to correct the problem under the agreed terms. Testing and returning every batch depends on inspection and does not stop inconsistent material from being produced. Accepting the shipments and deferring the issue to a later contract review ignores the contractual quality requirements and lets the risk to the structure grow.

Question 17 of 18

After upstream design delays on a hybrid project, the team proposes cutting the planned integration testing from three weeks to one to hold the release date. Analysis with the team shows that no fast-tracking or resequencing option recovers the two weeks, and the sponsor committed the release date to a key customer. What should the project manager do NEXT?

  1. A.Present the sponsor with the quality risk of shorter testing and the date options so the sponsor can decide.
  2. B.Approve the shorter integration testing, trusting the judgment of the team as the people closest to the work.
  3. C.Re-run the schedule analysis with the team to look for another way to recover the two lost weeks of testing.
  4. D.Keep the full three weeks of integration testing and ask the team to work overtime until the delay is recovered.
Show answer and explanation

Correct answer: A

The team has already shown that the schedule cannot absorb the two weeks, and the release date is a commitment the sponsor made to a key customer, so the trade-off between the date and quality risk is outside the project manager's authority. Presenting the quality risk and the date options lets the sponsor make an informed decision. Approving the shorter testing accepts significant quality risk on the team's view alone without involving the person who owns the commitment. Re-running the schedule analysis repeats work that has already found no recovery option. Mandating sustained overtime is not sustainable and still leaves the decision about the customer commitment unmade.

Question 18 of 18

After several defects reached production, the agile team's senior leaders begin asking which developer caused each one, and team members have started hiding issues. What is the MOST appropriate response?

  1. A.Provide the leaders with a breakdown of defects by developer and let their accountability discussions rely on facts.
  2. B.Ask the team to fix the defects quietly and keep minor issues out of the reports that are sent to the leaders.
  3. C.Meet with the leaders to explain how blame suppresses reporting and propose a blameless root cause review.
  4. D.Hold a blameless review with the team only and avoid sharing any of the defect findings with the leaders.
Show answer and explanation

Correct answer: C

Blame is already causing the team to hide issues, which undermines transparency and makes the process causes harder to find, so the project manager should work with the leaders to shift toward a blameless root cause review. Providing defects by developer feeds the blame culture and does not address the process gaps. Keeping issues out of leadership reports reduces transparency and hides real quality risk. Running the review without the leaders excludes the people whose behavior needs to change and leaves the problem in place.

Ready for exam conditions?

Practice these questions with randomized answer order and instant scoring, or take a full domain-weighted mock exam with a real exam timer.

More Process practice questions