In Nutanix Self-Service (Calm), a Quota Policy limits the total infrastructure resources that can be consumed by a Project.5 When configuring a Project, the administrator sets limits for the following specific resources:
* vCPUs:The total number of virtual CPUs allocated to VMs in the project.
* Memory:The total amount of RAM (in GiB) allocated to VMs.
* Disk:The total storage capacity (in GiB) allocated to VMs.
These quotas are enforced during the provisioning process. If a user attempts to launch a blueprint that would cause the project to exceed these defined limits (vCPU, Memory, or Disk), the deployment will fail. Quotas do not monitor IOPs, NIC counts, or the number of blueprints stored.

For users to successfully deploy Marketplace Blueprints to a specific infrastructure, the Project must have a configuredEnvironment.
* The Gap:Merely adding the Account and whitelisting the Cluster in the Project settings (the
"Infrastructure" tab) onlyauthorizesaccess. It does not tell the Self-Service enginehowto use that infrastructure (e.g., which Networks to attach, which Storage Containers to use, or what sizing policies to apply).
* The Solution:The administrator must go to theEnvironmentstab within the Project andCreate a New Environmentmapped to the new Account and Cluster.
* Marketplace Logic:Marketplace blueprints are typically "Environment Agnostic." When a user launches one, they are prompted to select a destination Environment. If no Environment exists for the new cluster, the user cannot select it as a target for deployment.

Nutanix Self-Service governance supportsApproval Policiesthat enforce control over resource consumption and automation actions. Nutanix documentation states that approval policies:
* Apply toblueprint deployments,runbook executions,day-2 actions, orresource scale-up requests.
* Requireexplicit authorizationfrom a designated approver before the action proceeds.
* Provide governance to ensure resource usage aligns with organizational policies.
Thus, Approval Policies existspecifically to require authorization before a user-triggered task is executed
, makingOption C correct.
Options A, B, and D are unrelated to approval workflows.

To automate a remediation action (like restarting a VM) based on a specific performance threshold (like CPU usage > 90%), the administrator must useIntelligent Operations (X-Play)with an event-driven trigger.
* Alert-Based Trigger:The administrator first ensures there is an Alert Policy in Prism Central for "VM High CPU" configured with a threshold of 90%.
* Playbook Configuration:The administrator then creates a Playbook and selects theAlerttrigger (or Alerts Matching Criteriatrigger). They link this trigger to the specific CPU alert policy.
* Action:The administrator adds theVM Reboot(or Power Cycle) action to the Playbook.
* Result:As soon as the system detects the CPU exceeding 90%, the Alert fires, which immediately triggers the Playbook to reboot the VM without human intervention.
* Options A (Scheduled) and C (Manual) do not meet the requirement of "whenever it exceeds," which implies real-time reaction. Option B is incorrect because Project Quotas manage resource allocation limits, not runtime performance monitoring or remediation.

The most efficient and scalable method for managing user access in Nutanix Self-Service Projects is leveraging existing Identity Providers (such as Active Directory).
* Add an Active Directory group to a role:When adding users to a Project, the administrator can select an entireDirectory Group(AD Group) and assign a specific Project Role (e.g., Developer, Consumer, Operator) to that group.
* Result:All users currently in that AD group, and any users added to that AD group in the future, automatically inherit the assigned Project Role. This eliminates the need to manually manage individual user accounts (Option D) or maintain separate local groups (Option A) within Prism Central.