You have to look at the candidate's overall performance in the interview; not the answer to a single question.
Describing a closure is actually a great example of something many great software developers WON'T know based upon their prior domain experience.
A strong Java or old school C/C++ programmer (yes I know C++11 has closures) may actually be an excellent candidate, but have no idea what a closure is.
I would expect that a front end JavaScript developer, RoR dev, or anyone else "experienced" in a language with some functional support (Scala, Haskell, F#, etc...) should be able to explain a closure.