Technology & IT

IT Support Quiz: Test Your Technician Knowledge

25 Questions 13 min

This quiz covers the day-to-day decisions an IT support technician makes when diagnosing user issues: scoping symptoms, isolating root causes, and choosing safe next steps. Expect practical scenarios across Windows/macOS basics, TCP/IP troubleshooting, account access, and maintenance hygiene so you can spot gaps before a help desk shift or interview.

Start Quiz

IT support technician - open toolkit with screwdriver and wrench

Choose quiz length

1Which PC component converts wall AC power into the low-voltage DC power used by internal parts?

2Which storage type uses flash memory and has no moving parts?

3What TCP port does HTTPS use by default?

4In Windows, which built-in command-line tool shows your current IP address, gateway, and DNS configuration?

5What is the main reason technicians boot Windows into Safe Mode?

6Malware that disguises itself as a legitimate app to trick a user into installing it is best described as:

7Which protocol translates human-readable domain names (like example.com) into IP addresses?

8Windows Remote Desktop connections use which protocol by default?

9To apply security patches automatically on a Windows PC, which feature should be enabled?

10A user reports frequent timeouts to a cloud app. You suspect packet loss somewhere between the office and the provider. Which Windows command best helps identify loss along the route?

11A Windows user reports an application crashes immediately on launch. Which tool is most appropriate to check for crash details and related error codes?

12A desktop reboots randomly under load, and no blue screen appears. What should you check first to confirm a likely cause?

13In a small office, users complain about frequent Ethernet collisions on an older shared network segment. Which device best reduces collisions by creating separate collision domains per port?

14You’re asked to give a contractor access to one internal web app only. Which approach best follows the principle of least privilege?

15After an unexpected power loss, a Windows PC boots but files open with errors. Which built-in tool is most appropriate to check and repair the disk file system?

16Several PCs suddenly show IP addresses starting with 169.254.x.x and cannot reach the internet. What is the most likely cause?

17By default, Windows Disk Cleanup removes personal documents such as files in the Documents folder.

True / False

18Windows Safe Mode loads all third-party startup programs so you can see which one is failing.

True / False

19You need to carry multiple VLANs over a single link between switches. Which standard is used for VLAN tagging on Ethernet trunks?

20An employee receives an email claiming to be from IT, asking them to enable macros in an attached spreadsheet to “restore access.” What is the best technician guidance?

21In a Windows domain, you need to enforce a password policy for all users in a specific Organizational Unit (OU). Which tool is typically used to configure and link the policy?

22A Windows workstation feels “slow,” and Task Manager shows high CPU usage. What is the best next step to identify the cause?

23Select all that apply: best practices for patch management in an organization.

Select all that apply

24A site-to-site VPN is up, but large file transfers stall while small pings succeed. Which change most directly addresses an MTU/fragmentation issue?

25After installing a second OS, a PC now refuses to boot and shows a Secure Boot violation. What is the most appropriate next action to restore bootability while keeping security in mind?

Frequent IT Support Troubleshooting Errors (and the Fixes Technicians Use)

Most wrong answers on IT support assessments come from skipping fundamentals under time pressure. These are the patterns that cause the most avoidable misdiagnoses on the job.

Changing multiple variables at once

Installing drivers, rebooting, and changing network settings in one burst makes it impossible to know what actually fixed (or broke) the issue. Fix: make one change, retest, and document the before/after state.

Confusing “no internet” with DNS failure

Users report “internet is down” when only name resolution is broken. Fix: test an IP target first (gateway/public IP), then test DNS (lookup + alternate resolver) before escalating to an ISP outage.

Skipping the simplest physical and account checks

Loose cables, muted microphones, airplane mode, expired passwords, or locked accounts still account for a large share of tickets. Fix: verify power, link lights, Wi‑Fi association, correct SSID/VLAN, and account status early.

Treating symptoms as the root cause

“Outlook won’t open” might be profile corruption, disk-full, authentication loops, or an add-in crash. Fix: reproduce, gather error text/event entries, and isolate by launching safe mode/clean boot or using a known-good profile.

Overlooking permissions and policy

Access issues are often group membership, conditional access/MFA, or share/NTFS rights—not “the server is down.” Fix: check identity, token/MFA prompts, effective permissions, and recent policy changes.

Poor ticket notes and weak escalation

Vague notes (“tried everything”) slow teams down. Fix: record scope, impact, exact errors, steps tried, timestamps, and what changed; escalate with reproducible evidence and clear next hypotheses.

IT Support Technician Rapid Reference: Triage, Network Checks, and Safe Fixes

Printable note: Save or print this section as a PDF for a desk-side troubleshooting reference.

1) Fast triage (first 2 minutes)

