IT Support and Helpdesk Flashcards

Question 1

What is the main purpose of a helpdesk in an organization?

Accepted Answer

A helpdesk is a single point of contact where users report technology problems and ask for help. Its staff receive, record, prioritize and resolve requests so that people can keep working. A good helpdesk also tracks trends, shares solutions and communicates clearly, which reduces downtime and improves the user experience.

Question 2

What is an IT incident, and how does it differ from a service request?

Accepted Answer

An incident is an unplanned interruption to a service or a reduction in its quality, such as an email outage. A service request is a routine, planned ask from a user, such as a request for a new laptop or software access. Incidents focus on fast restoration, while requests follow a standard fulfillment process.

Question 3

What does a service level agreement, or SLA, define?

Accepted Answer

A service level agreement is a formal commitment that defines the service a provider will deliver, including measurable targets such as response time, resolution time and availability. It also sets out responsibilities, reporting and what happens when targets are missed. Clear SLAs help support teams set priorities and give customers realistic expectations.

Question 4

What is a ticket, and why is it important in a helpdesk?

Accepted Answer

A ticket is a record that tracks one user request or incident from opening to closing. It normally holds the reporter's details, a description of the problem, the category, priority, actions taken and the final resolution. Tickets matter because they create accountability, support handoffs, and a history for reporting and recurring problems.

Question 5

What is priority in ticket handling, and how is it usually set?

Accepted Answer

Priority describes how urgently a ticket needs attention, and it is usually set by combining impact with urgency. Impact measures how many people or how much business activity is affected, while urgency measures how quickly a delay would cause harm. A payroll outage affecting the whole company ranks above one user's broken mouse.

Question 6

What is first-contact resolution, and why do helpdesks measure it?

Accepted Answer

First-contact resolution is the share of issues solved during the user's first interaction, without a callback, transfer or escalation. Helpdesks measure it because it usually reflects good knowledge, clear procedures and efficient use of staff time. It also tends to raise user satisfaction, since people dislike repeating their problem to several people.

Question 7

What is a knowledge base, and how does it help support staff?

Accepted Answer

A knowledge base is an organized collection of articles that describe known problems, their symptoms, causes and step-by-step solutions. Support staff use it to resolve issues faster and more consistently, and it avoids rediscovering the same fix. Many organizations also publish selected articles so users can solve simple problems themselves.

Question 8

What does a first-line, second-line and third-line support model describe?

Accepted Answer

A tiered support model divides work by complexity. First-line staff handle common, well-documented requests and act as the initial contact. Second-line staff investigate harder problems that need more skill or access, and third-line specialists, often engineers or vendors, handle the most complex or unusual cases.

Question 9

What is the first step in a structured troubleshooting process?

Accepted Answer

The first step is to identify the problem by gathering information from the user and confirming the symptoms. Useful questions cover what changed, when the issue started, who else is affected, and the exact error message. Reproducing the problem yourself, when safe, is the fastest way to confirm what is happening before you act.

Question 10

What does it mean to establish a theory of probable cause?

Accepted Answer

Establishing a theory of probable cause means forming a reasoned guess about the most likely source of the fault based on the symptoms. Start with the simplest likely explanations, such as a recent change or a loose cable. Each guess should be specific enough to test, so you can confirm or reject it quickly.

Question 11

Why should you change only one variable at a time during troubleshooting?

Accepted Answer

Changing only one variable at a time lets you see which action actually fixed the problem. If you change several settings together and the issue disappears, you cannot tell which change was responsible. Recording each step also keeps the troubleshooting trail clear for you and for any colleague who takes over the ticket.

Question 12

What is the purpose of isolating a fault by dividing a system into parts?

Accepted Answer

Fault isolation narrows the search by testing parts of a system separately until the failing component is found. For example, when a computer cannot reach a website, you can check the device, the local network, the router and the external service in turn. This divide-and-test approach avoids guessing and saves time on complex problems.

Question 13

How should you verify that a fix has actually resolved the issue?

Accepted Answer

Verification means confirming the original symptom no longer occurs under the same conditions the user described. Ask the user to repeat their normal task, and check logs or status indicators. Do not close the ticket until the user agrees the problem is solved, because a fix that only hides the symptom will return later.

Question 14

