What is a key benefit of integrating workflows with a code repository in Morpheus?

Question

Options

• AEnabling continuous deployment of infrastructure changes
• BAutomating user role assignments
• CDisabling manual script execution
• DLimiting instance provisioning to local files

• A
  83% (35)
• B
  10% (4)
• C
  2% (1)
• D
  5% (2)

Explanation

Integrating workflows with a code repository in Morpheus enables continuous deployment of infrastructure changes by allowing automation pipelines to trigger provisioning, configuration, and lifecycle tasks directly from version-controlled code - making infrastructure changes reproducible, auditable, and automated. Options B and C are incorrect because Morpheus handles user role assignments through its own RBAC system (not code repo integration), and code repo integration actually enables script execution rather than disabling it. Option D is the opposite of a benefit - repository integration expands provisioning sources beyond local files, not restricts them.

Memory tip: Think "repo = pipeline." Connecting a code repository to Morpheus is about enabling CI/CD-style automation for infrastructure, just like connecting a repo to GitHub Actions enables automated builds - the core value is always continuous deployment.

No community discussion yet for this question.