How to prepare for the Provyn IT Support assessment

What the assessment is testing

The IT Support assessment is built around the work of a first- or second-line help desk role. It is not a certification syllabus and it does not test trivia about one vendor's menus. Most questions describe a ticket or a situation and ask what you would do, in what order, or what a symptom tells you.

Each attempt draws questions from four areas in proportion: troubleshooting method, OS and network fundamentals, identity, access and security hygiene, and customer communication. Your credential shows a separate result for each area, so a recruiter can see that you are, say, strong on networking and still developing on ticket handling.

Troubleshooting method

The questions here reward a method more than a memory. Expect to put troubleshooting steps in order, to pick the most useful first question for a vague report, and to say what a test result rules in or out. A good habit to practise: before changing anything, ask what the user was trying to do, what they saw, when it started and whether anyone else is affected.

Two ideas come up repeatedly. First, change one thing at a time and re-test, otherwise you can't tell which change fixed the problem. Second, swap in a known-good part to split the problem in half: if the laptop works on a colleague's dock, the laptop is fine and the fault is in the path you swapped out.

Knowing when to escalate is part of the method. A strong escalation says what the symptom is, what you've ruled out and why the fix needs another team, and the user is told what happens next.

OS and network fundamentals

You should be comfortable reading the output of ipconfig (and ifconfig or the Network settings pane on a Mac), and knowing what a self-assigned 169.254 address, a missing default gateway or a failing DNS server looks like from the user's side. Know the everyday commands for checking and refreshing network settings, and the default ports of services that firewalls and VPNs commonly block.

On the operating-system side, expect questions on safe recovery after a bad update or driver, freeing disk space without breaking anything, and which built-in macOS and Windows tools to reach for. The emphasis is on the safest effective step, not the most dramatic one.

Identity, access and security hygiene

Help desks are a favourite target for social engineering, so several questions put you on the phone with an urgent, important-sounding caller. The right answer is always to follow the verification process; a real executive would rather wait five minutes than lose their account. You should never ask anyone for their password.

Expect questions on least privilege (giving the access needed for the task and no more), what to do when someone reports typing their password into a suspicious page, what repeated unexpected MFA prompts mean, and how leavers should be handled on their last day.

Customer communication and the written replies

A few questions ask you to write a short reply to a ticket or describe how you'd work an incident, usually in about 150 words. These are graded against a published rubric: points for the specific things a good reply does, such as acknowledging the problem, giving accurate status, stating the next step and closing the loop, and deductions for things like putting a password in a ticket.

Written answers are graded by an automated grader that checks each one twice, independently. When the two checks disagree or either is unsure, a person grades it. Write the way you would to a real user: short, specific and in plain words. Length earns nothing on its own.

Priority questions ask you to rank tickets by impact (how many people, how critical the work) and urgency (how soon it hurts). Ticket-note questions reward notes that let the next person carry on without asking the user to repeat themselves.

Three-day prep plan

Day one: work through the practice set at /assess/it-support/practice, then walk through a structured troubleshooting method out loud on three problems you've fixed before. For each, say what you'd ask first and what each test would rule out.

Day two: on your own machine, run the basic network commands and read every line of the output. Break things safely (switch off Wi-Fi, set a wrong DNS server on a test machine) and note what the user would see.

Day three: write three short replies to imaginary tickets: a frustrated user, a delayed fix and a new starter who isn't set up. Check each against the rubric points above. Then take the assessment from /assess/it-support when you have fifty uninterrupted minutes.