A self-service engineer needs to deploy development VMs in a Nutanix project. The engineer must not be able to delete production VMs in the same project. Which role should you assign?
Select an answer to reveal the explanation.
Short Explanation
Think of project roles like a coworking space: a Consumer can rent a desk and use it, but can't clear out somebody else's office. Consumers deploy and manage the VMs they own, so they can't delete production VMs that belong to others. Project Admin and Cluster Admin hand over far more than you want.
Full Explanation
Prism Central projects use built-in roles to scope what a user can do inside a project. Project Admin manages the project itself, its users and every VM or application in it. Developer can create and manage blueprints and the applications they launch. Consumer can provision VMs and applications from what the project offers and can manage the items they own, but cannot act on VMs owned by other users. Operator can run actions on existing VMs and applications in the project but cannot provision new ones. For an engineer who must deploy development VMs but must not delete production VMs in the same project, Consumer meets both conditions: self-service creation plus ownership-based limits. Project Admin is too broad because it controls all VMs in the project, including production. Operator cannot deploy VMs at all, and its actions apply to VMs it doesn't own, so it misses both parts of the requirement. Cluster Admin grants cluster-wide authority outside the project boundary and violates least privilege. Exam caveat: watch for role names that sound plausible but aren't Nutanix built-ins; the project roles are Project Admin, Developer, Consumer and Operator. Operational check: sign in as a test Consumer, deploy a VM, and confirm that delete is unavailable on a production VM owned by another user.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.