Post a community wiki for the purpose of attracting trivial answers, not combining ones that were already posted
Every now and then we get a question which is formulated in a way (either intentionally or unintentionally) that will allow a large number of trivial answers in a range of languages. Especially in cases where it's unintentional (and the trivial answer is an "exploit" of the question), having a large number of duplicate trivial answers is just noise that a) makes it hard to find the more interesting answers, and b) discourages the posting of more interesting answers that don't use the exploit, in a language where the exploit works.
If a problem does admit trivial answers in a large number of languages, this will normally be immediately obvious to someone viewing the post early. As such, I'd strongly recommend posting a community wiki for the purpose before the question has too many answers, to encourage people to just add their trivial answer with an edit there rather than posting it separately as an answer. See here, for example; that's a community wiki that I originally posted (thinking of this question when I did so) when the question was new and I realised that a literals-only solution would typically be a valid answer to the question as worded. If not for the community wiki, we might well have made the thread unusable as a result of 19 identical answers cluttering it up; a single answer showing the exploit is interesting, a large number of duplicate answers isn't.
We can also see that there are answers on the page in some of the languages where the trivial solutions work; some of them are longer, but much more interesting. Without the community wiki, that may well not have happened (as people typically scroll through the list of languages to see if theirs is listed, if there's a shorter one shown already, they may well just not bother).
The big advantage of doing things this way is that we aren't retroactively penalising users, but rather encouraging them to help keep the thread clean via giving a push in advance.
Note that this typically only works in questions which have some sort of exploit (literal-only answer, zero-byte answer, syntax errors being a valid solution in many languages, and the like). If the question is one which is expected to be solved via a trivial, non-exploit answer, then the best approach is probably just to downvote the question and post answers separately per language, so that it can have some sort of value as a catalog; the thread's likely to be unusable in that case anyway, and there's no benefit in encouraging the posting of less trivial answers as there'll be nothing differentiating them from the trivial one but the lack of golfing.