NCP-MCA Exam Dumps - Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6 Exam

Calm can be deployed as a VM on ESXi or AHV hypervisors and leverage calm functionality without the Nutanix infrastructure. Calm can also be enabled inside of Prism Central, which is a VM that can run on any Nutanix supported hypervisor, including ESXi and AHV. However, Calm cannot be enabled inside of Prism Element, which is the management interface for each Nutanixcluster. Calm also cannot be deployed as a VM on Hyper-V, as this is not a supported hypervisor for Calm. References: Nutanix Calm Configuration and Training, Calm on ESXi Deployment | Nutanix Community, Nutanix Support & Insights

 A time trigger is a type of playbook trigger that allows the user to specify a schedule for running a playbook. This trigger is useful for automating tasks that need to be performed periodically or at a specific time. A manual trigger requires the user to initiate the playbook execution manually, which is not ideal for a recurring task. A report trigger is a type of playbook trigger that allows the user to run a playbook when a specific report is generated. However, this trigger does not guarantee that the report will be generated on the first of every month, as it depends on the report settings. A wait until day of month action is a type of playbook action that pauses the playbook execution until a specified day of the month. This action is unnecessary if the playbook already has a time trigger that specifies the desired schedule.

References:

• Nutanix Multicloud Automation Administration (NMCAA) course, Module 4: Playbooks, Lesson 4.1: Playbook Triggers
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam Blueprint Guide, Section 3.1: Create a playbook to automate IT operations using X-Play

The error message indicates that the password parameter is not a secret parameter, which means it is not encrypted and stored securely in the Calm database. This can happen when a Playbook is cloned from another Playbook that has a password parameter defined as a secret parameter. The cloned Playbook will inherit the password value from the original Playbook, but it will not be a secret parameter. To resolve this issue, the administrator needs to either delete the password parameter and create a new one as a secret parameter, or edit the password parameter and mark it as a secret parameter. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 15, section 4.2.1
• Nutanix Calm Playbooks
• Nutanix Calm Parameters

To create and execute a scaling action using Calm, the administrator should create the action under the service profile section of the blueprint and the application profile section of the blueprint. The service profile section defines the properties and actions of each service in the blueprint, such as the VM configuration, the scripts to run, and the scaling parameters. The application profile section defines the properties and actions of the entire application, such as the number of instances, the dependencies, and the scaling triggers. The administrator can then execute the scaling action in the Overview tab or the Services tab of the application, depending on the scope of the scaling action. References:

• Nutanix Certified Professional - Multicloud Automation, Page 18
• Nutanix Calm User Guide
• Nutanix Calm User Guide
• Nutanix Calm User Guide
• Nutanix Calm User Guide

To update the running configuration for a multi-VM application in AWS using the Manage tab for the application in Calm, the administrator needs to provide the provider information for the AWS account. This includes the access key, secret key, region, and VPC ID. If the provider information is missing, the administrator will not be able to perform any actions on theapplication from Calm. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 16, section 4.1.1. 

Calm integrates natively with AWS and AHV as providers. A provider is a cloud platform or infrastructure that hosts the application VMs or services. Calm supports various providers such as Nutanix, AWS, Azure, GCP, VMware, and Kubernetes. AWS and AHV are two of the most commonly used providers in Calm, as they offer scalability, flexibility, and cost-efficiency for deploying applications. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 11; Nutanix Calm User Guide, section 3.1.

Scaling VM replica settings allow you to specify the minimum, maximum, and default number of VMs that can be created from a blueprint service. The minimum and default values must be equal to or greater than the number of VMs needed at any time and at time of deployment, which is 2 in this case. The maximum value must be equal to or less than the project quota divided by the VM resources, which is 100/12 = 8 for vCPUs and 300/24 = 12 for memory. The lowest of these two values is the limit for the maximum value, which is 8. Therefore, the only option that meets all the requirements is B. MIN: 2, MAX: 7, Default: 2.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 10, Objective 3.1: Given a scenario, create a blueprint to deploy infrastructure and applications using Self-Service
• Nutanix Multicloud Automation Administration (NMCAA), Module 5: Self-Service, Lesson 5.2: Blueprint Design, slide 23: Scaling VM Replica Settings
• Nutanix Certified Professional Multicloud Automation (NCP-MCA) 6 Exam, page 10, Objective 3.1: Given a scenario, create a blueprint to deploy infrastructure and applications using Self-Service

