NCP-MCA Exam Results

The feature within Nutanix Self-Service (Calm) designed specifically for publishing blueprints to end-users is theMarketplace.

Marketplace:This component acts as an app store for the organization. Administrators and developers create Blueprints and thenpublishthem to the Marketplace.

Process:The "Marketplace and Application Management" capability encompasses the workflow of submitting a blueprint for approval, versioning it, and making it visible to users based on their Project entitlements.

Consumption:Once published, users do not access the raw blueprint design canvas; instead, they access the Marketplace Item to launch (consume) the application.

While "Unified Multi-Cloud Orchestration" describes the platform's broad goal, and "DSL" is a method for creating code-based blueprints, "Marketplace" is the specific functional area for publishing and consumption.

To create or configure aCustom Providerin Nutanix Self-Service (Calm), the administrator typically defines the provider's schema (endpoints, variables, and actions) using theSelf-Service DSL(Domain Specific Language) or by constructing a definition file.

YAML Definition:The standard workflow for creating complex custom providers involves defining the provider logic in Python (via the DSL) and compiling it into aYAMLfile, or writing the YAML definition directly.

Import/Update:This YAML file is then uploaded to the Self-Service interface to create or update the Provider definition. This allows the administrator to extend Self-Service capabilities to any infrastructure or service that has an API, beyond the native supported providers.

Note:While the question option phrasing ("Update the blueprint...") may be imprecise, the action of uploading aYAML fileis the specific mechanism associated with defining Custom Providers and DSL-based constructs in Nutanix Self-Service.

InIntelligent Operations (X-Play) Playbooks, the syntax for string interpolation (using parameters) differs from Self-Service (Calm).

Playbook Syntax:X-Play uses thedouble curly bracesyntax {{ ... }} to reference parameters.

Example:To reference the name of the entity that triggered the playbook, the correct parameter string is {{trigger[0].source_entity_info.name}} or {{trigger[0].alert_entity_info.name}} depending on the trigger type.

Contrast:@@{...}@@ (Option B) is the syntax used inSelf-Service (Calm)macros, not X-Play Playbooks.

The most efficient and scalable method for managing user access in Nutanix Self-Service Projects is leveraging existing Identity Providers (such as Active Directory).

Add an Active Directory group to a role:When adding users to a Project, the administrator can select an entireDirectory Group(AD Group) and assign a specific Project Role (e.g., Developer, Consumer, Operator) to that group.

Result:All users currently in that AD group, and any users added to that AD group in the future, automatically inherit the assigned Project Role. This eliminates the need to manually manage individual user accounts (Option D) or maintain separate local groups (Option A) within Prism Central.