A county clerk’s office grants application rights user-by-user instead of by job function for clerks versus auditors. Which identity strategy should replace that practice?
Select an answer to reveal the explanation.
Short Explanation
Hand-crafting every clerk’s permissions is like cutting a new house key for each shift—messy and error-prone. Put people in clerk and auditor roles (or groups) and hang the rights on the role. Forever one-offs, shared god-rights, or “just sit at that desk” do not scale and invite mistakes.
Full Explanation
Group- and role-based identity strategies map job functions to reusable authorization packages, improving consistency, least privilege, and lifecycle management. Ad-hoc per-user grants drift quickly and complicate reviews and revocation. Collapsing distinct duties into shared privileged rights violates separation of duties, and disabling authorization checks removes the control entirely. Roles for clerks versus auditors exemplify scalable identification and authorization design in municipal applications.