RBAC (Role-Based Access Control) assigns permissions how?

RBAC (Role-Based Access Control) assigns permissions how?

• A. Based on time of day
• B. Access rights are assigned by role; users get permissions for their role
• C. Inheritable from a default global role
• D. Random assignment

Answer: (B)

In RBAC, access rights are assigned by role. Each role has a defined set of permissions for what actions can be performed on which resources. Users are granted membership in one or more roles, and by belonging to those roles they automatically inherit the permissions attached to them. This makes administering permissions scalable: you manage what a role can do, not what every individual user can do. If someone changes positions, you update their role memberships rather than reconfiguring many permissions for that person. While some systems support role hierarchies where higher roles include the permissions of lower ones, the core idea remains that permissions flow from roles to users through role membership. The other options don’t fit because RBAC isn’t based on time of day, isn’t defined as inheriting from a default global role, and isn’t assigned randomly.

In RBAC, access rights are assigned by role. Each role has a defined set of permissions for what actions can be performed on which resources. Users are granted membership in one or more roles, and by belonging to those roles they automatically inherit the permissions attached to them. This makes administering permissions scalable: you manage what a role can do, not what every individual user can do. If someone changes positions, you update their role memberships rather than reconfiguring many permissions for that person. While some systems support role hierarchies where higher roles include the permissions of lower ones, the core idea remains that permissions flow from roles to users through role membership. The other options don’t fit because RBAC isn’t based on time of day, isn’t defined as inheriting from a default global role, and isn’t assigned randomly.