Most definitely sir. That is what is confusing/annoying/frustrating about the test. I have seriously done afternoon problems and had NO IDEA what in the name of Abraham Lincoln I was doing...and gotten an acceptable. I have thrown things together in 30 minutes, figuring out and reading the code as I go along and gotten acceptable. As in, I'd never done that type of problem before, never studied it...nothing...and apparently aced it.I do have a question for people that have taken the test before. Were there any PM questions you thought you bombed or did poorly on then found out later that it got you the I grade or even an A, when all the while you were certain it was a U?
On the other hand, I have looked at a problem and been 100% confident, done it mostly without consulting practice problems or having that panicky "what do I do" moment and gotten unacceptable. That tells me a few things:
1. Process and procedure are paramount
2. You get points for showing what you know....but ALSO get points deducted for applying/knowing/using the wrong approach/method/procedure code reference. This means that this isn't partial credit like in college. NCEES doesn't show compassion cuz you "tried".
3. You can hide deficiencies in knowledge on the AM. But for the afternoon, if you don't know what you're doing, less is more. Putting too much information down can betray weaknesses and get points deducted, even if you "finish" every part of the problem.
4. For the morning, numbers and accuracy are key. For the afternoon, code checks and completeness are key. For example, say a problem is about seismic on "other" structures. If you use the wrong procedure, or incorrectly apply vertical seismic, you're better off not doing the problem since certain key procedural errors give you unacceptable and fail the entire test.