"Dumb" questions are fine, but they're completely different than lazy questions, which are often misidentified as dumb questions.
A dumb question might be something like "I can't log into my server with `ssh server.com`. It keeps rejecting my password when it asks for `user@server.com's password`. What's going on?" The user might not know to explicitly add `admin@` on the command line.
A lazy question is "My server that I bought doesn't let me log in!" Come on, you need to address 1) what result you expect, 2) the exact steps you take, 3) the result you obtain instead, and 4) any other details a non-omniscient being might need to answer your question.
The first one is not really a dumb question. They may have setup their .ssh/config so that the user is automatically taken from that file and password being rejected may simply be due to some other reasons (such as disabling password based login at the server). This is why people should not assume something or make a judgment.
The second question is more because of a misunderstanding about the particular platform. These type of lead-in questions are common in tech support and even many forums where they expect someone will get back to them with more specific questions (they may not have an idea what sort of information will be relevant). A simple comment clarifying this will not only prevent confusion due to arbitrarily closing the question but will help them make a better question.
The second question could be coming from someone that simply doesn't have enough context to lead off with that information.
Like maybe they don't realize there are different ways of interacting with servers. I wouldn't expend a great deal of effort helping someone asking a question like that, but I hope I wouldn't make a bunch of a priori assumptions about why they were asking that question instead of another one.
The second question simply fails to describe what actions the user is taking. In this case, it's not a matter of not knowing about methods of interacting with servers. It's a matter of leaving out steps, such as typing `ssh`, due to lack of their effort.
If I asked a question about something I have no idea about, such as training a sheepdog, I'd still be able to put forth effort into describing the steps I take to someone, so they know what I tried to do. The question "The dog isn't learning this command!" isn't bad because of my lack of sheepdog knowledge, it's bad because it omits tons of important information about my situation. Therefore it's a lazy question.
A dumb question might be something like "I can't log into my server with `ssh server.com`. It keeps rejecting my password when it asks for `user@server.com's password`. What's going on?" The user might not know to explicitly add `admin@` on the command line.
A lazy question is "My server that I bought doesn't let me log in!" Come on, you need to address 1) what result you expect, 2) the exact steps you take, 3) the result you obtain instead, and 4) any other details a non-omniscient being might need to answer your question.