I always cringe a little when people start to discuss interview "tests" like this. I've always wondered what it actually proves, if anything at all. The scope of automation is so vast, and candidate pool tiny already that you could ask a specific question to a great candidate and they simply aren't familiar enough with the concepts that they could fail the test(s) and of course now there is a big negative in the eyes of the interviewer. As Ron said, you have no idea what the learning capacity is of the candidate.
Ron's example is great, the one guy that can pass the test they aren't interested in because he was too expensive. Well, if you wanna play the game, play the game. If your budget dictates that you find a "technician" and pay them $50K a year, well align your expectations. If are looking for an "Engineer" and will pay them $100K, again align your expectations. But don't expect that you'll find an "Engineer" who will take a "Technician" role and technician pay. "We are looking for a guy that knows everything except what they are worth!". Candidates are NOT like capital projects, don't treat them as such.
Pressure during an interview is different than pressure in a manufacturing facility. Dropping a "test" like this during an interview especially w/o notice to the candidate prior is really poor practice in my opinion. I can understand this if you have presented the interview process to the candidate and they have some means to prep for the test topic(s). But then again, maybe it was 5 years ago they messed with PLC5s and block transfers and now don't even have the means to prep for it so they can read manuals and try to freshen up the memory but it doesn't build much confidence.
In my opinion leverage their references and take them through the facility and probe them for feedback on the architecture and what they see. This is a better way to separate the "men from the boys", but it only works if the interviewer is one of those "men" and not a "boy" himself.