I feel like closing a question because not enough research was done prior to asking is a bit against what SE is about. Creating a reason for closing because not enough research was done, I feel, may allow for an elitist atmosphere to form. When the community on SE is so young (as is devops) I feel as these questions are going to be common as people search for their issues and questions. I feel that if these questions do arise and it is obvious that no research was done, I think it would be better for the community to answer the specific question being asked by linking and quoting the documentation where they could have found their answer. This way future visitors who may experience the same thing can be helped, as is the purpose of this community.
I don't think we should be doing peoples work, but I do know that often, stack exchange sites are among the first results when searching for information or tutorials, examples etc. I have seen questions from other SE that the community at the time was heckling the poster for his question, but has since become the top google result.
IMO closing b/c user didn't research enough goes against the idea of this community. lets keep the questions open (including this one), answer them with quotes and links to the tutorial so that we can be that resource future visitors years to come. "Give me teh codez" questions should be flagged and closed. We are too small to close topics because not enough research was done. IMO we are the research people look for, especially in a field as young as devops.