I'd suggest, a suitable English term might be ...
Ambiguous or Ambiguous question.
Hmm... ambiguous: open to multiple interpretations. That's not it, because the point is that the question itself is incorrect, not that it can be interpreted incorrectly. In face-to-face, I can often infer the correct interpretation of ambiguous questions –– like "When you were carrying that TV yesterday, did you notice the friendly squirrel at front? Did you bring it inside okay?" typically "it" referring to the TV, and not to the squirrel. In written text, it is similarly common for the exact interpretation to be inferrable from the surrounding context, often subsequent text, leaving the interpretation in a Schrödinger state for a paragraph or two.
To be clear, I'm referring to questions like "Why isn't there any solutions to x*x - 2.0 = 0?", when the asker is really asking why their C code using the float type (float x = sqrtf(2.0f); float y = x*x - 2; if (y == 0) printf("Okay!\n"); else printf("Fail!\n");) fails. I indeed do occasionally answer this kind of questions, often with a snarky initial bite to get the OP out of the passive funk (indicated by the, uh, "inane" question they posed?), followed with actual useful help.
And also questions like "I want to fix this engine using these two q-tips and a crow feather", or their programming or engineering or electronics equivalent. These are super-constrained so that no realistic solution is possible, unless you start by "First, trade one of the q-tips for at least two rubber strings no less than four inches in diameter", and describe the next thousand or so steps in detail.
(And yes, I kinda like "inane question" even better than "wrong question", because its dictionary definition fits like a finger in a nostril. It's just that I don't see it used in everyday speech, so I think it might be perceived a bit snotty.)
But you don't know if the question is incorrect or not (with absolute 100% certainty), that in itself, maybe a considerably harder question/problem to solve. Hence the term ambiguous.
An expert on C, on this forum, may take one look at it, and say something like, "Since version xyz.123...... of the C standard, that (hypothetical, no connection to the C code you just mentioned) expression is always defined as ...".
Or later in the job interview, they might say, that the question was purposely created to have no definitive exact answers. In order to make sure the possible future employee, is confident enough to simply say "They don't know the answer", or the question is ambiguous or badly formed (incorrect question).
It might be that (the reader of the question), missed some additional information/clues. Which made the question answerable. E.g. A schematic, which says all resistors are 1%, 0.25watt metal film, unless stated otherwise.
In other words, MAYBE the question is faulty, but it could also be that the reader (of the question), is simply mistaken or lacking experience, which would make the question unambiguous to them. So simply saying the question is incorrect, is NOT that simple.
So I still think the term, ambiguous, is probably best.
Real Life Example (from memory, so might be wrong, also I can't 100% remember the original question, so I may have changed it a fair bit).
There was an online electronics test quiz, with (at the time it was written), perfectly valid questions. But it said something like:
"How many transistors, might there be on a high complexity integrated circuit?".
A:..10,000
B:..1 million
C:..None of these answers
Nowadays, the correct answer is probably C, but at the time the question was created, answer B, or even A, could be correct. So I actually gave the wrong (as regards current technology) answer, in the hope it was the correct answer for when the online quiz question was created.
EDIT: On reflection, you could always say "Incorrect Question", I can't really object.