I did bad on the mocks and expected to score in the 60's, but instead got 89% somehow even though I didn't really know AWT or java.util.
Concentrate on exactly what the objectives say will be tested. Like many have said before, expect around 6 questions on Threads (reconize deadlock conditions) and know all the java.io constructors mentioned in the objectives. My sincerest thanks to everyone on this site who has mentioned the importance of these two topics in the past 6 months. Got 100% in all categories except : Flow control and exceptions - 85% Lnaguage Fundamentals - 88% (I expected better) Operators and Assignments - 71 % (I expected much better) Java.AWT.package - 50% (exactly what I expected) I took 3 JQplus tests a few weeks before the test and averaged 60% and I took Jwhiz a few times about a month before the test and got in the 70's each time. So going into the test I was a little scared since people have said the mock tests were easier than the real thing. In my case however those mocks were harder. Overall I liked Jwhiz slightly better even though it had worthless questions on deprecated methods and applets which aren't on the test. I scored 78 in the Marcus Green mock(I think it was his latest). I haven't heard anyone talk too much about the online mock test that Sun sells for $75 and lasts for 3 months. In my opinion it is by far the most accurate indicator of the level of difficulty you can expect for the real test. But it does not explain the answers very well and is not too helpfull to learn from. I also found two errors in the answers which would not compile which I have reported. Never the less if I had to do it over again I would choose only the Sun test, not Jqplus or Jwhiz for training purposes. But that my also be because I had every decent Java book there was to study from (Mughal, RHE, Exam Cram, Exam Prep, Syngress, and few other general books) and didn't need to use the mock to learn from. I spent about 9 months studying. Started with "Java in 21 Days" which took me a few months. Then concentrated on the first 5 chapters in Mughal's book for about 4-5 months. Overall, RHE is the best for exam purposes assuming you have some other book you have already read concerning java. Mughal is good also, but covers more than is needed for the exam and I thought he needed more examples for Threads. The Syngess book is vastly underrated; it is actually very good despite what the reviewers said on Amazon.com. Any of those three books will get you through the exam with no problems. I jumped around reading about 5 other Java books and never did spend the proper amount of time on AWT, Threads, String, IO, and Collections that I should have. The 2 days before the test I created customized tests on JWhiz, JQplus, and the Sun mock, focusing only on Threads and IO. Thanks to everyone on this site who has replied to my postings or has posted usefull information. I love you all!
Hi Herb, Congrats! What a pleasure to hear ur opines. I also checked (not studied thoroghly) all the popular books in Java as I have to teach in a reputed IT org in a small country. But i covered first half of the Syngress, Herb Shieltd, Ivor Horton and completely covered RHE and Khalid Mughal. I have Exam Cram and thinking to review it just before one week of appearing the exam. Do u think i m right? My area of weakness is I/O (only studying for 3 days now) and lack of giving mock exam. But these weaknesses r tgemporary and will be covered in the coming two weeks.;D Any suggestion?
Ashik Uzzaman Senior Software Engineer, TubeMogul, Emeryville, CA, USA.
Joined: Feb 12, 2001
Originally posted by Ashik uzzaman: Hi Herb, My area of weakness is I/O (only studying for 3 days now) and lack of giving mock exam. But these weaknesses r tgemporary and will be covered in the coming two weeks.;D Any suggestion?
ExamCram has usefull points, but RHE is better if you have the time. For IO: What I did is create a list of all the important (see objectives) IO Classes and their constructors on 1 piece of paper so you can easily see the differences and similarities between all of them at once. For example, at the top half of the page was a simple hierarchy diagram showing INPUT/OUTPUTSTREAM at the top, then below that FileInput/OutputStream and FilterInput/Output Class, then below Filter was Buffered and DataInput/Output. Those are the important classes for byte stream IO classes. The next half of the page was for the other IO classes. File, Reader/Writer, and Random Access. (and their subclasses as well, which I forgot to mention) Next to each class I put an abrreviated notation of their constructors and if they implemented anything (like DataInput). You'll notice that most the constructors in the top half of the page use Input/OutputStream in their constructors. Look for more similarities /differences. Notice which classes append/create files and how do they work... ("true" for append which isn't mentioned in many books) [This message has been edited by herb slocomb (edited August 06, 2001).] [This message has been edited by herb slocomb (edited August 09, 2001).]