NCP-MCA Exam Dumps and Practice Questions

In Nutanix Calm, a Blueprint is the fundamental building block that defines infrastructure automation templates. The core components of a Blueprint are:

• Services: Represent the VMs or applications that will be deployed
• Application Profiles: Define the deployment configurations, packages, and credentials needed for provisioning
• Deployment Configurations: Specify environment-specific settings like resource sizing and placement

These three elements together form the complete structure of a Blueprint, enabling administrators and developers to create reusable automation templates for infrastructure provisioning and application deployment.

To create a blueprint that deploys a Linux VM with NGINX, the developer needs several prerequisites. Most critically, a cloud provider account (such as Nutanix, AWS, Azure, or vSphere) must be associated with the project. Additionally, while not always listed as a separate requirement, the developer must have operator-level permissions (which they have) and access to appropriate VM templates or images. The provider account is the foundational requirement that enables all blueprint provisioning capabilities.

For a Self-Service restore to be possible, there must first be an existing backup of the application. This backup is created using the Snapshot action in the application's lifecycle. Without a prior snapshot, there is nothing to restore from.

To have a task appear in the Library for reuse:

• Creation as a reusable component:
  • Build the task within Nutanix Calm using the task editor
  • Define inputs, outputs, and task logic
  • Configure error handling and retry policies
• Library registration:
  • Save the task with a descriptive name
  • Provide clear documentation and tags for discoverability
  • Ensure proper categorization for easy searching
• Making tasks available:
  • Local Library: Tasks are available within the current workspace/account
  • Shared Library: Tasks can be shared across teams or organizations if configured
  • Calm Marketplace: Published tasks can be made available to the broader community
• Reusing Library tasks:
  • Browse the Library in Calm UI or IDE
  • Drag tasks into blueprints and playbooks
  • Task inputs can be mapped to blueprint/playbook variables
• Benefits of Library tasks:
  • Code reuse across multiple blueprints
  • Standardization of common operations
  • Easier maintenance and updates
  • Faster blueprint development

The Library is the central repository for reusable automation components in Nutanix Calm.

To make an application available for deployment only to the QA team, an administrator must assign the blueprint to a specific Project and then configure that Project's membership to include only members of the QA team. This ensures access control at both the blueprint and project level.