For sysadmin/ops jobs, I want to see debugging ability in addition to programming skill.
I usually ask about HTTP and DNS (for web-focused) or Kerberos/AD logins (for user focused).
There are a lot of moving parts to either of these, so a question like: "You type a web address into a browser, it doesn't load" can turn into questions about the DNS resolver process, system and network config, split horizon, time setup, etc.
Basically, I want to know if they have a grasp of how things all go together, and how to test the individual parts that make up the whole.
More sysadmin / troubleshooter focused person here, and I love this sort of question. It also brings out people who will throw out things like "do a network capture". Then you either get the "well, send it to the network team!" answer or the (much more desirable) "look for X, Y, Z, or something weird in N...".
No, I'm saying that it's used as a blowoff answer for something that sounds important because it's outside of what one in said job would normally do, but when asked about it (to see how generalist the person is) they wave it off as something for another person to handle.
These are questions I remember being asked. But they also asked what experience with servers I have and stuff..
* At which layer things are in the OSI model.
* How to reset AD user passwords.
* What different kinds of servers are for.
* Access port 25 in VLAN1 but not VLAN2 using port forwarding in the firewall
* What ways of securing a DMZ are available in emergencies.
I usually ask about HTTP and DNS (for web-focused) or Kerberos/AD logins (for user focused).
There are a lot of moving parts to either of these, so a question like: "You type a web address into a browser, it doesn't load" can turn into questions about the DNS resolver process, system and network config, split horizon, time setup, etc.
Basically, I want to know if they have a grasp of how things all go together, and how to test the individual parts that make up the whole.