100-140 · Question #56
What is the purpose of a queue management system for a help desk?
The correct answer is B. It ensures that customer issues are addressed fairly and timely.. Queue management systems in help desks exist to ensure all customer issues receive prompt and equitable attention.
Question
Options
- AIt ensures that customer issues are addressed based only on issue complexity.
- BIt ensures that customer issues are addressed fairly and timely.
- CIt allows clients to choose their place in the queue.
- DIt allows technicians to choose which ticket they want to complete.
How the community answered
(37 responses)- A8% (3)
- B70% (26)
- C3% (1)
- D19% (7)
Why each option
Queue management systems in help desks exist to ensure all customer issues receive prompt and equitable attention.
Queue management does not route tickets based solely on complexity - it considers multiple factors including time submitted, priority level, and SLA agreements.
A queue management system organizes incoming tickets so that issues are handled in a structured, fair manner - typically by priority, submission time, or SLA requirements. This ensures no ticket is overlooked and customers receive timely responses, balancing urgency with fairness across all requestors.
Clients do not select their own position in a help desk queue; placement is determined by system rules such as ticket priority and submission time.
Technicians are generally assigned tickets by the queue system according to workload and priority, not by personal selection, which would undermine fair and timely service.
Concept tested: Help desk queue management system purpose
Source: https://www.comptia.org/certifications/a
Topics
Community Discussion
6Blueprint sub-domain: IT Support Concepts, specifically help desk operations and ticket management. Memory hook: think of queue management as the "fairness engine" that keeps service consistent and prevents any single ticket from being ignored or jumped. Correct answer is B. A queue management system exists to organize incoming requests so that every customer issue is handled in an orderly, equitable fashion and within a reasonable timeframe, not to give technicians or clients control over sequencing, and not to sort solely by complexity.
Good framing, Priscilla, and worth adding that queue management also ties directly to SLA compliance, since the timestamp and priority tracking built into the system is what lets a help desk supervisor catch a ticket approaching its resolution deadline before it actually breaches, which is a detail that shows up in exam distractors more than people expect.
I kept second-guessing B thinking complexity had to factor in, but "fairly and timely" covers exactly what queue management is designed to guarantee.
Right, the complexity piece lives in the scheduler algorithm under the hood, not in the service guarantee that queue management is promising to each flow.
Nailed B right away, queue management is pure fairness plus SLA discipline. On my 100-140 sitting back in 2019 they dressed this up with a scenario about a flooded ticket system but the answer was always the same: B keeps things fair and timely, nothing more.
Good point on the scenario dressing, Sam, though I'd add that the group flagged one wrinkle worth keeping in mind: when a question layers in priority tiers or VIP SLAs, pure FIFO fairness gets bumped and you have to weigh which constraint the stem is really testing, so reading for that signal before locking in B (or whatever the fairness pick is) saved a few of us from the trap version of this question.