For these types of checks where you don’t want to expose the answer on the browser console the best approach is to actually create privacy rules that stops the user from seeing that data, and then create a backend workflow that bypasses privacy rules where you can run the search and then return a boolean stating whether it was the correct answer or not, or any extra data you may need but you don’t want to expose on the client.
This will ensure that the sensitive data effectively never leaves the server, it’s not accessible to the user if they know how to query it, but the info you need is returned correctly.
This is a very common flow, the most common one being vouchers and promocodes - you don’t want the user to be able to view any promocodes, but you need them to be able to check for their existence and return the data related to the checked promocode.
In bubble, calling your own backedn workflows is a bit tedious, but this topic might be useful: