How can administrators control access to self-service catalog items in Morpheus?

Question

Options

• ABy assigning role-based access control (RBAC) policies
• BBy enforcing hardcoded credentials in each catalog item
• CBy disabling catalog automation features
• DBy restricting all catalog items to private clouds

• A
  88% (21)
• C
  8% (2)
• D
  4% (1)

Explanation

Option A is correct because Morpheus uses Role-Based Access Control (RBAC) to govern which users or groups can view, provision, or manage self-service catalog items - administrators assign roles that define permissions, ensuring the right people access the right resources without exposing everything to everyone.

Why the distractors are wrong:

• B - Hardcoded credentials are a security anti-pattern and have nothing to do with access control for catalog items; they would create vulnerabilities, not manage permissions.
• C - Disabling catalog automation defeats the purpose of self-service provisioning entirely and doesn't selectively control access.
• D - Catalog access restrictions aren't tied to cloud type (private vs. public); RBAC works across all cloud targets in Morpheus.

Memory tip: Think of RBAC as a keycard system - administrators hand out keycards (roles) that only open specific doors (catalog items). If you remember that "self-service" still needs governance, and governance in modern platforms = RBAC, you'll always land on A.

No community discussion yet for this question.