PMP Process — Managing Technical Aspects Practice Question
You are leading a project to deploy a new enterprise resource planning (ERP) system. The project is in the monitoring and controlling phase. The quality control team reports that a critical module has failed performance testing due to latency issues. The vendor claims the issue is with your network infrastructure. You need to identify the root cause and determine corrective actions. Which tool or technique should you use?
⚠ Common exam trap
The trap here is selecting a tool that shows correlation or monitors variation, such as a scatter diagram or control chart, instead of one that systematically analyzes causation.
Answer choices
Why each option matters
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
In a dispute over performance failure, the project manager needs a structured root cause analysis. The cause-and-effect diagram enables the team to brainstorm and categorize potential causes, leading to identification of the true root cause. This fosters collaboration with the vendor and supports data-driven corrective actions, rather than relying on assumptions or blame.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Control chart
Why it's wrong here
A control chart monitors process stability over time and identifies special cause variation. While useful for ongoing performance monitoring, it does not directly help in root cause analysis of a specific failure. It would show that latency is out of control but not why, making it less suitable for diagnosing the underlying cause in this scenario.
- ✗
Scatter diagram
Why it's wrong here
A scatter diagram shows the relationship between two variables, such as latency and network load. It can indicate correlation but does not establish causation or identify the root cause. In this complex vendor dispute, a more definitive causal analysis is required to determine whether the network or the module is at fault.
- ✓
Cause-and-effect diagram
Why this is correct
A cause-and-effect (Ishikawa or fishbone) diagram is the appropriate tool to systematically explore potential causes of the latency issue, categorizing them (e.g., people, methods, machines, materials, measurement, environment). It helps the team identify and analyze root causes, facilitating a fact-based discussion between your team and the vendor to resolve the dispute.
- ✗
Affinity diagram
Why it's wrong here
An affinity diagram is used to group ideas and data for further analysis, often in quality planning or idea generation. It does not provide the structured cause-and-effect analysis needed to pinpoint the root cause of a performance failure. While it could help organize potential causes, it is not the primary tool for root cause analysis in this scenario.
Go deeper
Related to this question
About these practice questions
This PMP question is part of Courseiva's 820-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
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.