An architect reviews RBAC for a multi-agent solution. The research agent only needs read access to a knowledge index and a web-fetch tool. The fulfillment agent needs to create support tickets. Currently both agents use a role that can read secrets, write tickets, and delete indexes. What change best applies least privilege?
Select an answer to reveal the explanation.
Short Explanation
The correct answer is D. Least privilege means the research agent only reads knowledge and fetches pages, and fulfillment only creates tickets—no shared role that can delete indexes or read unrelated secrets. Keeping a fat shared role or subscription owner for convenience is how breaches spread. Removing API auth dodges RBAC by making everything worse.
Full Explanation
Option D is correct. Secure multi-agent design requires identity-based access, RBAC, and tool permission boundaries aligned to each agent's scope. Separating research and fulfillment roles eliminates unnecessary rights such as secret read and index delete from agents that never need them.
Option A is incorrect because convenience onboarding does not justify standing privileged access that enables lateral damage.
Option B is incorrect because subscription owner maximizes blast radius and violates least privilege.
Option C is incorrect because removing API authentication eliminates authorization rather than refining it.