Here are a couple of interesting tidbits I encountered. There was a question about threads. They wanted to know if some call to an image loader would stop a thread. I wasn't sure if it was a legit method, but the other methods all looked legit and it sounded like a method packed with blocking... so I answered "yes" - which in hindsight might have been one I got wrong. After all, calling waitForData() (or whatever it was) won't block the thread unless there is no current data. Another oddity was a fill-in-the-blank question. They wanted to know what was currently in the string. I wasn't sure if they wanted quotes or not. I'm now guessing "not".
This will be my only opportunity to gloat, since very few people have any idea what I'm talking about. When I finished the test I still had over an hour left on the clock. So I guess I finished the test in 55 minutes. Too bad that info isn't on the printout.
Well done. Do we know how many of us are certified so far? I would be worried if anyone took the whole time to answer the exam. I read through all my answers twice and still had loads of time left. So your next step is the developer exam!
I was pretty worried. I had read in other forums that people finished question number 20 only to look up and see that they had less than an hour left! Their advice was to keep a good pace and don't dilly-dally. So I may have rushed too much.
At the 55 minute mark I clicked on "done". I double checked my answers as I went. When I finished the last one, I could see no benefit to going back. I found the test to be so easy, I expected to get 100%. I was disappointed to get 97%.
I have two years of experience with Java. I spent about a month preparing for the test part time. When taking the mock tests, be sure to have javac ready to roll and test things that you aren't sure about. I would guess that the mock tests have about 5% faulty information and 10% stuff that won't be on the exam. Throw in another 5% for ambiguity that won't be on the exam.