The point of asking questions on this blog is to have an on-going conversation with other people who are interested in the Java language. Maybe I could find the answers in a book, but it's more fun to go back and forth with other developers about these questions.
This can go both ways... If the topic is general (and open enough) to get into an interesting conversation, then yes. If the topic is complex enough to discuss the many nuances, then yes.
If the topic is looking for a straight answer (and not an open ended discussion), on a relatively simple topic, or on something that comes up often, then no. Not doing a quick check prior to asking the question is just being lazy, and shows a disregard for other people's time.
These examples are, of course, the two extremes. I am not commenting on where this topic fits.
I don't want to read a lot of message threads from five years ago looking for the one that answers my question. The learning experience is really a "live" experience here.
It may be boring, but reading books, reading tutorials, etc. etc. is part of research, which is an important skill needed by any professional programmer.
Keep in mind that you are asking very simple (classroom) questions to a forum. What will happen when you run into something hard in a real project? Say debugging a huge program that has been around for decades, and worked upon by hundreds of developers (many of which changed jobs) -- there might not be a forum of people that can help you.
Henry