However, if your position is "I believe you want one specific textbook answer to the problem from me, and I refuse to do anything at all instead of risking what I think the interviewer would see as incorrect, even partially," you'd be at a wrong interview: the hidden goal is "let's find some technical problem to talk about, we wish to see an approximation of your problem-solving skills; if that approximation is 'freeze indecisively,' that would hardly solve any problems." If you see making any mistake as a threat (instead of going back-and-forth to an optimal solution), you would burn out on the actual technical challenges of the job within a month - literally none of them had a single, perfect, by-the-book solution, each needed to be iteratively developed; cramming the Right Exam Answers wouldn't have helped you on that job, as there weren't any.

Edit: perhaps such person would feel better in a tester/QA position, but does not really strike me as fit for developing (development's usual cycle of trying many things, finding that many of them are not applicable and trying something else, seems like outright torture for someone who needs to have the perfect answer right from the start). Therefore, both sides would find out early, at the interview; in this respect the question would serve its purpose well.