IT Support Quiz: Test Your Technician Knowledge
True / False
True / False
True / False
Put in order
True / False
Select all that apply
Select all that apply
Select all that apply
Put in order
Put in order
Put in order
Select all that apply
Select all that apply
Avoidable IT Support Misdiagnoses (and the Habits That Prevent Them)
Strong technicians aren’t the ones who “know every fix”; they’re the ones who reduce uncertainty fast without creating new variables. These are the most common patterns that derail troubleshooting during interviews and real shifts.
Changing multiple variables at once
Installing drivers, toggling VPN, flushing DNS, and rebooting in one burst hides the true cause and complicates rollback. Fix: make one change, retest, and note the exact before/after state (error text, time, network name, user account).
Treating “no internet” as a single problem
User wording often mixes Wi‑Fi association, IP routing, DNS resolution, and captive portals. Fix: verify link/association, then test gateway reachability, then a known public IP, then DNS lookup.
Skipping identity and policy checks
Login failures and “access denied” are frequently password expiry, lockout, disabled accounts, missing group membership, conditional access/MFA prompts, or device compliance. Fix: confirm the account state and recent policy changes before blaming the app or server.
Not reproducing the issue (or capturing evidence)
“Outlook won’t open” is meaningless without the dialog text, Event Viewer clues, add‑ins, profile state, and disk space. Fix: reproduce once, capture the exact error, and isolate with safe mode/clean boot or a known‑good profile.
Weak escalation notes
Escalations fail when they lack scope, impact, and what’s already been ruled out. Fix: document who/what/where, steps tried, timestamps, and your next hypothesis (for example: DNS vs routing vs auth token).
Desk-Side IT Support Triage Cheat Sheet (Print-Friendly)
Printable note: Save or print this section as a PDF for a desk-side reference during tickets and interview prep.
1) Fast triage (first 2 minutes)
- Scope: one user vs many; one device vs all; one site vs remote; one app vs multiple apps.
- Recent change: updates, new drivers, password reset, new Wi‑Fi/VPN, device move, new peripheral, mailbox migration.
- Impact: hard stop vs degraded (slow/intermittent). Define “can’t work” in measurable terms.
- Reproduce: steps, exact error text/code, timestamp, and any prompts (MFA, certificate, captive portal).
2) Network ladder (diagnose in layers)
- Physical / association: power, cable seated, link lights, Wi‑Fi connected, correct SSID, signal strength, airplane mode off.
- IP config: IP/subnet/gateway/DNS servers; DHCP lease time; signs of APIPA; duplicate IP symptoms.
- Reachability tests (order matters): gateway → known public IP → internal host (if applicable).
- DNS: resolve internal name, then external; compare to an alternate resolver if policy allows; watch for split-DNS with VPN.
- Path: traceroute to identify where routing breaks; confirm VPN split vs full tunnel expectations.
3) Identity & access quick checks
- Account status: locked/disabled/expired password; recent password change not synced across services.
- MFA/conditional access: user prompted? device compliance required? location/risk policy triggered?
- Permissions: group membership; share vs NTFS rights; “effective access” for the target resource.
4) Safe next steps that don’t make things worse
- Change one variable, retest, and be ready to roll back.
- Prefer known-good comparisons: another user account, another device, another network, another cable/port.
- Before reinstalls: check disk space, service status, certificates, time sync, and recent updates.
5) Ticket note template (copy/paste)
Symptoms: … Scope: … Impact: … Environment: OS/build, network, location/VPN … Error: exact text/code … Steps tried + results: … Next hypothesis: …
IT Support Role-to-Skill Map: What the Quiz Scenarios Mirror on the Job
This quiz is organized around the tasks technicians perform daily: triage under time pressure, safe remediation, and clean escalation. Use this map to connect missed questions to the job skill you should practice next.
Intake and triage (frontline help desk)
- Task: turn a vague report (“Wi‑Fi is broken”) into testable symptoms.
- Skills covered: scoping (one vs many), asking discriminating questions, capturing exact error text, identifying recent changes.
Workstation and OS basics (Windows/macOS)
- Task: restore user productivity without destabilizing the device.
- Skills covered: safe mode/clean boot concepts, storage and performance hygiene, driver/update awareness, peripheral troubleshooting, app vs OS isolation.
Connectivity troubleshooting (LAN/Wi‑Fi/VPN)
- Task: determine whether failure is association, IP config, routing, DNS, or upstream.
- Skills covered: “network ladder” testing order, interpreting ping results, recognizing DHCP/APIPA patterns, DNS vs internet reachability, VPN split-tunnel expectations.
Account access and permissions (identity-first thinking)
- Task: resolve sign-in and “access denied” issues efficiently.
- Skills covered: lockout/expiry checks, MFA/conditional access prompts, group membership logic, share vs NTFS permission layers, least-privilege decision-making.
Escalation and documentation (team operations)
- Task: escalate with evidence so the next team can act immediately.
- Skills covered: documenting scope/impact/timestamps, listing tests performed and outcomes, stating a next hypothesis, avoiding “tried everything.”
IT Support Quiz FAQ: Troubleshooting Method, Tools, and What “Good” Looks Like
In troubleshooting questions, what’s the best default approach when the symptom is vague?
Start by scoping and reproducing: determine whether it affects one user or many, one device or multiple devices, and one app or the whole system. Capture the exact error text and timestamp, then change one variable at a time so you can attribute cause and safely roll back.
How do I quickly separate DNS problems from general connectivity problems?
Use a layered test order: confirm link/Wi‑Fi association, then reach the default gateway, then reach a known public IP. If IP reachability works but names fail to resolve, focus on DNS settings, resolver reachability, and split-DNS behavior with VPN rather than assuming the ISP is down.
Why do IT support assessments care so much about “one change, then retest”?
Because the goal is a reliable fix, not a lucky fix. Making multiple changes at once destroys your ability to prove root cause, complicates incident review, and increases the chance you introduce a new issue (for example, breaking VPN routing while “fixing” Wi‑Fi).
What’s the fastest way to handle “can’t log in” or “access denied” scenarios in the quiz?
Think identity-first: verify account status (locked, disabled, expired password), then confirm MFA/conditional access prompts, then check authorization (group membership, role assignment, and effective permissions). If access is to a file share, distinguish share permissions from NTFS permissions and confirm the user is targeting the right resource.
Which adjacent skills should I practice if I struggle with TCP/IP or security-themed items?
If the network-layer questions are the hardest, work through fundamentals like addressing, routing vs DNS, and common troubleshooting commands using the Basic Networking Quiz - Free Practice Questions. If the scenarios involve MFA, suspicious sign-ins, or policy-driven access, the Cybersecurity Basics Quiz helps reinforce the security concepts that appear in real help desk tickets.
What does a high-quality escalation note include for IT support work?
It includes scope (who/what/where), impact, environment (device, OS, network/VPN), exact error messages, timestamps, and a list of tests performed with outcomes. End with the next hypothesis you want the next team to validate (for example: DNS misconfiguration vs conditional access vs service outage).
