A municipal cloud team assigns permissions by job role—billing viewer, network admin, backup operator—rather than writing unique ACL entries for every individual user. Which access model are they implementing?
Select an answer to reveal the explanation.
Short Explanation
Picture name badges for 'billing viewer' or 'network admin' instead of rewriting the lock list for every new hire. Stick people in the right role and they inherit the permissions that go with the job. That is RBAC—scalable, predictable, and way less messy than one-off ACLs everywhere.
Full Explanation
Role-based access control (RBAC) assigns permissions to roles that reflect job functions, then places users or groups into those roles. This reduces per-user ACL sprawl and keeps privilege aligned with duties such as billing viewer or network admin. Physical keycards alone do not govern cloud API actions; hand-edited per-user ACLs and anonymous write access to management planes are insecure or unscalable. Cloud+ identity objectives explicitly include RBAC for cloud resource authorization.