What must be configured when creating a new policy in Morpheus?

Question

Options

• APolicy type, scope, and enforcement rules
• BUser passwords and security groups
• CManual system override settings
• DRole-based access restrictions only

• A
  91% (32)
• B
  6% (2)
• C
  3% (1)

Explanation

When creating a new policy in Morpheus, option A is correct because policies require three core components to function: the policy type (what the policy governs, such as naming conventions, quotas, or approvals), the scope (which tenants, groups, clouds, or users it applies to), and enforcement rules (how and when the policy is triggered). Without all three, a policy cannot be properly defined or applied within the platform.

Option B is wrong because user passwords and security groups are managed through identity and access management settings, not the policy configuration workflow. Option C is wrong because manual override settings are not a standard configuration element when creating policies - policies in Morpheus are designed for automated governance, not manual bypasses. Option D is wrong because while role-based access is part of Morpheus's overall security model, defining it alone does not constitute creating a policy; scope is broader than just roles and must be paired with type and enforcement.

Memory tip: Think TSE - Type, Scope, Enforcement - the three pillars needed before any Morpheus policy can "TSE" (take shape and execute).

No community discussion yet for this question.