How do policies contribute to governance in Morpheus?

Question

Options

• ABy enabling manual intervention for all changes
• BBy allowing unrestricted cloud spending
• CBy limiting unauthorized access and enforcing compliance
• DBy disabling user authentication

• A
  5% (1)
• C
  91% (20)
• D
  5% (1)

Explanation

Policies in Morpheus serve as the enforcement layer of governance by limiting unauthorized access and enforcing compliance - they define what users and groups can do, where, and under what constraints (e.g., resource quotas, network restrictions, approval workflows). This makes option C correct.

• A is wrong because policies automate governance enforcement; manual intervention defeats the purpose of policy-driven control.
• B is wrong because policies do the opposite - they restrict cloud spending through budgets and quotas, not enable unrestricted spending.
• D is wrong because disabling authentication would undermine governance entirely; policies layer on top of authentication, not in place of it.

Memory tip: Think of policies as a rulebook - they limit and enforce, never open the floodgates (B) or remove the doors (D). Any answer suggesting "unrestricted" or "disabled" security is always wrong in a governance context.

No community discussion yet for this question.