Nutanix Updated NCP-MCA Exam Questions and Answers by peyton

The most optimal way to correct the failed deployment is to retry the failed deployment. This option allows the administrator to resume the deployment from the point of failure, without having to redeploy the entire application or create a new runbook. Retrying the failed deployment also preserves the application state and configuration, and avoids creating duplicate resources or conflicts.

Redeploying the application is not the best option, because it requires the administrator to delete the existing application and launch a new one from scratch. This option wastes time and resources, and may result in data loss or inconsistency.

Creating a runbook to retry is also not the best option, because it requires the administrator to write a custom script or workflow to handle the retry logic. This option adds complexity and overhead to the automation process, and may not be compatible with the original blueprint or application.

Rewriting the blueprint to have error handling is a valid option, but it is not the most optimal one. This option requires the administrator to modify the blueprint code and add logic to handle different types of errors and exceptions. This option improves the robustness and reliability of the blueprint, but it does not correct the failed deployment itself. The administrator still has to redeploy the application or retry the failed deployment after rewriting the blueprint.

References:

Nutanix Calm User Guide: Chapter 6: Managing Applications

Nutanix Calm DSL User Guide: Chapter 4: Blueprints

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide: Section 3: Validate Blueprints, Runbooks, Playbooks, and Automation Settings

The Calm Marketplace acts as an application store, providing end users with a catalog of available applications. By default, Calm comes pre-seeded with validated Blueprints for multiple open source and enterprise applications. These are the set of pre-seeded application Blueprints. Additionally, Marketplace Manager acts as a staging area for publishing default and user-created Blueprints to your local Marketplace. These are the published and versioned Blueprints. The other two options, library of executable tasks and store of all Blueprints created in Calm, are not features of the Calm Marketplace. References: Calm: Marketplace - Read the Docs and Calm: Marketplace - Read the Docs

 The alert in Prism Central indicates that Calm showback is not able to reach the beam service. This could be due to network connectivity issues or incorrect configurations. The administrator should check the DNS configuration in Prism Central (Option A) to ensure that it is correctly configured to allow communication with the Beam service. Additionally, checking if Prism Element is configured with Proxy settings (Option C) is essential as it can also affect the communication between Calm and Beam. Pulse (Option B) and Flow (Option D) are not related to the Calm showback feature and do not impact its functionality.

References:

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 2 - Deploy and Configure Nutanix Calm and Related Components, Objective 2.4 - Identify required configuration settings for a Nutanix Calm deployment

Enabling and Disabling Showback in Calm | Nutanix Community

The error indicates that there is an issue with DNS resolution while executing the delete script. To resolve this and successfully delete the deployment, the administrator can:

Perform a Stop: Stop the application or VM to ensure that no processes are actively using the resources. This might resolve any temporary network or DNS issues.

Manually delete the VM: If stopping the application does not resolve the issue, manually deleting the VM from the Prism Central or the respective hypervisor management console is necessary. This will bypass the script error.

References:

Nutanix documentation on Managing Applications.

Nutanix Best Practices for Manual VM Management.