Honestly, good interviews are a conversation. You can get more relevant information by having a simple conversation and trying to understand the individual rather than quizzing them. I’ve made a lot of my best technical hires by having a conversation for an hour and doing no deliberate technical/coding interviews. Given the context of the conversation it tends to naturally focus on more technical topics. You can typically get a good read on things like passion and curiosity and whether they value things you find beneficial for the organization/position. Sometimes a less knowledgeable but more hungry/passionate candidate can be a better hire. I very rarely go into an interview with prepared questions.

My vote: these are terrible interview questions.

I can only remember having those strict questions a single time (not counting applications to internships during studies), I have turned them down, I did not consider them a good fit for me, partly because of that, and also because they had a single “openspace” office with a huge monitor displaying a realtime ranking of “productivity metric”…

My current employer just sat down with me, offered a soft drink and we talked. Yes, they had some questions as conversation starters, but there was no “right” or “wrong” answer to them. This was the rough procedure about everywhere where I applied since failing studies.