This is a very interesting question. I would also personally lean towards "C" but I could be way off-base.
Why not A? I agree, prioritization should not be done on the basis of something being easy. To me that also implies circumventing the change control process as customers have asked for a change and the team is deciding on what to prioritize.
Why not B? Assign "someone" from the team to prioritize changes indicates that theoretically you could assign anyone from the team to prioritize the change, and do so without any feedback from the rest of the team or from the customer? Seems like a recipe for disaster. Note: For this very reason I did give option A some more thought but ruled it out.
Why not D? Agreed with Michael, denying change requests based on the phase isn't acceptable, though you could try to reason why it's not a good idea if you're too far along in the project.
Option C allows for the correct process to be followed (CCB, evaluation of LOE, discussions with customers to get justification of why both are the highest priority, and then arrive at an accurate priority for each.)
Definitely interested to see what the correct answer is so OP, please share
Yasir Mehmood, MBA, PMP, PMI-ACP, CSM, CSP, CLP (LeSS), CSPO
Community Moderator