What is a workaround, and how does it differ from a permanent fix?

Accepted Answer

A workaround is a temporary method that lets a user continue working while the underlying cause remains unresolved. For example, a user might print to another printer for now. A permanent fix removes the root cause, so the problem should not return. Document workarounds and track them until a real solution arrives.

Question 15

What is root cause analysis, and when is it worth doing?

Accepted Answer

Root cause analysis is the process of tracing a recurring or serious problem back to its underlying origin, not just its symptoms. It is worth doing when issues repeat, outages are costly, or quick fixes fail. The outcome is a preventive change such as a patch or revised procedure.

Question 16

What is a rollback, and when would a technician use one?

Accepted Answer

A rollback returns a system, application or configuration to its previous known working state, usually after a change or update causes a failure. Technicians use it when a change breaks something and the fastest safe option is to undo it. Before making changes, staff should record the current state so a rollback is possible.

Question 17

What are the first checks to make when a computer will not start?

Accepted Answer

Start by confirming that the power source works, the power cable is secure, and the power button and indicator lights respond. Check that any external monitor is connected, since a blank screen can look like a dead computer. If the machine shows no signs of life, escalate suspected hardware faults to the appropriate team.

Question 18

What is the difference between hardware and software in a support context?

Accepted Answer

Hardware is the physical equipment, such as computers, monitors, printers, keyboards and network switches, that you can touch. Software is the programs that run on that equipment, including operating systems and applications. Support staff must diagnose both, because a fault can come from a failing part or from a corrupted or misconfigured program.

Question 19

Why is it important to back up user data before reinstalling an operating system?

Accepted Answer

A reinstall usually erases the existing system partition and may remove files, profiles or settings stored on the same drive. Backing up user data protects against permanent loss if something goes wrong during the process. Confirm the backup opens and important files are present before wiping anything.

Question 20

What does a driver do, and why can an outdated driver cause problems?

Accepted Answer

A driver is software that lets the operating system communicate with a specific hardware device. An outdated or incompatible driver can cause crashes, poor performance, lost connections or missing features after an update. Support staff should check the device manager or vendor source for the correct version and confirm the change fixed the fault.

Question 21

What is the purpose of a standard software image in desktop support?

Accepted Answer

A standard image is a prepared, tested configuration of an operating system and approved applications that can be deployed to many devices. It speeds up setup, keeps machines consistent, and reduces the number of unique faults that support staff must handle. Updating the image on a schedule keeps the fleet secure and predictable.

Question 22

How do you check whether a printer problem is caused by the device or the computer?

Accepted Answer

Test the printer from a different computer, and test a different printer from the affected computer. If the printer fails for everyone, the device, its network connection or its queue is the likely cause. If only one computer fails, check its driver, print queue, and whether its connection to the printer is configured correctly.

Question 23

What is a patch, and why should support staff apply patches promptly?

Accepted Answer

A patch is an update that fixes defects, closes security holes or improves compatibility in existing software or firmware. Prompt application reduces the window in which attackers can exploit known weaknesses. Staff should still test patches on a small group first, since updates can occasionally break a working configuration.

Question 24

How should a technician handle a user's data and privacy during device repair?

Accepted Answer

Technicians should access only what the repair requires, avoid browsing personal files, and never copy data to unapproved storage. Where a backup is needed, use the approved method and keep data within security controls. Document what was accessed and why, and follow the organization's data handling policy and any legal requirements that apply.

Question 25

What is an IP address, and what does it identify?

Accepted Answer

An IP address is a numerical label assigned to a device on a network so that traffic can reach it. It identifies the device's location on the network, much as a postal address identifies a house. Many devices receive addresses automatically from a DHCP server, while others use fixed addresses that staff configure manually.

Question 26

What is the difference between a switch and a router?

Accepted Answer

A switch connects devices within the same local network and forwards data frames to the device that needs them. A router connects different networks, such as a home or office network and the internet, and decides where packets should travel. Many home devices combine both roles, so staff should identify which function is failing.

Question 27

What is DNS, and what happens when it fails?

Accepted Answer

DNS, the Domain Name System, translates names such as website addresses into IP addresses that computers use to connect. When it fails, users often see a site cannot be found, even though the site is running. Staff can test by connecting to the same site via its IP address.

