What are key benefits of RBAC in Morpheus? (Select two.)

Question

Options

• AImproved security by restricting access based on roles
• BEnforcing standardized permissions for all users
• CReducing administrative overhead by automating access control
• DPreventing unauthorized users from executing restricted actions

• A
  87% (46)
• B
  9% (5)
• C
  4% (2)

Explanation

Role-Based Access Control (RBAC) in Morpheus delivers security by limiting what users can see and do based on their assigned role (A), and it enforces those boundaries by blocking unauthorized users from executing actions they haven't been granted permission to perform (D). These two benefits work together - roles define the rules, and enforcement ensures the rules are actually applied.

Why B is wrong: RBAC intentionally does not give everyone the same permissions - its core purpose is differentiated access. Standardizing permissions for all users would defeat the point of having roles.

Why C is wrong: RBAC doesn't automate access control in an autonomous sense; an administrator still manually assigns roles. It reduces complexity, not the need for administration itself.

Memory tip: Think of RBAC as a bouncer system - roles are the guest list (A: who gets in and what they can access), and enforcement is the bouncer at the door (D: turning away anyone not on the list). B and C describe features of a flat permission model or an autonomous provisioning tool, not RBAC specifically.

No community discussion yet for this question.