Sure, that's good management - ask the expert.
But this manager didn't want to clarify the question, so that the expert could give a considered answer.
Perhaps the manager already knew what answer he wanted?
There's this estimating technique: it's called "Guess the number the manager wants you to give". It's much less career-limiting than giving an honest answer.
Conversely, if I ask a colleague, however smart, a question but their response is "first I need a 10min infodump on things many of which I should already be aware of", I'm just going to say "nevermind then, thanks" and go ask the colleague who can communicate in a more focused and proactive way. (It's not a very charitable reading of the author's position either. I'd prefer to believe both were acting in good faith but with completely misaligned goals.)
I have fielded plenty of similar questions from technical EMs, and even CTOs, when it's way outside their area of expertise.
I've also seen ICs give similar answers to the author to the mild shock of the manager, who then has to gently respond with something like "well, John mentioned in the standup today that he noticed 10s p99 spikes on the cart page, while investigating what Paula from the BI team reported in the planning meeting yesterday, that abandoned items are up 30% in the past month..."
My react frontend is made up, but my actual example is the CTO (no background in software) suggesting we move our embedded product from linux to android because "our updater is broken and i read that android has a great updater," while the issue was faulty flash chips where the brownout protection bit could not be set.
(Moving from linux to android for an embedded product means you basically have to rewrite absolutely everything since the userland is different, for a stack that is under the control of a single company, and is rarely used outside of mobile devices and automotive. And it still won't fix broken flash chips).
This is an order of magnitude more egregious than the react example I transformed it into, and also why I left the company. If I can't present my expertise and get listened to for such an important decision, there really is nowhere for me to go.
You seem to be very dismissive of people when they opine outside of where you think they are qualified to have opinions, and yet you give opinions where you might not have sufficient perspective.
Moving from linux to android for an embedded product means you basically have to rewrite absolutely everything... Great, that is information the CTO needs to know.
for a stack that is under the control of a single company, and is rarely used outside of mobile devices and automotive.
Here the CTO has more perspective then you do. Is the company about to sign a partnership with an Android shop? Is the company contemplating moving into a new product area? Yes, the ultimate problem would not have been fixed by moving to Android, but that does not make your opinion somehow factually right. Before reacting, try assuming the person making suggestions has valid reasons for making them and try to figure out what those reasons are.