How does Morpheus enforce policies?

Question

Options

• ABy applying predefined rules to platform behavior and user actions
• BBy disabling automation workflows
• CBy manually approving every provisioning request
• DBy restricting users to a single cloud provider

• A
  94% (47)
• B
  4% (2)
• D
  2% (1)

Explanation

Morpheus enforces policies by applying predefined rules to platform behavior and user actions - for example, setting quotas, restricting resource sizes, enforcing naming conventions, or controlling which clouds or groups users can access, all automatically without manual intervention (A is correct). Option B is wrong because Morpheus enhances automation workflows rather than disabling them - policies work within automation, not against it. Option C is wrong because the entire point of policy enforcement in Morpheus is to automate governance, eliminating the need for manual approval of every request. Option D is wrong because Morpheus is a multi-cloud platform by design, and policies can manage multi-cloud access rather than restrict users to one provider.

Memory tip: Think of Morpheus policies as "guardrails on a highway" - they define the rules of the road automatically so traffic (provisioning) flows freely but safely, without a traffic cop (manual approval) at every intersection.

No community discussion yet for this question.