From what I've seen here in the last month, you're trying to study backwards from the test. By backwards, I mean that you're gathering up all the mock tests you can find (some of them questionable, by the way), posting them here and trying, with the help of people here, to learn what the answers are.
This is a good approach if you're going to be tested on historical dates or
word definitions but not for programming. The self test questions at the end of the chapters are designed to show whether you know the underlying concepts or not. If you do, you should be able to answer any questions on the subject, no matter how they're worded.
A more solid approach, in my opinion would be to study a chapter then write some little programs of your own to test your assumptions about the way things should work. If you can write these programs and consistently predict the output from them, move on to the questions in the book. If you get any wrong, go back over that material, write some more programs that use whatever concepts are being taught and make sure that you know the material inside and out. Once you do, then move on to the next chapter.
When you get to the end of the book, then start looking for mock tests, not to study, but to find out if there are any areas where you're knowledge is weak. Once you find such a topic, stop taking the mock tests and study that topic. Sometimes a different book is what it takes to get a particular concept to click. Sometimes, a well written question to the forum can show folks here what you don't understand and help them to help you.
Most importantly, write lots of code.
Lots and lots of code.
[ April 08, 2008: Message edited by: Ben Souther ]