β All study guides Β· Technical & Trades
Technical reasoning, troubleshooting, networking concepts, and systems thinking for IT civil service titles.
12 track practice questions in the bank Β· Free 25-question practice test included below.
Take Free Practice Test βOverview
IT Specialists keep city offices and systems running: helping users with computers and accounts, setting up hardware, keeping networks and data safe, and solving problems when technology stops behaving. The work is equal parts technical skill and people skill β you need to understand the systems and explain them in plain language.
The exam tests technical reasoning more than memorized facts: how to work through a problem step by step, how networks and systems fit together, how to handle data safely, and how to serve users professionally. It is a multiple-choice exam. You do not need to be a programmer to pass β you need a solid, practical understanding of computers, networks, and troubleshooting.
Use this guide to build your method first β a reliable troubleshooting sequence you apply to every scenario β then learn the key terms and concepts. Work the practice questions and keep a mistake log: the same reasoning errors come up again and again until you catch them.
What the exam typically tests
Troubleshooting method
Questions present a user problem β a computer that will not start, a printer that will not print β and ask for the best first step or the next step. The correct answer follows a logical method: gather facts, check the simplest cause, then work toward the complex one.
Networking basics
Expect questions on how devices connect: the roles of modems, routers, switches, and access points, wired versus wireless connections, and what IP addresses, DNS, and DHCP do. You need the concepts, not vendor-specific setup steps.
Hardware and software fundamentals
Questions cover the hardware and software of a workstation: CPU, memory, storage, operating system, and common applications, and how to set up, update, and support them.
Security and data protection
You will be tested on keeping data and systems safe: strong passwords, multi-factor authentication, updates, firewalls, antivirus, phishing, and β most importantly β backing up data and testing the backup.
User support and communication
Scenario questions test professional judgment: how to handle a frustrated user, how to explain a technical fix in plain language, when to escalate, and how to document what you did.
Systems thinking
Questions cover how systems fit together: how a request travels from a user's computer to a server, what happens when a service is down, and how to prioritize when several users have problems at once.
Topic checklist
Work through this list honestly β drill the items you cannot do yet.
- β State a troubleshooting sequence: identify the problem, gather information, test the simplest cause, fix, verify, and document.
- β Explain what a user should be asked first when something stops working: what changed, when it started, and who is affected.
- β Describe the role of a modem, router, switch, and Wi-Fi access point in a small network.
- β Explain what an IP address, DNS, and DHCP do, in one sentence each.
- β Describe the difference between a wired and a wireless connection and when each is the better choice.
- β Explain the difference between backing up and archiving, and why backups should be tested.
- β List the signs of a phishing email and the correct response to one.
- β Explain what a firewall and antivirus software do, and why updates matter.
- β Describe the steps to set up a new workstation: account, software, updates, and testing before handover.
- β Explain what to do when a user cannot log in, in order: verify the account, check the password, check the account status, then escalate.
- β Describe good password practice and how multi-factor authentication protects an account.
- β Explain how to communicate a fix to a non-technical user clearly and confirm it worked.
How to prepare
Ticket triage drill
Take five support tickets a day β a printer that will not print, a user who cannot log in, a slow computer β and write the first three steps you would take, in order. Good looks like gathering information and checking the simple cause before any repair or reinstall.
Network sketching
Draw a small office network from a written description: a modem, a router, a switch, and six workstations. Label each device and what it does. Do two a week until you can sketch it from memory and explain the path data takes.
Term flashcards
Make cards for key terms β IP address, DNS, DHCP, firewall, VPN, backup, phishing β each with a one-sentence definition in your own words. Review ten cards a day until the definitions come without thinking.
Plain-language explanations
Practice explaining a technical fix in plain language, as if to a non-technical colleague, in three sentences or fewer. Do one a day. Good looks like a clear explanation with no jargon and a check that the fix worked.
Mistake log review
Work through the practice questions in the bank, and after each wrong answer write one sentence explaining why the correct answer is right. Review your notes the next day β good looks like fewer repeat mistakes each week.
Common mistakes to avoid
- β Jumping straight to a reinstall or a system wipe before checking the simple cause β a loose cable, a wrong password, a full disk. The correct answer is almost always the least drastic step that could fix it.
- β Skipping the information-gathering step in troubleshooting. Asking what changed and when is not wasted time β it points at the cause.
- β Confusing similar network terms, such as DNS and DHCP, or a router and a switch. Learn each one in your own words and the mistakes stop.
- β Forgetting to back up or to warn the user before a risky step. In scenario questions, protecting data comes before fixing the problem.
- β Choosing the most technical-sounding answer. Exam questions reward the methodical, safe, user-friendly answer, not the cleverest one.
- β Ignoring the human side: a frustrated user is not a technical problem, but how you treat them is tested. Acknowledge, explain in plain language, and confirm the fix worked.
Exam day strategy
- β Arrive early with the identification and materials your exam notice asks for, and leave yourself extra travel time.
- β When a troubleshooting question gives a list of symptoms, read them all before choosing β one small detail usually rules out the tempting wrong answer.
- β Talk through the scenario in your head: what did the user do, what changed, what would you check first? The answer that follows the method is usually right.
- β Do not skip the boring answer. The correct fix is often the simple one β restart, check the cable, verify the account β not the most technical one.
- β Do not leave questions blank. Eliminate the clearly wrong choices, make your best choice, and move on β you can return to flagged questions if time allows.
- β On scenario questions about users or data, choose the answer that is safest for the user's data and the most professional in tone.
Sample questions
Try these 3 sample questions from the practice bank. The correct answer is marked β read the explanation even when you get one right.
Sample 1 Β· Problem Solving
A user reports that her monitor shows nothing at all. What is the best first step?
- A.Reinstall the operating system immediately
- B.Replace the monitor with a new one
- C.Check the power and cable connections, then ask what changed β Correct answer
- D.Wipe the hard drive and start over
The method is: identify the problem, gather information, check the simplest cause first, then work toward the complex one. Reinstalling the system or replacing hardware before checking the cable or the power skips the cheap, common causes.
Sample 2 Β· Problem Solving
Twenty users in the same office all lose access to a shared drive at the same time. What should you investigate first?
- A.Reinstall the software on every computer
- B.Ask each user to change their password
- C.Check each computer's cable one by one
- D.Check the shared network or server that all users depend on β Correct answer
When many users are affected at once, the problem is usually shared infrastructure β the network, a server, or a service β not each user's computer. Checking one computer's cable or password first wastes time when the pattern points elsewhere.
Sample 3 Β· Problem Solving
A user must transfer a very large file reliably, but the Wi-Fi connection keeps dropping. What is the best recommendation?
- A.Move the computer closer to the router and hope the signal improves
- B.Restart the file server every time a transfer fails
- C.Use a mobile hotspot instead
- D.Connect the computer to the network with an Ethernet cable β Correct answer
A wired connection is generally faster and more stable than Wi-Fi, so for a large, reliable transfer it is the better choice. Moving closer to the access point helps Wi-Fi, but it does not beat a wired connection for reliability.
Official sources
The exam announcement (Notice of Examination) is the final authority for the exam you are taking. Always check it for the exact subjects tested, eligibility requirements, and exam procedures, since details can differ between titles and exam administrations.
Take Free Practice Test β 25 questions, 35 minutes ββ Back to all study guides Β· My progress dashboard
Important disclaimer
All questions on NYCExamPrep.com are original practice questions written for study purposes. They are not official DCAS questions, and this site is not affiliated with the NYC Department of Citywide Administrative Services (DCAS) or the City of New York.