This potentially could be a good test, if the example is well chosen.

We read of all kinds of tests, some of which border on the ridiculous: throwing bizarre (often not even IT related) examples at someone to see if they can jump out of the box fast enough. These kooky tests, however, seem to be more about the ego of the interviewer than any real world capabilities of the candidate.

Another extreme is a test about knowledge or deeply arcane functionality of SQL or whatever to see if they have the photograhic memory to recall syntax. Realistically, however, a good admin/developer needs to know these rarely used capabilities are there, most sensible people check the documentation when they need to use them.

The ideal test, I think, involves presenting a problem (like above) and asking: how would you go about improving this? Not the detailed syntax, but instead listening to the candidate's thought process.

For a humorous take:

https://jobmob.co.il/blog/funny-ikea-job-interview-cartoon/