PK0-005 Tools and Documentation Practice Question
A project manager wants to identify the most significant causes of delays in a software development project. Which quality tool should she use to prioritize the causes based on the Pareto principle?
⚠ Common exam trap
PK0-005 often tests whether candidates confuse the fishbone diagram (cause identification) with the Pareto chart (cause prioritization) — the key differentiator is the Pareto principle and the 80/20 prioritization aspect.
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
✓
Pareto chart
A Pareto chart is a bar chart that orders causes by frequency or impact, overlaid with a cumulative percentage line, directly applying the Pareto principle (80/20 rule). It helps prioritize the most significant causes of a problem, which is exactly what the project manager needs to identify the biggest sources of delays.
Answer analysis
Option-by-option breakdown
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
A scatter diagram plots two variables to reveal correlation between them; it produces no frequency ranking of causes, so Pareto prioritisation is impossible. It is tempting because it is a recognised quality tool for analysing relationships, and would be correct when testing whether one factor correlates with another, such as defect rate versus code complexity.
- ✓
Pareto chart
Why this is correct
A Pareto chart orders causes by frequency and overlays cumulative percentage, exposing the vital few responsible for most delays. This satisfies the stem's requirement to prioritise causes using the Pareto principle, unlike a fishbone diagram, which only categorises causes without ranking them.
- ✗
Control chart
Why it's wrong here
A control chart tracks a process over time against statistical limits to detect variation; it does not count or rank causes by frequency, so it cannot support Pareto prioritisation. It is tempting because it is a standard quality tool for monitoring stability, and would be correct when determining whether a process is in statistical control.
- ✗
Fishbone diagram
Why it's wrong here
A fishbone diagram organises potential causes by category to explore root causes; it does not rank or quantify them, so it cannot apply the Pareto principle. It is tempting because it is a core quality tool for cause analysis, and would be correct when the goal is to brainstorm and structure possible causes rather than prioritise them.
Go deeper
Related to this question
About these practice questions
One of 954 original PK0-005 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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 CompTIA exam blueprint
This PK0-005 practice question is part of Courseiva's free CompTIA 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 PK0-005 exam.