I would flag such an answer accordingly.
Suggesting more than one alternatives that do the same thing is more confusing rather than helpful. Questions that allow multiple suggestions in a single answer, while not attempting to solve particular issue of the OP, and answers that provide equal and independent alternatives for the same thing are to me Off-Topic
.
In a related spam-handling discussion I have posted a suggestion for flagging such answers, as well as question. According to that these questions would be categorized as "Off-Topic/Overly General"
Note: The linked discussion answer is mine. The purpose is not to promote it, but rather encourage its improvement and the flagging discussion in general.
Following the recent comments, I am updating with my personal suggestion on handling the flagged post. As I am not very familiar with the exact flow on flagged posts on StackOverflow (from where I acquired the idea), and in what aspects it is customizable, so I would expect the following behavior, which seems standard.
- The posts get flagged by the community and accumulate close votes
- Once a number of close votes is reached (not sure if votes weight based on voter's role) the question gets closed automatically, with the appropriate description (example):
This question is closed as Off-Topic because it has been identified as Overly General by { list of users }.
- A moderator could have the privilege to immediately close a question if appropriate (maybe this should be further discussed).
- Once closed, only the OP and moderators can edit or remove the post. After editing, the OP should be given the opportunity to request reopening - if s/he has made edits that are suitable for the Q&A requirements.
- Questions requesting reopening will appear in a dedicated moderators queue and will be voted for approving the reopening or not. It will be fair if approval requires the same number of votes as closing does.
- If the question is not approved for reopening, we will return to step 4.
I understand the above sequence of steps does not include the possibility of removing a post, and allows for endless loop of approval attempts - rejection, which could practically keep the post alive for a long time. I am not familiar with how the StackExchange platform addresses this (I am sure it certainly does address this), but I'd suggest a policy for that matter, which I believe is used already (or at least a similar one):
- A restriction on the number of reopen attempts. If the user has exceeded the reopen attempts on a question, the question will be removed. I believe 2 or 3 is reasonable value for the number of allowed attempts per user.
- Lack of activity upon the closed post - no edit or reopen attempts for a while will cause the post to get automatically removed. Perhaps two weeks or 1 month will be a decent period.
- Manually removed by moderators upon casting remove votes. This implies that closed question can be further voted upon for removal. The rest is similar to close vote accumulation principle described above.
Note, that the removal does not apply to flagging of the type This question belongs to another stackexchange site.
, as the removal should be substituted with the migration, if applicable.
In the above flows I have expressed some uncertainty on what are the technical possibilities of the Stack Exchange platform, so I will try to clarify these on Meta and update accordingly. I will add comments to this post when I do so.
Here are some references from meta.stackoverflow.com regarding closing, which might be useful :