Question 28

What does the ping command test, and what are its limits?

Accepted Answer

Ping sends test messages to a target address and reports whether replies come back and how long they take. It shows basic reachability and latency. However, many systems block ping, so a failed ping does not always mean the service is down, and a successful ping does not prove an application works.

Question 29

What is a default gateway, and what happens if it is misconfigured?

Accepted Answer

A default gateway is the router address that a device uses to send traffic to destinations outside its own local network. If it is misconfigured, the device may reach local machines but fail to reach the internet or other networks. Compare the gateway setting with the router's actual address to confirm it is correct.

Question 30

What is a VPN, and why might a remote user need one?

Accepted Answer

A VPN, or virtual private network, creates an encrypted tunnel between a device and a private network over the public internet. A remote user may need one to reach internal systems not exposed to the internet. Support staff often check credentials, the client version and whether the local connection allows the tunnel.

Question 31

What is network address translation, and why do home networks use it?

Accepted Answer

Network address translation, or NAT, lets many devices with private addresses share one public address when they reach the internet. Home routers typically use it, so all household devices appear externally as a single address. NAT also means devices on the network are not reachable from outside unless a rule is set up for them.

Question 32

What information should you collect before escalating a network fault?

Accepted Answer

Collect the affected device's IP address and host name, the time the problem started, and the exact error messages. Note which sites, applications or servers fail, and whether others on the same network are affected. Also record the tests you have already run and their results, so the next engineer does not repeat them.

Question 33

What is escalation, and when should a ticket be escalated?

Accepted Answer

Escalation means passing a ticket to a higher level of support, a specialist team or a manager because it needs more skill, access or authority. Escalate when the issue exceeds your skill or authority, an SLA is at risk, or security is involved. Good escalations include full notes so the next person can continue.

Question 34

How should a technician communicate a problem and its status to a user?

Accepted Answer

Use plain language, avoid unexplained jargon, and explain what is happening in terms of the user's work. Confirm the issue in your own words, give a realistic time estimate, and say what you need from them. Update the user at agreed intervals so they know the ticket is not forgotten.

Question 35

What is a major incident, and how is it managed differently?

Accepted Answer

A major incident is a severe disruption with significant business impact, such as a company-wide outage, needing rapid coordination. It is managed by a designated incident lead who coordinates responders, and by frequent, clear updates to stakeholders. Once service is restored, the team completes a review to understand what happened and prevent recurrence.

Question 36

What belongs in a good closure note when resolving a ticket?

Accepted Answer

A good closure note states the root cause if known, the actions taken, the final result, and confirmation from the user. It should be specific enough that a colleague could repeat the fix or understand the history without contacting you. Avoid vague entries such as fixed or done, since they teach no one anything.

Question 37

What is change management, and why do support teams follow it?

Accepted Answer

Change management is the process of planning, reviewing, approving and recording changes to systems so that disruption is minimized. Teams follow it because unplanned changes are a common cause of incidents, and an approved record makes it easier to roll back or investigate problems. Even small updates should go through the agreed process.

Question 38

What is the purpose of asset management in IT support?

Accepted Answer

Asset management tracks the hardware and software an organization owns, including where each item is, who uses it, its configuration, warranty status and license position. Accurate records help support staff locate devices quickly, plan replacements, and avoid breaching software license terms. Without them, troubleshooting and budgeting become much harder.

Question 39

What is a service catalog, and what is its goal?

Accepted Answer

A service catalog lists the services users can request, such as new accounts or software installs, with expected delivery times. Its goal is to make requests easier to find and submit, and to set clear expectations about what will happen. Catalogs also reduce unnecessary tickets, because users can see what is standard and self-service.

Question 40

What is customer satisfaction feedback, and how can support teams use it?

Accepted Answer

Satisfaction feedback is information gathered from users after a ticket closes, often through a short survey or rating. Teams can use it to spot patterns, such as repeated complaints about response time or unclear explanations, and to coach staff. Feedback should lead to action, and users should hear when their comments led to change.

IT Support and Helpdesk Flashcards

1Helpdesk Fundamentals

2Structured Troubleshooting Methods

3Hardware and Software Support

4Networking Basics for Support

5Service Management and Communication

Learning Resources