OK you win :D
Just finished Cisco academy for the second time(had to do it again as part of my degree) and because it's such an integral part of the course I just forgot it's not exclusive to cisco. Got indoctrinated!
Anyway you probably have enough suggestions to last you a few interviews!
2. Am guessing they will have another pc to hand to see what subnet the current network is on or how would they know what subnet mask to set it to ?
these things have that association with 'cisco' via the ccna for many, many people.
if this vacancy is for a part-time position and the pay is commensurate with having applicants with limited or no experience, it doesn't seem particularly fair to expose them to stuff that they may not have done previously and weeding out people based on prior knowledge, and more importantly knowing the ins and outs of subnetting isn't important for a junior position.
At my first IT job i didn't know the ipconfig /release and /renew commands - ping was about the only command i knew, joining domains, net use commands all that shit i didn't know.....i watched more senior officers use ipconfig as the most common method to first troubleshoot ip address/dhcp issues at the client side. Did i have a thorough understanding of dhcp did i even know how to setup a basic dhcp range for a dhcp server.....no. similarly i didn't know anything about subnetting beyond knowing what subnet values the organisaiton i worked for used. that's all i needed to know for what i was there for.
the role of a junior tech is about learning on the job and in many cases gaining the practical understanding to aid a better grasp of theory later. not the other way round. If you can find someone with more of a headstart then great, but it's by no means the end of the world to give someone able and eager to learn the opportunity.....people have to start somewhere. ofcourse if given details of the task beforehand could be a useful guide to distinguish people eager to research and able to use their initiative to solve a problem from those who can't be asked.
To be honest I would get a PC, disconnect the HDD, the CD drive, the RAM, molex connectors etc. Pretty much everything and see if they are capable of been calm and collective and working out where they go.
I know it is all plug and play so to speak and you can see where it fits, but if they just calmly plug it all back in and get the machine to boot (or close to booting) you have your trainee.
As you want someone who can remain calm under pressure and has common sense.
In a desktop environment, ask them where to look for network connections, printers etc.
Then up it a bit and ask how to find out the ip address of your machines (cmd prompt) and how to share a folder.
If they don't know this, ask them to find out how on the internet.
Also you could ask them to try finding something more in depth using the internet if they knew how to find the ip address and see if they can find what you're looking for. All basic stuff with a bit of medium stuff to see if they have any experience.
If you want something written, then stick with the suggested priority questions already posed to you.
I've been doing stuff like this for years but, while I can sit down and work it out, it's a lot easier to find a subnet calculator on the web and use that. In a real job, you'd always have access to web based info so checking to see if someone can use that seems reasonable.