I have a query, I have a field that stores the answer to the question, which is found by the radio_button "Yes", however I'm not sure where the sub-options should be stored, the quickest thing that comes to mind is create an additional field in the same table that stores the answers, something like SubAnswer, or create an additional table where each suboption is nested, and reference said table to the main table, but I would appreciate a suggestion on the best way to do this
you could just create an enum and by storing it in a
example:
enum red-social: {Faecebook: 0, twitter: 1, Instagram: 2}
the documentation if you're interested: https://api.rubyonrails.org/v5.2.2/classes/ActiveRecord/Enum.html
Both options are valid, adding a field or creating a table, however deciding between one or the other depends more on the nature of your problem and why you are going to require said information.
If it's going to be just to display that information later, I think a field to store the information would suffice. You could create a string type field, where you serialize an array where you store that information, or a jsonb type field (in postgresql, I don't know if it exists in other engines) which is much more versatile when it comes to making queries. Now, if you plan to carry out more intensive queries, where you consult thousands or millions of businesses and you need to filter among those who use one or another social network, perhaps it would be a good option to create a table.
Personally I would choose a field over a table which is easier to implement and more maintainable. If you see a need to scale in the future, since the number of records in your table has grown quite a bit, you might consider creating a new table and migrating that information.