HPE0-G04 · Question #18
What are best practices for managing Morpheus Blueprints? (Select two.)
The correct answer is B. Configuring role-based access to restrict execution C. Using version control to track blueprint changes. Managing Morpheus Blueprints effectively requires both security controls and change management - which is exactly what B and C address. Configuring role-based access (B) ensures only authorized users can execute or modify blueprints, reducing the risk of accidental or…
Question
What are best practices for managing Morpheus Blueprints? (Select two.)
Options
- AStoring blueprints outside of Morpheus to avoid automation
- BConfiguring role-based access to restrict execution
- CUsing version control to track blueprint changes
- DAvoiding pre-testing before deployment
How the community answered
(40 responses)- A18% (7)
- B73% (29)
- D10% (4)
Explanation
Managing Morpheus Blueprints effectively requires both security controls and change management - which is exactly what B and C address. Configuring role-based access (B) ensures only authorized users can execute or modify blueprints, reducing the risk of accidental or unauthorized deployments. Using version control (C) lets teams track changes over time, roll back to known-good states, and collaborate safely - a foundational DevOps practice.
The distractors fail because A is counterproductive: blueprints are the automation mechanism in Morpheus, so storing them externally defeats their purpose. D is dangerous - skipping pre-deployment testing introduces unpredictable failures in production environments.
Memory tip: Think "RVC" - Role-based access + Version Control = responsible blueprint governance. Anything that removes visibility or control (like external storage or skipping tests) is always wrong in a platform management context.
Topics
Community Discussion
No community discussion yet for this question.