What are best practices when managing code repositories in Morpheus? (Select two.)

Question

Options

• AStoring configuration files in version-controlled repositories
• BEncrypting sensitive credentials and API keys
• CDisabling repository syncing to prevent automation issues
• DRestricting repository access to developers only

• A
  72% (34)
• C
  19% (9)
• D
  9% (4)

Explanation

Storing configuration files in version-controlled repositories (A) enables traceability, rollback capability, and collaboration - core principles of Infrastructure as Code. Encrypting sensitive credentials and API keys (B) is a fundamental security practice that prevents exposure of secrets even if repository access is compromised; Morpheus integrates with secret managers precisely for this purpose.

Disabling repository syncing (C) is counterproductive - syncing is what enables Morpheus to automate deployments and keep environments consistent with the source of truth. Restricting access to developers only (D) is too narrow; in Morpheus, operations and automation services also need repository access to function, and role-based access control (RBAC) is the proper mechanism - not blanket developer-only restrictions.

Memory tip: Think "Version control + Encryption = VEry secure repos." The wrong answers both involve removing capabilities (syncing, access) rather than securing them - Morpheus best practices are about enabling automation safely, not limiting it.

No community discussion yet for this question.