Scope: one user vs many, one device vs all, one site vs remote.
Recent change: updates, password reset, new Wi‑Fi, VPN, device move, new peripherals.
Impact: hard stop (can’t work) vs degraded (slow/intermittent).
Reproduce: user steps + exact error text + timestamp.

2) Network “ladder” (common order)

Link/association: cable seated, Wi‑Fi connected, correct SSID, signal strength.
IP layer: IP address, subnet, gateway, DHCP lease time, duplicate IP signs.
Reachability: ping gateway → ping known public IP → ping internal host (as appropriate).
DNS: lookup internal name, then external; compare results with an alternate resolver if policy allows.
Path: traceroute for routing breaks; verify VPN split/full tunnel expectations.

3) Windows quick commands (know what each proves)

ipconfig /all: address, DNS servers, DHCP status.
ping / tracert: reachability vs routing.
nslookup: DNS resolution and which server answered.
netstat -ano: listening ports and active connections (tie to PID).
tasklist /svc: map services to processes.
sfc then DISM (when system file corruption is suspected).

4) Safe repair rules

Back up before destructive steps: profile resets, OS refresh, disk repairs.
Prefer reversible actions: disable add-in, new user profile, driver rollback, restore point.
Change control mindset: note what changed, when, and how to undo it.

5) Ticket note template (copy/paste)

Problem: what fails + error text
Scope/impact: who/what affected
Evidence: tests run + results
Actions: changes made (one per line)
Next: remaining hypotheses / escalation target

Help Desk Role-to-Skill Map: What This IT Support Quiz Reflects on the Job

This quiz targets the skills that show up in real tickets: isolating variables, proving (not guessing) the failure domain, and choosing fixes that minimize risk.

User access and identity tasks

Password resets / lockouts: account state, MFA prompts, token/session issues, basic directory concepts.
Permission requests: group membership, share vs NTFS rights, least-privilege reasoning, documenting approvals.

Endpoint troubleshooting and OS maintenance

Slow computer / crashing apps: CPU/RAM/disk saturation, startup impact, drivers, safe mode/clean boot logic.
Updates and reliability: patch windows, restart planning, rollback awareness, verifying successful installs.
Device issues: printers, audio, webcams—spoolers, default devices, drivers, and connection paths.

Network and connectivity incidents

“No internet” tickets: IP configuration, DHCP vs static mistakes, gateway reachability, DNS vs routing separation.
Wi‑Fi/VPN problems: authentication vs signal vs policy, split-tunnel expectations, captive portals, certificate time drift.

Security-minded support behaviors

Phishing/malware suspicions: containment steps, credential resets, safe evidence capture, escalation thresholds.
Data protection: when to back up before repairs, what “restore” actually returns, and how to avoid overwriting good data.

Service management basics

Ticket handling: triage, prioritization by business impact, crisp notes, and clean handoffs/escalations.
Remote support: guiding user actions, confirming outcomes, and leaving systems in a known-good state.

IT Support Quiz FAQ: Troubleshooting Logic, Tools, and What “Good” Looks Like

How can I quickly tell a DNS problem from a general connectivity outage?

Start with reachability to an IP: confirm the local gateway responds, then try a known reachable IP (internal or public, depending on your environment). If IP reachability works but hostnames fail, you’re in DNS territory (resolver misconfiguration, DNS server down, or blocked queries). If you can’t reach the gateway, focus on link/Wi‑Fi association, VLAN/port issues, or local firewall/stack problems first.

What’s the safest troubleshooting approach when you’re supporting a live user?

Prefer reversible steps that isolate a single variable: reproduce the issue, capture the exact error, then try low-risk actions (restart the app, disable an add-in, test with a new profile, swap a cable/port, renew DHCP). Avoid “shotgun” fixes like reinstalling drivers or clearing caches without evidence, and back up user data before any action that could reset profiles or remove settings.

Which Windows logs and built-in tools matter most for common help desk incidents?

For many desktop issues, Event Viewer (System + Application) plus Task Manager/Resource Monitor explains more than third‑party utilities. Look for service crashes, disk warnings, driver failures, and repeated authentication errors near the reported timestamp. Pair logs with targeted tests (ping/traceroute/nslookup) so you can connect symptoms to a specific layer (device, OS, network, or identity).

How should I prioritize tickets when multiple users report different symptoms at once?

Prioritize by business impact and blast radius: a partial outage affecting many users (network, authentication, shared service) usually outranks a single-device issue. Validate scope with quick checks across at least one known-good device/user. If a shared dependency is failing, shift from “fix one endpoint” to “stabilize the service” and communicate expectations early.

What should I study next if my weak areas are backups or security controls?

If you missed questions about restore points, backup types, or recovery tradeoffs, practice with the scenarios in the Data Backup Assessment Questionnaire. If the misses were around phishing, MFA, or safe containment steps, review the Information Security Quiz for Employees to tighten your security-first decision making during support calls.