Quick Answer
The answer is the cause-and-effect diagram, also known as the fishbone or Ishikawa diagram. This is the correct tool for root cause analysis of a critical defect because it systematically organizes potential causes into categories like people, process, technology, and environment, allowing the team to visually trace the defect back to its underlying source rather than just treating symptoms. On the PMP exam, this question tests your ability to distinguish quality management tools from the Plan-Do-Check-Act cycle; a common trap is choosing a flowchart or Pareto chart, which track process steps or prioritize issues but do not map causal relationships. For a critical defect in software testing, the diagram helps the project manager brainstorm and isolate technical root causes, such as a coding logic error or integration failure. Memory tip: think of a fish skeleton—each bone is a potential cause, and the head is the defect you are trying to solve.
This PMP practice question tests your understanding of process — managing technical aspects. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A project team is implementing a new software feature. During testing, a critical defect is found that could delay the release. The project manager needs to determine the root cause. Which tool or technique should be used?
Scatter diagram
Why wrong: Scatter diagrams show relationships between variables, not root causes.
Control chart
Why wrong: Control charts monitor process variation, not root cause analysis.
Delphi technique
Why wrong: Delphi technique is for reaching expert consensus, not root cause analysis.
Cause-and-effect diagram
Cause-and-effect diagrams systematically explore potential root causes of a defect.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Cause-and-effect diagram
The cause-and-effect diagram (also known as a fishbone or Ishikawa diagram) is the correct tool for root cause analysis because it systematically maps potential causes of a defect across categories like people, process, technology, and environment. In this software testing scenario, the project manager would use it to brainstorm and visually trace the critical defect back to its underlying technical root cause, such as a coding logic error or integration failure, rather than just observing symptoms.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Scatter diagram
Why it's wrong here
Scatter diagrams show relationships between variables, not root causes.
Control chart
Why it's wrong here
Control charts monitor process variation, not root cause analysis.
Delphi technique
Why it's wrong here
Delphi technique is for reaching expert consensus, not root cause analysis.
Cause-and-effect diagram
Why this is correct
Cause-and-effect diagrams systematically explore potential root causes of a defect.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates confuse root cause analysis tools with quality control tools, mistakenly selecting scatter diagrams or control charts because they associate them with defect analysis, but only the cause-and-effect diagram directly structures the search for underlying causes.
Trap categories for this question
Command / output trap
Scatter diagrams show relationships between variables, not root causes.
Detailed technical explanation
The cause-and-effect diagram works by decomposing the defect into major cause categories (e.g., methods, machines, materials, measurements, environment, people) and then drilling down into sub-causes through iterative brainstorming. In software development, this often reveals hidden issues like incorrect API endpoint configurations, race conditions in multithreaded code, or missing input validation that a scatter diagram or control chart would never expose. A real-world scenario is debugging a memory leak in a microservice: the fishbone diagram might trace it to improper garbage collection settings (environment) or a circular reference in the code (methods).
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the PMP exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Process — Managing Technical Aspects — study guide chapter
Learn the concepts, then practise the questions
Process — Managing Technical Aspects practice questions
Targeted practice on this topic area only
All PMP questions
892 questions across all exam domains
Project Management Professional PMP study guide
Full concept coverage aligned to exam objectives
PMP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PMP questions linked to People — Leading Projects.
Practise PMP questions linked to Process — Managing Technical Aspects.
Practise PMP questions linked to Business Environment — Strategy and Value.
Practise PMP questions linked to Business Environment: strategy and project benefits.
Practise PMP questions linked to PMP fundamentals.
Practise PMP questions linked to PMP scenario.
Practise PMP questions linked to PMP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Process — Managing Technical Aspects — This question tests Process — Managing Technical Aspects — Read the scenario before looking for a memorised answer..
The correct answer is: Cause-and-effect diagram — The cause-and-effect diagram (also known as a fishbone or Ishikawa diagram) is the correct tool for root cause analysis because it systematically maps potential causes of a defect across categories like people, process, technology, and environment. In this software testing scenario, the project manager would use it to brainstorm and visually trace the critical defect back to its underlying technical root cause, such as a coding logic error or integration failure, rather than just observing symptoms.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This PMP practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.