Correct answers: B - C

B: Global picklist = how is consistent ? -> can use the same values on different objects, so the integrity of the values itself is preserved across objects, for example

C: Dependent picklist = how is consistent ? -> the conditional relationship to another field (es. field A), makes this picklist "appear" on the layout ONLY when the record type you define HAS the field A included. So that ensure that you will see only relevant picklists, dependent to the field for the record type.

I hope this helps.

Dependent picklists are usueless in this case. For each record type you can define which values of pickists are available in object setup. C and D are correct answers.

The correct answers are definitely C and D.
A makes no sense here and you cannot choose the record type as the controlling field for a dependent picklist.
As category is not a standard field, you need to create a custom picklist, so D.

The answer is B and C. The dependent picklist gives 'values respective to record types'. Global picklists ensure '(...) consistent picklist values'.

Correct answer is C,D