What is the primary function of Role-Based Access Control (RBAC) in Morpheus?

Question

Options

• ATo restrict user access based on predefined roles and permissions
• BTo allow all users full access to all system functions
• CTo disable API-based authentication
• DTo eliminate the need for user authentication

• A
  90% (56)
• B
  5% (3)
• C
  3% (2)
• D
  2% (1)

Explanation

Option A is correct because RBAC is a security model that grants system access based on a user's assigned role (e.g., admin, developer, tenant user), with each role carrying a specific set of permissions - ensuring users can only perform actions relevant to their responsibilities within Morpheus.

Why the distractors are wrong:

• B is the opposite of RBAC's purpose - unrestricted access defeats the entire point of access control.
• C is false; RBAC has no bearing on disabling API authentication - it governs what authenticated users can do, not how they authenticate.
• D is false; RBAC assumes users are already authenticated - it controls authorization (what you can do), not authentication (who you are).

Memory tip: Think of RBAC as a "job title = badge access" system - a janitor's badge opens the supply closet, not the server room. Roles define doors, not identities.

No community discussion yet for this question.