suggestion: have a "key-fact" subcategory for each question.

[likejudo]

Suggestion.
Currently every question has a topic name which is too broad for us to sharpen our revising of topics.
Yet, each question is based on a critical, key fact.
suggestion: have a "key-fact" subcategory for each question. for instance: clone() is a shallow copy and both objects share the deeper members after cloning.
this was for enthuware.ocpjp.v17.2.3065 and the topic "Arrays" is too broad.
Furthermore, having a "key-fact" sub-category has potentially powerful uses.
One can query our test history to give a report of failures grouped by key-facts to find exactly what one's critical weakness in understanding are.
This will make for sharper exam study. Which in turn will be more effective and efficient.

[admin]

Thank you for your suggestion. We will work on it asap.

[likejudo]

To identify the key-fact, it may help to ask, "what is the one (most) critical fact in this question that would make a person stumble and get it wrong?" or to put it another way, "what trip-wire fact makes this question a gem (or a bomb ) that we had to include it on a test?"
(Feel free to contact me by email or WhatsApp if you would like to discuss more).