A senior engineer reviewing a governance plan notices every project member has been made an owner of the project's models. What principle should drive the correction?

The correct principle is assigning governance roles based on responsibility, separation of duties, and least privilege, rather than granting ownership broadly to everyone on the team. Assigning roles by responsibility, keeping duties separated, and granting only the access each role needs prevents both accountability gaps and unnecessary exposure. Extending ownership even further, to every stakeholder who might ever touch the project, is incorrect because it compounds the problem rather than fixing it. The idea that roles do not matter once a model has passed validation testing is incorrect because role discipline matters throughout a model's life, not only before validation. Keeping a single blanket role because it is simpler to administer is incorrect because administrative simplicity does not justify undermining accountability and access control. For the exam, recognise 'everyone is an owner' as a red flag for missing least privilege and separation of duties.