I can't win on these. If you read it exactly as it is written then people complain that we should have understood what the question was really asking in spite of the "accidental" typo. So I figure this must just be another "accidental" type and I correct it, separating the "from" from the the "TEST." But no, this time the question is attempting to trick us. If it wasn't then why use fromTEST as the alias? No one would ever use that intentionally. So I guess I don't know what the lesson is here. If it is to identify errors in code, then I passed. I found the error and corrected it. If it is to pretend that someone would actually name an alias "fromTEST" and want to know the results, then I would say, don't waste my time.
When I saw the question in the newsletter, I assumed the missing space was a typo. But after seeing that one of the answer options actually mentioned the missing space, I knew that this must have been deliberate. I fail to see how you can think the question author could have accidentally missed a space he intended to be there.
As to what can be learned from this question - have you never stared for half an hour or more at an inexplicable error message being returned from what appears to be perfectly valid SQL before finally noticing the missing comma in
INSERT INTO dbo.TargetTable (ColA, ColB, ColC, ColD, ColE)
SELECT (Complicated + Expression) / That
* Nevertheless * (1 - IsSyntacticallyValid) -- ColA
ColB, -- ColB
'String constant', -- ColC
17.0 * (1 - ColD), -- ColD
NULL -- ColE