It bears repeating: good interview(er)s will try to determine how you think, not your end result. I do a decent amount of interviews (maybe 2-3 a month), and we by and large are looking for people who can think through a problem, defend a solution, ask good questions, not give up, and appear to be cool to work with. That's it. Some of these questions are great, fundamental CS stuff that I would expect any engineer to have in their back pocket, but some are trivia. Trivia is great, but if you dont't know it I wouldn't hold it against you. I guess my point is to relax. If you thought about some of these things and answered them, great. You're better prepared for next time. Memorizing answer sheets doesn't help in the long run

> good interview(er)s will try to determine how you think,

I can say up front: I don't usually do my thinking at the interviews.

Oh, if only I could upvote a million times...

But doesn't all this imply that I have to get the answer at least right?

No. good wrong answers are just as valuable in seeing your thought processes in action.

This, of course, assumes a good interviewer. If you're dealing with HR-type people then you're screwed anyway unless you play buzzword-bingo.