You're presented with a laptop connected to a remote VM, and told "Fix MySQL", or "Rewrite the git history in this repository".
Usually these are simple problems, which have obvious solutions. Every now and again you might get a surprise like an immutable-bit set on a file, or SELinux blocking access to specific files/paths, but the good thing about these kind of "challenges" is that you'll usually also have full google access.
I guess l33tcoding isn't really a thing for sysadmins, but I do appreciate a (fair) simple test like that, especially being given the opportunity to talk through the process.
But i have also heard people say "Oh my god! They asked me to do a debugging exercise - ON PAPER!!!? What were they thinking?!".
Followed by "this code needs refactoring, go nuts, and then let's talk about what you did and why afterwards".