Help Desk Priorities & Performance
Tickets & Documentation
Troubleshooting & Communication
100

Taking an hour to solve a problem that should take five minutes can negatively affect a company’s ________.

Reputation

100

When closing a help desk ticket, what word should technicians avoid using by itself instead of explaining how the problem was resolved?

“Closed”

100

Before troubleshooting effectively, the end user and help desk agent need to develop a solid ________ of the problem.

Understanding

200

What does KPI stand for?

Key Performance Indicator

200

How clear should the description on a help desk ticket be?

Clear enough that someone who has not worked on the ticket can understand what is happening.

200

What type of questions should help desk technicians ask when they need more specific details from a user?

Open-ended questions

300

If the people affected by an IT issue cannot do any work at all, how should the support call be prioritized?

High priority

300

 If a help desk ticket cannot be handled at its current support level, what should happen to it?

It should be escalated.

300

When a failure occurs, what should a help desk agent identify before deciding how to fix it?

The probable cause of the failure

400

What type of agreement establishes the acceptable amount of time for addressing help desk calls?

Service Level Agreement (SLA)

400

What is the last step in the problem-solving process?

Documenting the changes made to resolve the problem

400

There may sometimes be a delay between developing a plan to ________ a problem and actually implementing that plan.

Solve

500

A company promises that critical IT issues will be addressed within a specific amount of time. What determines that expected response time?

 Service Level Agreement (SLA)

500

A technician cannot resolve an issue and needs to send the ticket to someone with a higher level of expertise. What should the technician do?

Escalate the ticket

500

If the solution you tried does not ________, you need to know how far back to go before changing your troubleshooting approach.

Work