A building-permit system needs permissions that match clerk job duties rather than one-off exceptions. Which authorization model should be implemented?
Select an answer to reveal the explanation.
Short Explanation
Permit clerks need a job-shaped keyring, not a master key or a free-for-all. RBAC hangs the right permissions on the clerk role so everyone in that job gets a consistent, least-privilege set. Per-desk DAC favors, blanket admin, or intelligence MAC labels on permit PDFs are the wrong tools for this counter.
Full Explanation
Role-based access control assigns permissions to roles that reflect job functions such as permitting clerk, then assigns users to those roles. That model scales municipal applications better than ad-hoc discretionary grants or universal administrator rights. While MAC is appropriate in label-driven environments, transplanting intelligence classification schemes unchanged onto ordinary permit workflows misapplies the model. RBAC supports least privilege, reviewability, and consistent authorization for civic permitting systems.