An administrator can look to view a list of executed playbooks in two locations: Executions and Plays. The Executions page shows the status and details of all the playbooks that have been executed across all the projects. The Plays page shows the status and details of all the playbooks that have been executed within a specific project. The Lists page shows the predefined and custom lists that can be used as inputs for playbooks. The Dashboard page shows the overview and statistics of the X-Play service. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 3 - Validate Blueprints, Runbooks, Playbooks, and Automation Settings, page 4
• Nutanix Multicloud Automation Administration (NMCAA), Module 5 - X-Play, Lesson 5.3 - Playbook Management, page 2
• Nutanix Calm User Guide, X-Play, Executions

When a Blueprint is launched via Marketplace, it uses the credential that is configured in the Project Environment. If the credential is invalid, the Blueprint deployment will fail with a check login error. To fix this issue, the developer needs to verify and update the credential in the Project Environment and ensure that it has the required permissions to access the target infrastructure and applications. References: Nutanix Multicloud Automation Administration (NMCAA), page 29-30; [Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide] (https://www.nutanix.com/content/dam/nutanix/resources/support/ncp-mca-ebg.pdf), section 3.1.

To reduce the manual effort for the NOC personnel, the administrators can create a new Action that contains the custom Python script as an Execute task with a script type of EScript. This will allow the NOC personnel to run the script on any VM from the Calm UI or API without logging into each VM. To ensure the process is repeatable across all applications, the administrators can create a new Runbook that contains the same Action and assign it to the relevant Projects. This will enable the NOC personnel to run the script on multiple VMs across different applications in a single workflow. To provide audit history for management of the actions, the administrators can view the Execution History tab under the Runbook page for audit purposes. This will show the details of each Runbook execution, such as the status, duration, user, and logs. Alternatively, the administrators can also view the Audit tab under the Application view for audit purposes. This will show the history of all actions performed on the application, such as launch, update, delete, and run actions. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 18, section 4.2.1. 

The archived application logs within Prism Central can be found under Services > Calm > Settings. Calm automatically archives run logs of the deleted applications and custom actions that are older than three months. The administrator can download the archives within 7 days from the time of archive creation. For a running application, data is not archived for the system-generated Create actions. References: Nutanix Support & Insights

 In the context of Nutanix Multicloud Automation (NCP-MCA), the order of actions in a playbook is crucial for its successful execution. In this case, the playbook is designed to execute a script to fix a known problem in an application but keeps failing because it attempts to power off the VM and take a snapshot before executing the script. The correct order should be to execute the script first, then power off the VM if necessary, and finally take a snapshot. References: I found some references from Nutanix Multicloud Automation (NCP-MCA) Learning documents or resources that might be helpful for you:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam: This is the official exam blueprint guide that covers the objectives, topics, and skills required for the certification. It also provides some sample questions and answers.
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide: This is another version of the exam blueprint guide that has similar content as the previous one.
• Free Questions for NCP-MCA by certscare - p2pexams.com: This is a PDF document that contains 11 questions and answers for the NCP-MCA exam. The question you asked is one of them, and the answer is the same as mine.

The administrator should use a conditional playbook and create a playbook using alert to accomplish this task. A conditional playbook is a type of playbook that allows the administrator to define different actions based on certain conditions or criteria1. A playbook using alert is a type of playbook that is triggered by an alert policy that monitors the VM status2. By using these two features, the administrator can create a playbook that checks if the rebooted VM is the mission-critical VM and sends a notification to the on-call administrator, or else sends an email to the Operations team.

References:

• Nutanix Multicloud Automation Administration (NMCAA) course, Module 3: Nutanix X-Play, Lesson 2: Nutanix X-Play Playbooks, Topic: Conditional Playbooks
• Nutanix Multicloud Automation Administration (NMCAA) course, Module 4: Nutanix Calm Governance, Lesson 2: Nutanix Calm Alerts, Topic: Alert Policies and Playbooks
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5 Exam Blueprint Guide, Section 1: Describe and Differentiate Automation Concepts and Principles, Objective 1.3: Define the components of X-Play

 According to the Nutanix Multicloud Automation Administration (NMCAA) course1, you can create and configure multi-VM blueprints for the Nutanix, AWS, VMware, GCP, and Azure providers. However, according to the Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide2, the exam objectives only cover Nutanix and AWS as the providers for multi-VM blueprints. Therefore, the correct answer is C. Nutanix and E. Amazon AWS. References: Nutanix Multicloud Automation Administration (NMCAA) course and Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide

https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Calm-Admin-Operations-Guide-v3_6_2:nuc-macros-variables-overview-c.html

The error “Connection refused” can occur due to several reasons but in the context of running a script through Calm on VM, it is most likely caused by firewall restrictions or insufficient permissions. Option A suggests that the VM port is not allowed by the firewall, meaning that the firewall settings are preventing the connection. This could be because specific ports needed for the script to run are being blocked. Option B indicates that the credentials have insufficient permissions, meaning that the user or system trying to execute the script does not have the necessary permissions to establish a connection. Option C is unlikely because the VM should be ready before the script is executed. Option D is possible but not specific enough to explain the connection issue. References: You can find more information about this topic in the following sources:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 3 - Validate Blueprints, Runbooks, Playbooks, and Automation Settings, page 9
• Nutanix Multicloud Automation Administration (NMCAA), Module 5 - Troubleshooting, Lesson 1 - Troubleshooting Calm, page 5-4

Nutanix Calm is a cloud-agnostic automation and orchestration solution that can be deployed on Nutanix AHV or any public cloud platform, such as AWS, Azure, or GCP. Calm can also manage applications across multiple cloud environments, including hybrid clouds. Calm cannot be deployed on vSphere Essential Edition or VMware ESXi, as these are not supported hypervisors for Calm. However, Calm can manage existing VMs on vSphere or ESXi clusters through the VMware provider. References:

• Nutanix Calm Configuration and Training1
• Nutanix Calm Admin and Operations Guide2

A Playbook is a feature of Nutanix Calm that allows you to automate tasks based on certain triggers or events. You can use a Playbook to create a workflow that monitors the storage capacity of the cluster and sends an email notification to the IT Director when the capacity reaches a certain threshold. You can also use the Playbook to generate a forecast report that shows the projected storage usage and availability based on historical data and trends.

References:

• Nutanix Support & Insights, section “Playbooks”
• Managing Storage Resiliency is now Simpler than Ever - Nutanix, section “Updates to the Storage Summary Widget”
• Alert on resilient capacity of a cluster | Nutanix Community, section “What you can do is enable (check the warning checkbox) for this alert policy”

The port 5986 is used for PowerShell Remoting over HTTPS, which is a secure way of executing PowerShell commands on a remote Windows VM. Calm uses PowerShell Remoting to run scripts on Windows VMs as part of the blueprint actions. Therefore, the port 5986 needs to be opened on the VM firewall to allow the communication between Calm and the VM. The other ports are not related to PowerShell Remoting, as they are used for SQL Server (1433), Remote Desktop Protocol (3389), and PowerShell Remoting over HTTP (5985). References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam Blueprint Guide, page 10; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 3; Nutanix Calm User Guide,page 93.

 Categories are key-value pairs that you can use to tag and filter entities in Nutanix. There are two types of categories: system defined and user defined. System defined categories are built-in and cannot be deleted. User defined categories are created by the administrator and can be deleted if they are not used in any policy. Policies are rules that apply actions or restrictions to entities based on their categories. Flow policies are policies that control the network security and visibility of VMs. If a category is part of a flow policy, it cannot be deleted unless the policy is removed or modified. Therefore, the two conditions that could prevent an administrator from deleting a category are: the category is system defined, or the category is part of a flow policy. References:

• Nutanix Support & Insights: This is the official Nutanix documentation for categories, where you can find information about the types, usage, and deletion of categories.
• Nutanix Exam NCP-MCA Topic 1 Question 12 Discussion: This is a forum where you can find discussions and explanations for Nutanix certification exam questions, including question 12 from topic 1, which is related to your question.
• Nutanix Flow Overview: This is a Nutanix community post where you can learn more about Nutanix Flow and its policies.

To ensure the VMs are properly remediated, the Playbook actions should be added in the following order: Take a VM Snapshot, VM add Memory, Resolve Alert. This is because Memory Hot Add allows the administrator to increase the memory allocation of a running VM without powering it off. Taking a VM snapshot before adding memory provides a backup point in case of any issues. Resolving the alert after adding memory clears the notification and updates the status of the VM. Powering off the VM is not necessary and may cause downtime or disruption to the applications running on the VM. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 11; Nutanix Calm SaaS User Guide, section 4.2.3.

According to the Nutanix Calm Administration Guide1, the minimum system requirements for Prism Central are 32 GB of RAM and 8 vCPUs. If the production Prism Central has less than the minimum RAM, it may affect the performance of Calm and other services running on Prism Cen

Autopilot is a feature of Nutanix Calm that allows the administrator to automate the execution of playbooks based on predefined conditions or triggers. Autopilot can optimizethe performance, availability, and cost of applications by applying the appropriate actions in response to events or metrics. Before configuring autopilot, the administrator must be aware of the following limitations12:

• Autopilot never waits for approvals. This means that the administrator must ensure that the playbooks are tested and verified before enabling autopilot. Autopilot will execute the playbooks without any human intervention or confirmation.
• Autopilot feature only applies to metric-based alerts as triggers. This means that the administrator can only use metrics from the Nutanix Prism Central or the Nutanix Karbon clusters as the conditions for triggering the playbooks. Autopilot does not support other types of triggers such as schedules, webhooks, or manual triggers. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, page 10; Nutanix Calm SaaS User Guide, section 4.3.

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

Substrates are the components of a blueprint that define the cloud resources and configurations for deploying VMs or applications. Substrates can be associated with different cloud accounts, such as AWS, Azure, GCP, or Nutanix, to enable multicloud deployments. By using substrates, an administrator can create a blueprint that can deploy VMs to multiple clouds, depending on the availability, cost, or performance requirements.

References:

• Nutanix Multicloud Automation Administration (NMCAA) course, Module 3: Blueprints, Lesson 3.2: Substrates1
• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 2.1: Create a blueprint to deploy infrastructure and applications using Nutanix Calm2

The Task Library is a centralized repository of tasks that can be reused across multiple blueprints. The administrator can publish a task to the Task Library by clicking on the Publish icon in the task editor. The task will then be available in the Task Library tab under the Tasks section in the Calm UI. The administrator can select the task from the TaskLibrary and drag and drop it into another blueprint. This way, the administrator can reuse the task with the least amount of effort.

References:

• Nutanix Certified Professional Multicloud Automation (NCP-MCA) 6 Exam, page 11
• Nutanix University - NCP-MCA 6 Exam Prep - Tasks and Task Library

The Consumer can ensure all underlying VMs are deleted with the removal of the application by going to the Manage tab of the application and selecting the Hard Delete action. This option will delete the application and all its associated resources from the Nutanix platform, without leaving any traces or backups. This option is useful when the application is no longer needed or has to be removed for compliance reasons.

From the Applications page, selecting the checkbox next to the application and selecting Delete from the action’s menu will not delete all underlying VMs. This option will only delete the application from the Calm UI, but not from the Nutanix platform. The application and its resources will still be available in the Nutanix cluster and can be restored from the Calm UI using the Restore action.

From the Marketplace page, selecting the checkbox next to the application and selecting Delete from the actions menu will not delete the application or its underlying VMs. This option will only delete the application from the Marketplace, but not from the Calm UI or the Nutanix platform. The application and its resources will still be available in the Calm UI and the Nutanix cluster.

Going to the Manage tab of the application and selecting the Delete action will also not delete all underlying VMs. This option will only delete the application from the Calm UI, but not from the Nutanix platform. The application and its resources will still be available in the Nutanix cluster and can be restored from the Calm UI using the Restore action.

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 2: Deploy and Configure Self-service and Related Components

The correct method to result in unique names per VM when scaling out a Service in a Calm Blueprint is to use the macro variable @@{calm_array_index}@@ in the Service VM Name field (Option B). This variable will append a unique index number to each VM name based on the scale-out count. For example, if the Service VM Name is MyAppVM-@@{calm_array_index}@@ and the scale-out count is 3, the resulting VM names will be MyAppVM-0, MyAppVM-1, and MyAppVM-2. Option A is incorrect because the tag in the sysprep file will only affect the hostname of the guest OS, not the VM name in the cloud provider. Option C is incorrect because calling an external Python eScript to register the VM name in DNS will not change the VM name in the cloudprovider either. Option D is incorrect because setting the VM Name field to allow user edits at launch will require manual input from the user for each VM, which is not scalable or automated.

References: The information can be verified from Nutanix official training and certification documents available at Nutanix Training & Certification. You can also check out the Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam guide for more details on the exam objectives and format. Additionally, you can watch the Nutanix Calm - Multicloud Automation playlist on YouTube for some video tutorials on Nutanix Calm features and functionalities.

 In order to add users to a Project, the Prism Central administrator must first configure an Authentication Directory. This is a service that provides user authentication and authorization for Prism Central, such as Active Directory or OpenLDAP. By configuring an Authentication Directory, the administrator can enable users to log in to Prism Central using their existing credentials and assign them roles and permissions based on their group membership. The administrator can also create local user accounts for users who do not belong to any Authentication Directory.

References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) Exam Blueprint Guide, Section 2, Objective 2.5
• Nutanix Multicloud Automation Administration (NMCAA) Course, Module 2, Lesson 2.2
• Configuring Authentication | Nutanix Community

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:
• 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”

