Automation Fundamentals and Prism Central Automation Concepts
The Automation Fundamentals and Prism Central Automation Concepts domain tests how the Nutanix automation stack is assembled and governed. Prism Central is the control plane: it hosts categories, projects, roles, approval policies, Calm, X-Play playbooks, runbooks, and monitoring. Expect questions on how these objects scope and secure automation rather than on isolated product features.
Core building blocks
- Categories are key-value labels assigned to VMs, apps, and other entities. They are the main scoping mechanism for projects, quotas, playbooks, and policies.
- Projects combine a category scope with RBAC, quotas, approvals, and environment settings. A project is a guardrail, not a folder.
- Roles grant permissions; approval policies gate actions; credentials and endpoints store connection details for integrations.
- Automation follows a trigger-action model: an alert, event, schedule, or manual request starts a playbook or runbook.
Worked example
A team wants only production VMs in a quota. They create category Env:Prod, assign it to the VMs, and scope the project to that category. If a VM is missing the category, it falls outside the project: quota enforcement and category-scoped playbooks do not apply. The fix is to correct category assignment, not to raise the quota.
Traps
- Treating Prism Element and Prism Central as interchangeable; automation features live in Central.
- Assuming projects are folders; they enforce policy and quota.
- Forgetting that categories can have multiple values and must match the intended scope.
- Granting broad roles when a narrower project role works.