This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
First to quote the source: Sun's SCJP1.5 e-Practice Exam
Even then notify doesn't cause a thread to stop. I think the sense of the question is to ask about methods which stop an executing thread and out of those identify which directly cause the thread to stop.
As explained above notify and notifyAll don't cause a thread to stop (so no question of stopping it directly)
Now calling the wait method causes the thread to stop and wait (waiting from running)
The call to start on some thread or the call to yield doesn't mean a thread will be stopped. Its a matter chance which depends upon the current situation and thread scheduler.
As an example: A thread is already running and start method is called on some other thread. We can't say that first thread will be stopped. It depends upon thread priority, thread scheduler etc.
Now calling the yield() method on a thread makes the thread to go to waiting state so that some other waiting thread may be given resources. But what if there is no other waiting thread?? The thread will continue to run.