The Plays dashboard in Prism Central provides a centralized view of all the Playbooks that have been executed across the clusters registered with Prism Central. It shows the status, duration, and output of each Playbook run, as well as the details of the triggers, targets, and actions involved. An administrator can use the Plays dashboard to troubleshoot why a Playbook failed to grow the memory of a VM by checking the error messages, logs, and output of the Playbook run. The other options are not the correct places to check for Playbook failures, as they do not provide the same level of information and visibility as the Plays dashboard. References: Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6 Exam, Nutanix Exam NCP-MCA Topic 4 Question 20 Discussion

When configuring Playbooks to automate the scaling of CPU and memory resources for VMs, the administrator should consider the following prerequisites:

• CPU can be added to a powered on VM if the guest OS supports it. This is also known as hot-plug CPU. The administrator should check the compatibility of the guest OS and the hypervisor before enabling this feature. For example, Windows Server 2019 supports hot-plug CPU on AHV, ESXi, and Hyper-V, but not on XenServer1.
• Memory can be removed from a powered on VM if the guest OS supports it. This is also known as hot-unplug memory. The administrator should check the compatibility of the guest OS and the hypervisor before enabling this feature. For example, Linux supports hot-unplug memory on AHV, ESXi, and XenServer, but not on Hyper-V2.
• VM must be powered off to add CPU if the guest OS does not support hot-plug CPU. This is also known as cold-plug CPU. The administrator should plan for the downtime required to power off and power on the VM after adding CPU.
• VM must be powered off to reduce memory if the guest OS does not support hot-unplug memory. This is also known as cold-unplug memory. The administrator should plan for the downtime required to power off and power on the VM after reducing memory. References: Nutanix Multicloud Automation Administration (NMCAA), page 10; Nutanix Certified Professional - Multicloud Automation (NCP-MCA), section 3; Nutanix Support Portal - Guest OS Compatibility Matrix

 The best way to automate the entire database and application deployments is to use a combination of Nutanix Calm and Nutanix Era. Nutanix Calm is a multicloud automation platform that allows you to create blueprints to deploy and manage infrastructure and applications across different cloud environments. Nutanix Era is a database management platform that allows you to provision, clone, patch, refresh, and restore databases in a simplified and automated way. By creating a Calm blueprint that deploys applications and calls Era APIs to automate database deployments, you can achieve faster and consistent releases, as well as reduce the manual effort and complexity involved in the process. You can also leverage the features of Calm and Era, such as self-service, governance, showback, backup, and recovery, to enhance the efficiency and security of your deployments. References: 

https://www.nutanix.com/support-services/training-certification/certifications/certification-details-nutanix-certified-professional-multicloud-automation-v6-5

https://www.nutanix.com/content/dam/nutanix/resources/support/ds-ncp-mca.pdf

When launching Calm blueprints, there are two view options available: Developer and Consumer. The Developer view allows you to create, edit, and manage blueprints, as well as access advanced features such as macros, actions, and scripts. The Consumer view allows you to launch and manage applications from the Marketplace, as well as access basic features such as variables, tasks, and alerts. The view option is determined by the role assigned to the user in the project. Users with the Project Admin or Project Auditor role can switch between the Developer and Consumer views, while users with the Project User role can only access the Consumer view. References:

• Nutanix Certified Professional - Multicloud Automation (NCP-MCA) v6.5, Section 1 - Describe and Differentiate Automation Concepts and Principles, page 3
• Nutanix Multicloud Automation Administration (NMCAA), Module 2 - Nutanix Calm, Lesson 2.1 - Nutanix Calm Overview, page 9
• Nutanix Calm User Guide, Introduction to Nutanix Calm, Nutanix Calm User Interface