A project lead turning a proof of concept into a governed deployment wants to prevent the same person from building a model and also approving it for production. What principle addresses this?
Select an answer to reveal the explanation.
Short Explanation
Separation of duties is exactly this: you shouldn't let the person who built the model also wave it through. Keep build and approval with different people, so no one can push their own work through unchecked.
Full Explanation
The correct answer is separation of duties, which keeps build and approval responsibilities with different people so no one can push their own work through unchecked. It prevents one person from both creating and self-certifying a model for production.
The least privilege option is wrong because it concerns the scope of permissions, not splitting responsibilities between people; limiting login systems does not address build-versus-approval separation.
The role inheritance option is wrong because automatically escalating a builder's access after model completion would worsen the problem.
The accountability option is wrong because requiring the builder to write the approval justification themselves is the self-approval pattern separation of duties exists to prevent.
For the exam, distinguish separation of duties, who does what, from least privilege, how much access each role gets.