Most events need none of this. It is worth deciding in advance anyway, because the choice is much easier to make before the event than during it.
Deleting afterwards
This suits most apps. Posting stays immediate, which is what makes a feed feel alive, and you deal with the rare problem when it appears.
The cost is that whatever went up was visible until you noticed, and the notification for it has already gone out. See deleting posts and comments other people made.
Reviewing first
This suits an audience you do not know, a public event, or anything where a single bad post would be a real problem — sponsors in the room, press, students.
The cost is that every post waits for an admin, so somebody has to be watching. A feed where posts take an hour to appear stops being used. See turning on post approval, which is a Team plan feature.
If you are unsure
Start with deleting afterwards. Turning review on later takes one setting and a publish, so this is not a decision you are stuck with.
There is a third option you may not need
Restricting who can post at all is the simplest form of moderation: on a page set to admins only, there is nothing to moderate. If a page exists to carry your updates rather than host a conversation, that is usually the right answer instead of reviewing posts. See who can post to a social feed page.
Reference
Social Feed moderation — all the ways to handle what gets posted
Removing somebody from your app — for a person rather than a post
