What are best practices for configuring Morpheus after installation? (Select two.)

Question

Options

• ALimiting API access for automation
• BSetting up integration with cloud providers
• CDisabling built-in security features
• DConfiguring role-based access control (RBAC)

• A
  3% (2)
• B
  94% (58)
• C
  3% (2)

Explanation

After installing Morpheus, setting up cloud provider integrations (B) is foundational - without them, Morpheus cannot manage or provision resources across AWS, Azure, GCP, or private clouds, which is its core purpose. Configuring RBAC (D) is a universal post-installation security best practice that ensures users and teams only access what they're authorized to, reducing the risk of accidental or malicious changes in a multi-tenant environment.

Why the distractors are wrong:

• A is backwards - Morpheus is automation-driven, so limiting API access would cripple its primary value; you should properly secure and configure API access, not restrict it.
• C is a red flag answer - disabling built-in security features is never a best practice on any platform and would expose the environment to significant risk.

Memory tip: Think "Cloud + Control" - you configure cloud integrations (B) to give Morpheus something to manage, and RBAC (D) to control who can manage it. Any answer suggesting you disable or limit core capabilities is a trap.

No community discussion yet for this question.