Nutanix Certified Professional / NCP-MCA 5 NCP-MCA Full Course Free

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.

 If a Blueprint deployment fails, the administrator can use the Continue option in the Self-Service Portal to resume the deployment from the point of failure. This option will retry the failed task and continue with the remaining tasks in the Blueprint. The administrator does not need to delete the application or launch a new one, as this would waste time and resources. Saving the Blueprint will not automatically retry the task, as the Blueprint is only a template for the deployment.

References:

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 3, Objective 3.1: Determine the causes of a Blueprint or Runbook deployment failure.

Nutanix NCP-MCA Certification Exam Sample Questions, Question 17.

 The error code 1314 indicates that the user does not have the required privilege to perform the requested operation. This means that the credentials provided in the Calm Blueprint are not valid or do not have enough permissions to run the script on the Windows machine. To fix this issue, the administrator should verify the credentials and ensure that they have the appropriate rights to execute the script, such as local administrator or domain administrator privileges. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 15, section 3.3. Nutanix Multicloud Automation Administration (NMCAA) course, module 5, lesson 2. Nutanix NCP-MCA Certification Exam Sample Questions, question 25

To automate the creation of a new user in GitLab for every new development environment, the administrator should perform the following tasks within a Calm blueprint:

Create an HTTP pre-create task to create the user in GitLab via REST API. This task will send an HTTP request to the GitLab server with the user information and credentials, and receive a response with the user ID and status. The administrator can use the response to verify the user creation and store the user ID as a variable for later use.

Create runtime-editable variables for user and password in the blueprint. These variables will allow the administrator to specify the user name and password for the new GitLab user at the time of launching the blueprint. The variables can be passed as parameters to the HTTP pre-create task and used in the REST API call.

The other two options are not correct because:

Adding a task within the service to ask for user and password at runtime is redundant and unnecessary, as the runtime-editable variables can already provide this functionality.

Creating a task script to login with ssh to GitLab and create a random user and password is not a good practice, as it exposes the GitLab server to security risks and does not use the REST API that GitLab provides for user management. References:

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam, page 17

Nutanix Calm User Guide, section “HTTP Task”

GitLab API Documentation, section “Create user”