To provide users with access to Nutanix Self-Service (formerly Calm), an administrator must configure Role- Based Access Control (RBAC) within the context of a Project.
Access to Self-Service is not global; it is defined at the Project level.1An administrator must:
* Add the user (or their Active Directory group) to a Project.
* Assign a Roleto that user within the project.
* Project Admin:Full control over the project.2
* Developer:Can create blueprints and applications.
* Consumer:Can only launch blueprints available in the Marketplace.3
* Operator:Can perform day-2 operations on existing applications.4
Without an assigned role in a project, a user cannot access the Self-Service portal features or view any blueprints.

According to the Self-Service Administration Guide regardingError Handling in Runbook and Blueprint Tasks, there is a specific documented limitation regarding VM Power actions.
* General Behavior:The error handling mechanism is designed to allow workflows to continue or alert when tasks (including VM Power On/Off) fail for reasons such as the Prism Central being unreachable or the VM being deleted.
* The Exception (Option D):The documentation explicitly states:"Error handling, however, does not take into account the power on, power off, or restart task failures because of authentication errors."
* If the "VM Power On" task fails specifically due to an authentication issue (e.g., token expiry or connectivity preventing authentication with the host), the standard error handling flow may not trigger as expected, matching the scenario described.
* Option A is incorrect because Self-Servicecanhandle infrastructure task failures (like Power On), with specific exceptions like the one noted in D.

In Nutanix Prism Central Disaster Recovery, when a Prism Central instance fails over to a recovered site, several automation components-including Playbooks-must be revalidated. Nutanix documentation clearly states:
* Playbooks store encrypted credentials locally in the Prism Central database.
* When Prism Central is recovered on a DR site, the credential encryption keys donottransfer.
* As a result,any credentials previously stored in Playbooks become invalidand must be manually re- entered.
This requirement ensures that the scripts, tasks, remediation sequences, and integrations invoked by the Playbook can authenticate properly after recovery.
Therefore:
* Playbookscannot automatically use previously stored credentialsafter a DR failover.
* Administrators mustre-enter all credentialsin enabled Playbooks so the automation continues functioning.
Hence, OptionCis correct.
Options A and D are incorrect because Playbooks donotautomatically retain functional credentials after DR recovery.
Option B is incorrect because the presence or absence of a credential provider does not change the need to re- enter credentials.

To "compile a list" of entities using Intelligent Operations (X-Play) without manually tracking them, the administrator should leverage theCategorizationfeature, which acts as a dynamic tagging system.
* Trigger (Event):The restoration of a VM from a snapshot generates a systemEvent(e.g., "VM Restored" or "Clone from Snapshot"). The Playbook must be configured with theEvent Triggerto detect this specific action immediately when it occurs.
* Action (Assign Category):The Playbook should then execute theAssign Categoryaction. The administrator can define a specific category, such as Recovery:Restored.
* Result:As the administrator restores the VMs (either manually or via script), the Playbook automatically tags each one with the Recovery:Restored category. The administrator can then simply filter the Prism Central VM list by this category to see the compiled list of all recovered VMs.
Options B and D are incorrect because a successful snapshot restoration is anEvent, not anAlert(which indicates a fault or threshold breach). Option C is incorrect because a Time Trigger cannot react to the specific action of a restore operation.

To create or configure aCustom Providerin Nutanix Self-Service (Calm), the administrator typically defines the provider's schema (endpoints, variables, and actions) using theSelf-Service DSL(Domain Specific Language) or by constructing a definition file.
* YAML Definition:The standard workflow for creating complex custom providers involves defining the provider logic in Python (via the DSL) and compiling it into aYAMLfile, or writing the YAML definition directly.
* Import/Update:This YAML file is then uploaded to the Self-Service interface to create or update the Provider definition. This allows the administrator to extend Self-Service capabilities to any infrastructure or service that has an API, beyond the native supported providers.
* Note:While the question option phrasing ("Update the blueprint...") may be imprecise, the action of uploading aYAML fileis the specific mechanism associated with defining Custom Providers and DSL- based constructs in Nutanix Self-Service.