In non-discretionary access control using Role Based Access Control (RBAC), a central authority determines what subjects can have access to certain objects based on the organizational security…

Question

Options

• AThe societies role in the organization
• BThe individual's role in the organization
• CThe group-dynamics as they relate to the individual's role in the organization
• DThe group-dynamics as they relate to the master-slave role in the organization

• B
  94% (45)
• C
  2% (1)
• D
  4% (2)

Explanation

In RBAC, access permissions are assigned based on the individual's role in the organization (e.g., "Manager," "Auditor," "Developer"), not on personal identity - so B is correct. A central authority defines what each role can access, and users inherit those permissions by being assigned to a role.

Why the distractors fail:

• A ("society's role") is wrong because RBAC is scoped to the organization, not broader societal roles or external classifications.
• C ("group-dynamics as they relate to the individual's role") introduces the concept of group dynamics, which is not a factor in RBAC - permissions follow the role definition, not interpersonal or team dynamics.
• D ("master-slave role") is fabricated terminology with no meaning in RBAC or standard access control frameworks.

Memory tip: Think of RBAC as a job title system - a "nurse" gets access to patient records, a "billing clerk" does not, regardless of who the person is. The role is the key, not the person or group politics.

No community discussion yet for this question.