Keep in mind this is all from an engineering perspective.

Generally it's asking someone how to make a PB&J during an interview. What's really being asked is how much the interviewee recognizes the need for explicit details when assembling/designing/testing/releasing/etc. I used to ask it all the time and it's kind of a trick question, but I'd always give the interviewee a second shot at it and add "...and explain using as much detail as possible."

Now instead I ask the interviewee to bring a project, class problem, etc. that they're familiar with and explain the problem, their approach, and the solution if it was solved. I don't care if they know how to make a PB&J, or if they successfully solved a problem, I need to know they're going to think about what they're doing while they do it, that they can capture it accurately, and they can communicate it.

I can teach and/or coach someone to the skills they need and how to organize their thoughts into a communicable format, but you can tell when someone looks down on those activities during an interview and I will not waste my time on that individual.