220-1102 Operational Procedures Practice Question
A junior technician accidentally assigns a help desk ticket to the wrong category in the ticketing system. This causes a delay in resolution because the ticket is not routed to the appropriate team. According to IT best practices, what should the technician do to help prevent similar incidents in the future?
⚠ Common exam trap
Watch out — candidates often choose 'Request additional training' (Option B) because it sounds proactive, but the question specifically asks for what prevents similar incidents in the future, and a knowledge base update is a permanent, scalable solution that benefits the entire team, not just the individual.
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
✓
Update the knowledge base with the correct categorization and a brief explanation
Updating the knowledge base with the correct categorization and a brief explanation is the best practice because it directly addresses the root cause—lack of clear guidance on ticket categorization. By documenting the correct category and the reasoning, the technician creates a reusable reference that helps all team members avoid the same mistake, improving first-level resolution rates and reducing misrouted tickets. This aligns with ITIL's continual service improvement and knowledge management processes, which emphasize capturing and sharing lessons learned to prevent recurrence.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Update the knowledge base with the correct categorization and a brief explanation
Why this is correct
Updating the knowledge base with the correct categorization and a brief explanation is the appropriate corrective action because it creates a persistent reference that guides all technicians when selecting ticket categories. This documented example directly addresses the root cause—unclear categorization criteria—and prevents recurrence by standardizing the decision process. It is immediate, scalable, and aligns with knowledge management best practices in help desk operations.
- ✗
Request additional training on the ticketing system
Why it's wrong here
Requesting additional training on the ticketing system is a reactive measure aimed at the junior technician only, not at the whole support team. Even if the training helps this person, the team still lacks an accessible reference, so other agents may keep mis-categorizing similar tickets. Training schedules are slower than simply updating a knowledge article, and the lessons learned would remain in one person's memory rather than becoming shared institutional knowledge.
- ✗
Submit a change request to modify the predefined ticket categories
Why it's wrong here
Submitting a change request to modify the predefined ticket categories assumes the category list itself is flawed, but the problem is likely that the technician selected the wrong existing category. Category changes are high-impact because they can break reporting, alter SLA compliance, and require retraining of all staff, making this a disproportionate response to a single mis-categorization. A change request should be driven by recurring evidence of missing or ambiguous categories, not one isolated incident.
- ✗
Escalate the ticket to a senior technician and move on
Why it's wrong here
Escalating the ticket to a senior technician resolves the immediate handling but does not fix the underlying procedural gap that caused the bad categorization. Responsibility moves up the chain, and the junior technician misses the chance to learn; future tickets will not improve without a persistent, team-wide reference. The sustainable action is to capture the correct categorization logic in a knowledge base so that recurrence is prevented, not just handled.
Go deeper
Related to this question
Learn chapter
Documentation and Ticketing Systems
Key term
Ticketing system
A ticketing system is a software tool used by IT teams to track, manage, and resolve issues or requests reported by users, ensuring nothing gets lost and everything is handled in an organized way.
Key term
Lessons learned
Lessons learned is the process of capturing, analyzing, and documenting knowledge gained from past incidents or projects to improve future security operations and prevent recurrence of problems.
About these practice questions
This 220-1102 question is part of Courseiva's 925-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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1102 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 220-1102 exam.