Which of the following is not a prioritisation technique?

Any one of these, or a combination of them, may be used to help establish priorities.

I agree with Ian that any of the techniques are can be used to establish priorities. 

If I had to pick an answer it would be 'planning poker' since typically this exercise is used to establish estimates of Product Backlog Items.

This could be a precursor to something like Kano analysis or Product Backlog ordering which are more directly used to prioritize/order work. 

Where did you come across this question Dejan?:) I'd argue that the Kano, US Mapping and Product Backlog ordering are mostly used by the Product Owner (not saying the Dev Team wouldn't use them, but just my thought) and the planning poker mostly by the Dev Team. But that's my 2 cents. In that regard, the PO is responsible for ordering, hence Planning Poker has less to do with ordering as well as provoking a discussion.

Sander Dur

I found it here https://www.volkerdon.com/ as someone who passed exam recommended.

I agree with Tony Divel,

If I had to pick an answer it would be 'planning poker' since typically this exercise is used to establish estimates of Product Backlog Items.

Planning poker really is just for estimating the size or effort of an item. That doesn't equal priority. I suppose someone out there could use it for prioritization but that would be using the tool in a vastly different way than was intended. 

the best answer is number 3 (planning poker) because  is used for estimation of user stories not for others mentioned for prioritisation technique. 

Your reasoning is valid, and it highlights an important distinction. While "Planning Poker" is a valuable Agile technique for estimating the effort or complexity of tasks, it is not primarily a method for directly establishing priorities or ordering tasks based on their importance or value.