Nutanix NCP-MCA Dumps

To remove an application from Self-Service (formerly Calm) while keeping the VM up and running, the administrator should:

Go to the Manage tab of the application in Self-Service.

Select the Delete action.

By doing this, the application will be removed from the management of Self-Service, but the VM will remain running in the environment.

References:

Nutanix documentation on Managing Applications.

Nutanix Best Practices for Application Deletion.

The role required to create a remote Prism Central account within Self-Service (formerly Calm) is the Prism Admin role. Prism Admins have the necessary permissions to manage infrastructure components, including creating and configuring remote Prism Central accounts which are crucial for integrating and managing multi-cluster environments.

References:

Nutanix Calm documentation on RBAC Roles.

Nutanix Best Practices for Prism Central Management.

To automate the task of growing vDisks on multiple classes of VMs using Nutanix Playbooks, the administrator should follow these steps:

Create a custom Alert Policy:

Create an alert policy that triggers when the server's disk usage reaches 85% or above. This ensures the playbook is triggered based on the specified threshold.

Select Alert as the trigger:

Set the alert created in step 1 as the trigger for the playbook. This ties the alert condition to the execution of the playbook.

Select Email Action with custom message:

Add an action to send an email notification. This email should be sent prior to any work being started, to inform relevant stakeholders about the impending vDisk growth operation.

Add Action to Grow vDisks:

Add the action to grow the vDisks on the VMs. This step should include the necessary script or task that performs the vDisk growth operation on the specified VMs.

Based on the requirements and steps, the playbook should be structured as follows:

Step 1: Create a custom Alert Policy

Define the alert policy with the condition that disk usage on the VMs reaches 85% or higher.

Step 2: Select Alert as the trigger

Use the alert policy created in Step 1 as the trigger for the playbook.

Step 3: Select Email Action with custom message

Add an email action to notify relevant stakeholders before the vDisk growth task is initiated.

Step 4: Add Action to Grow vDisks

Include the necessary action to grow the vDisks on the VMs as required.

This structure ensures that the playbook is dynamically responsive to changes in server usage, sends notifications prior to execution, and performs the required vDisk growth operation automatically.