I don't really ask people to configure things. I ask if you understand how DHCP works, and how TCP works, how top works (ie info is in proc . . . I volunteer

I don't really ask people to configure things. I ask if you understand how DHCP works, and how TCP works, how top works (ie info is in proc . . . I volunteer laptop at the start of interviews but most people never use it. I try to stray away from asking for a list of facts. Often I will ask a question about making a big change and I want to know how they go about it, is there error checking, is the a list of failures that can be worked later, if it's big scale are things run in parallel, are parallel processes run in a way that would max out the boxes resources? I don't need all of those because everyone answers those questions differently but I want to know how you think and assume you can look up arguments later. Or that I can teach you how to use a man page depending on the level of hire. A huge majority of our stack is proprietary so you won't know how to use it anyway. So if you know how to think and you know how to learn then you should be fine.