Nutanix Self-Service defines several user roles, each with specific permissions.
Documentation describes theConsumerrole as:
* Allowed todeploy applications from the Marketplace or assigned blueprints
* Allowed to performday-2 operations(power actions, snapshots, etc.)
* Restricted from modifying blueprints, environments, or project configurations
* Ideal for end users who need access to deploy and manage their workloadswithout administrator capabilities This matches exactly what the DevOps team requires.
Why the other roles are incorrect
* Developer (A):Can modify blueprints and environments - too much privilege.
* Project Admin (C):Full control over project resources - far more access than needed.
* Operator (D):Used for automation and operational oversight, not end-user VM deployment.
Thus,Consumer (B)is the correct and intended role.

To enforce different configurations for different types of workloads within the same Project, Nutanix Self- Service usesEnvironments.
* Environments:These are logical configurations within a Project that map to specific infrastructure settings. An administrator can define multiple environments (e.g., "Development" and "Production") within the "Engineering" project.
* Category Assignment:Within each Environment configuration, the administrator can define specific VM Categoriesthat will be automatically applied to any VM provisioned into that environment.
* Mapping:
* Production Environment:Assign the category Protection: async_1hr_repl (Matches requirement: Asynchronous remote replication every 1 hour).
* Development Environment:Assign the category Protection: snap_24_hr (Matches requirement:
Daily snapshots).
* Execution:When a user launches a blueprint, they select the target Environment (Dev or Prod). The system automatically tags the VMs with the categories defined in that environment, which in turn engages the Protection Policies associated with those tags.
Option B uses the wrong category values (sync_remote_repl instead of async). Options C and D suggest using Playbooks, but the native and most efficient method for applying deployment-time governance in Self-Service is via theProject Environmentsettings.

Comprehensive and Detailed Explanation
Self-Service platform sync allows Prism Central to periodically collect updates from external providers.
Nutanix documentation states that the providers supportingplatform sync with a 20-minute update window are:
* Nutanix (AHV)
* VMware (vSphere)
* AWS
These environments support the metadata collection necessary for tracking:
* IP changes
* Disk resizing
* VM availability
Thus, the valid set isNutanix, VMware, and AWS, makingOption Ccorrect.

To fully validate the integration between a Self-Service Project and a Playbook, the administrator must perform a test deploymentwithin the specific Project context.
* Project Context:Playbooks often rely on triggers (like Categories) or parameters that are applied specifically by the Project's environment settings. Running the Playbook independently (Option A) only tests the script logic, not the trigger or the project-specific inputs.
* End-to-End Validation:By deploying the blueprint associated with the Project (Option D), the administrator confirms:
* The Project correctly provisions the resources (Quotas/Environment).
* The Resources receive the correct Categories/Tags from the Project.
* The Playbook Trigger successfully fires upon detecting these specific Project-derived events.
* The Playbook executes successfully.
This is the only method that validates "both the Project and Playbook configurations" as a unified workflow.

Nutanix Intelligent Operations (X-Play) allows administrators to create custom automation playbooks by defining triggers and associated actions. The system provides a library of pre-built actions to simplify integration.
To integrate notifications with standard collaboration platforms, the administrator should select theAction specific to that platform. For example, theSlackandMicrosoft Teamsactions are natively available in the Action Gallery.
* Slack Action:Requires entering a Slack Token and Channel Name.
* Microsoft Teams Action:Requires entering a Webhook URL from the Teams instance.
Using these pre-built actions is the direct and recommended method for supported platforms, as opposed to configuring a generic Webhook manually (Option D) or modifying global settings (Option B).