Drag steps to the numbered slots on the right, or tap a step then tap a slot.
ITIL4F The ITIL Service Value System Practice Question
Drag and drop the steps of the problem management process into the correct order.
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
1. Detection and logging, 2. Categorization, 3. Root cause analysis, 4. Solution identification, 5. Closure
Problem management starts with detection and logging, then categorization, root cause analysis, solution identification, and closure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
1. Detection and logging, 2. Categorization, 3. Root cause analysis, 4. Solution identification, 5. Closure
Why this is correct
This sequence accurately reflects the ITIL 4 problem management practice, starting with the formal recognition and recording of a problem. Categorization then provides essential context for efficient investigation by grouping similar issues. Root cause analysis systematically uncovers underlying causes, enabling the identification of effective and sustainable solutions before the problem record is formally closed, ensuring long-term service stability.
- ✗
1. Detection and logging, 2. Categorization, 3. Solution identification, 4. Root cause analysis, 5. Closure
Why it's wrong here
This order is incorrect because identifying a solution prior to conducting thorough root cause analysis is a common anti-pattern in problem management. Without understanding the true underlying cause, any proposed solution is likely to be a temporary workaround or address only symptoms, leading to recurring issues and wasted resources. Effective problem resolution demands that root cause analysis precedes solution identification to ensure sustainable fixes.
- ✗
1. Categorization, 2. Detection and logging, 3. Root cause analysis, 4. Solution identification, 5. Closure
Why it's wrong here
This sequence is fundamentally flawed as categorization cannot logically precede the detection and formal logging of a problem. A problem must first be recognized, recorded, and assigned a unique identifier within the problem management system before it can be classified or grouped based on its characteristics. Attempting to categorize an unlogged event would bypass essential tracking and accountability mechanisms, hindering effective management.
- ✗
1. Detection and logging, 2. Root cause analysis, 3. Categorization, 4. Solution identification, 5. Closure
Why it's wrong here
This order is inefficient and deviates from ITIL 4 best practices, as attempting root cause analysis before categorization can hinder the investigation process. Categorization helps to group similar problems, assign them to appropriate teams, and apply relevant diagnostic tools or knowledge articles, thereby streamlining the analysis effort. Skipping this crucial step can lead to disorganized investigations, delayed resolution, and misallocation of resources.
Go deeper
Related to this question
About these practice questions
Courseiva writes every ITIL4F question from scratch — 531 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ITIL4F practice question is part of Courseiva's free PeopleCert 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 ITIL4F exam.