To ensure that Prism Central sends the appropriate notifications (Alerts/Events) to ServiceNow—allowing ServiceNow's Event Management to process them via Event Rules —the administrator must configure an X-Play Playbook that exports these alerts.

According to the Prism Central Intelligent Operations Guide (ServiceNow Integration):

Export of alerts from Prism Central is achieved by creating an X-Play playbook.

The administrator should use the Alerts Matching Criteria trigger. This trigger allows the administrator to define the scope of the export (e.g., "All Critical Alerts" or specific categories).

The Playbook then uses the Send Alert to ServiceNow action to push these matching alerts to the ServiceNow Event API.

By configuring a Playbook with the Alerts Matching Criteria trigger, the administrator ensures a continuous, policy-based flow of event data into ServiceNow, satisfying the requirement for Event Rules to have data to process. Option A describes the action but lacks the governing trigger mechanism (matching criteria) that defines "appropriate" events for the integration.

When creating a Runbook that involves power cycling a VM (Restart), there is a gap in connectivity while the Guest OS reboots and network services initialize.

If the Runbook moves immediately from the "VM Restart" task to the "Add new credential" task (which likely uses SSH or PowerShell to connect to the VM), the connection will fail because the VM is not yet accessible.

To correct this, the administrator must insert a Delay task between the restart and the configuration step.

The sequence should be:

VM Restart: Initiates the reboot.

Delay: Pauses the runbook execution for a set duration (e.g., 60-120 seconds) to allow the OS to boot.

Add new credential: Executes the script once the VM is back online.

Nutanix Self-Service (formerly Calm) uses Services, app profiles, packages, substrates, and actions as the building blocks for a blueprint to define applications.

A Service is the core logical entity within a blueprint. An application is made up of multiple components (or services) working together, such as a Database Service and a Web Server Service. Each service defines the specific infrastructure (VM), software packages, and operations required for that component of the application.

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

Marketplace: This component acts as an app store for the organization. Administrators and developers create Blueprints and then publish them 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 automate post-deployment configuration within Nutanix Self-Service (Calm), the administrator must define Tasks within the Service lifecycle of the Blueprint.

Service Lifecycle: Every Service (VM) in a blueprint has lifecycle actions, such as Create, Start, Stop, and Delete.

Automation Implementation: The administrator should add specific tasks (e.g., HTTP tasks for API calls to monitoring, Scripts for tagging/email) specifically to the Create action (or Package Install phase) of the Service.

Execution: When the blueprint is launched, the Orchestrator provisions the VM (Substrate) and then automatically executes these defined tasks in sequence. This ensures that tagging, monitoring, and notification happen immediately and consistently for every deployment without manual intervention.

When creating a variable in a Nutanix Self-Service Blueprint or Runbook, the administrator must select a Data Type . The standard supported data types are String , Integer , Date , Time , and DateTime .

String (Single-line): This is the fundamental text data type (typically just labeled "String" in the UI). It is used for standard alphanumeric inputs.

Input Options: While a String variable can be configured with an attribute to accept "Multi-line" input (useful for SSH keys or scripts), the base data type itself is String (which defaults to single-line).

Invalid Options: "Multi-line integer" is not a valid type. "Year Month Day" is a format description, not the name of the Date data type. Therefore, Single-line string (representing the standard String type) is the correct available option among the choices.

According to the Nutanix Prism Central Admin Guide, a category is a grouping of entities into key-value pairs. Categories are used to group entities (such as VMs, hosts, or subnets) based on specific criteria (e.g., Department: Marketing or Environment: Production).

Once entities are assigned to a category, administrators can link policies (such as security, protection, or automation playbooks) to the category rather than to individual entities. This allows for scalable and dynamic management, as any new entity tagged with that category will automatically inherit the associated policies.

Nutanix Calm and Self-Service automation workflows require validation within the same execution context used by end users. Nutanix documentation specifies the following principles:

1. Playbook validation requires execution in the same user and project context

Playbooks that target resources using a CalmProject category must be tested in the exact context in which they will operate.

The "Execute on behalf of" option allows the administrator to run the Playbook as if a project user initiated it , ensuring validation of:

Project-based scoping

User permissions

Category-based triggers

Playbook logic and automation flow

This matches the documented requirement that Playbooks must be validated under the intended user execution model , making Option B correct .

2. Deployment must occur inside the Project to activate category-driven Playbooks

Blueprint deployments only trigger Playbooks when:

The deployment occurs inside the Project , and

The VM receives metadata (such as CalmProject category) associated with that Project.

Nutanix Calm documentation highlights that Playbooks relying on Project categories only activate when VMs are provisioned from that specific Project .

Deploying from the Marketplace does not guarantee that the correct project context or categories will be applied.

Thus, verifying Playbook execution requires deploying the blueprint assigned to the Project, making Option D correct .

Why the other options are incorrect

❌ Option A – “Execute”

This executes Playbooks only in the admin context, not the Project context. It does not validate permissions, user behavior, or category-based triggers required for Self-Service operation.

❌ Option C – Marketplace deployment

Marketplace deployments do not necessarily apply Project-specific categories or metadata, so they cannot reliably test integration with Playbooks bound to a Project.

In Nutanix Self-Service (Calm) Projects, the "Allow Collaboration" setting controls the visibility and management of entities shared among project members.

Allow Collaboration Enabled: This allows any group member to see the VMs, applications, scheduler jobs, and other objects created by other members of the group. With the appropriate role permissions, they can also modify these shared entities.

Allow Collaboration Disabled: Project users can manage only the objects that they strictly created themselves. They cannot view or edit objects created by other users, even if they are in the same project.

To modify a Scheduler Job created by another user, "Allow Collaboration" must be enabled for that Project.

The visibility of clusters within a Self-Service Project is strictly controlled by the Infrastructure (or Accounts) configuration within the Project settings.

Infrastructure Whitelisting: When configuring a Project, the administrator must select which Accounts and Clusters are available for use. This is often referred to as defining the Project Scope or whitelisting infrastructure.

The Cause: If users can see and create Environments targeting "Production Clusters," it is because the administrator explicitly selected (whitelisted) those Production Clusters in the Project's Infrastructure tab.

Environments vs. Infrastructure: Environments are definitions created using the allowed infrastructure. Option D is less accurate because you whitelist the Infrastructure (resources), and then Environments are created on top of them. The root cause of the resource availability is the infrastructure whitelist in the Project Scope.