I would recommend it. If the purpose of the table is more saving user responses and not data collection then I consider it part of the code. Therefore I put it in the frontend. Putting it in the backend will be more difficult since you will have to keep track of each user's response or live with conflicts.
I would take the matter even further than friend DCKunkle has suggested. A database is an architectural construct of tables and relationships. It fails if anything is missing. I would suggest that the main backend be retained ONLY for the database as viewed in this way. Temporary tables used for manipulation should be placed in the FE if their use is on a per user basis or in an alternate backend if shared. This latter idea protects the main database from any accidental damage if a collaborative user activity goes badly wrong.
I habitually use multiple front and backends in this way, including a sandpit where users gaining Access experience can muck about with queries and suchlike which might otherwise damage the operation of forms and reports if accidentally modified.