You could use a dictionary (key value pairs). You could use a flat file (equally viable as a text entry within a Shortcut perhaps) like a two column CSV. You could even use a database table (e.g. from AirTable).
But something we probably need to understand beyond your desire to understand dictionaries is more about your end goal as there’s a lot there that could affect the choice of data store.
- Type in some text and match it (case sensitive / case insensitive).
- Type in an ID to be matched from a list of options.
- Select one entry from a list of options.
- Select multiple entries from a list of options.
What presentation formats will the questions require from the following?
The data structures required for different question types and presentation formats would require different set-up, and a more complex one if you want a variety of types and formats.
Next, have a think about how you want to maintain, update, and potentially switch sets. How easy do you need it to be? Do you want to be able to maintain from within the shortcut, or perhaps via an external file or database. Perhaps more than one. Do you want to be able to mass import data from say a spreadsheet?
Again, this can affect the choice of data storage format.
In terms of the questions, presumably they should be randomly chosen rather than the same order each time based on your screenshot. But do you want to have a variable number of questions and do you want to guarantee each question appears a maximum of just one time? Do you want to ensure that you never get the same order more than once or even the same sub-set of questions more than once? If so, we need to consider holding that data and again that could influence the data storage format.
There’s quite a bit of scope even in a simple flash card solution, and this is why there are full blown apps for this sort of thing. Including free iOS apps and web apps.
The more detail you can provide, the clearer a recommendation, or set of recommendations, can be made.