System Administrator
Interview Questions.
15 practice questions across 13 skills — each with what the interviewer is really listening for. Prepare with intent, not guesswork.
Free · No signup · Grouped by skill
How to use this page
Don't memorise answers. For each question, read what the interviewer is looking for, then practise answering out loud in your own words with a real example. The notes describe strong answers and common red flags — they are for your prep, not a script.
Linux
1 questionA Linux server is running out of disk space. Walk me through how you find and fix it.
IntermediateWhat the interviewer is looking for: Strong answers use df and du to locate the culprit, check logs and deleted-but-open files, and clean up safely. Blindly deleting files without understanding them is a red flag.
System Security
1 questionHow do you approach patching and updates across many servers without breaking things?
IntermediateWhat the interviewer is looking for: Look for testing in staging, staged rollout, maintenance windows, and rollback plans, balancing security urgency with stability. Patching everything blindly or never patching are both red flags.
TCP/IP
1 questionA user reports they cannot reach an internal service. How do you troubleshoot the network path?
IntermediateWhat the interviewer is looking for: Strong candidates work layer by layer — connectivity, DNS, ports, firewall, and the service itself — using ping, traceroute, and telnet/nc. Guessing without isolating the layer is a red flag.
DNS
1 questionHow does DNS resolution work, and how do you debug a DNS problem?
IntermediateWhat the interviewer is looking for: Look for the resolution chain, TTL and caching effects, and using dig/nslookup to trace it. Not understanding caching or the resolution flow is a red flag.
Bash
1 questionHow do you automate a repetitive admin task, and when do you choose Bash versus PowerShell?
BasicWhat the interviewer is looking for: Strong answers automate to reduce toil and error, choosing the tool by platform and complexity. Doing everything by hand repeatedly is a red flag.
PowerShell
1 questionHow do you manage Windows machines at scale with Active Directory and Group Policy?
IntermediateWhat the interviewer is looking for: Look for centralised policy, scripted management, and least privilege. Manually configuring each machine is a red flag for scale.
VMware
1 questionHow do you approach capacity and consolidation with VMware or other virtualization?
IntermediateWhat the interviewer is looking for: Strong candidates right-size VMs, monitor resource contention, and plan for host failure. Over-provisioning blindly or ignoring the noisy-neighbour effect are red flags.
Active Directory
1 questionHow do you design user and permission management to be secure and maintainable?
IntermediateWhat the interviewer is looking for: Look for group-based least privilege, joiner/mover/leaver processes, and auditing. Direct per-user permissions and stale accounts are red flags.
Nagios
1 questionWhat do you monitor to know your systems are healthy, and how do you avoid alert fatigue?
IntermediateWhat the interviewer is looking for: Strong answers monitor the right signals, alert on actionable conditions, and tune thresholds. Alerting on everything until people ignore alerts is a red flag.
Backup and Recovery
1 questionWalk me through your backup and recovery approach and how you know it works.
IntermediateWhat the interviewer is looking for: Look for the 3-2-1 principle, offsite copies, and — critically — regularly testing restores. Untested backups are a serious red flag.
Troubleshooting
1 questionA production server is down and users are blocked. How do you handle the incident?
AdvancedWhat the interviewer is looking for: Strong candidates communicate status, restore service first, then find root cause methodically, and document. Silent flailing or skipping the post-mortem are red flags.
VPN
1 questionHow do you secure remote access for administrators and users?
IntermediateWhat the interviewer is looking for: Look for VPN with MFA, least privilege, and avoiding exposing management ports to the internet. RDP/SSH open to the world is a serious red flag.
Technical Documentation
1 questionHow do you document systems and runbooks so someone else can operate them?
BasicWhat the interviewer is looking for: Strong answers keep current runbooks, network diagrams, and recovery steps accessible. 'It's all in my head' is a red flag for operational resilience.
Behavioural & role-general
2 questionsTell me about the worst outage you handled. What did you change afterward?
BasicWhat the interviewer is looking for: Look for calm handling, root-cause analysis, and systemic prevention. Blaming users or claiming perfect uptime are red flags.
How do you balance keeping systems locked down with letting people get their work done?
IntermediateWhat the interviewer is looking for: Strong candidates apply proportionate security and enable users with safe options rather than blanket blocks. Being the 'department of no' or ignoring security for convenience are red flags.