Comprehensive and Detailed Explanation

When configuring a Self-Service Account for AWS , Prism Central must be able to:

Resolve AWS service endpoint URLs

Validate API calls via name-based resolution

Nutanix documentation specifies that DNS is required for all cloud-provider integrations, including AWS, Azure, and GCP.

Therefore, DNS is the required network element.

Correct answer: B

In Nutanix Self-Service (Calm), to protect sensitive data (such as passwords, keys, or personal tokens) from being displayed in plain text in the UI and Audit Logs, the developer must configure them as Secret Variables .

Secret Configuration: When defining a variable in a Blueprint or Runbook, there is a specific checkbox option to mark the variable as "Secret" (often indicated by a lock icon).

Behavior: Once a variable is marked as Secret, the Self-Service engine automatically masks the value (replacing it with asterisks *****) in all Audit Log outputs, task details, and the user interface. It is passed securely to the script execution environment but is never echoed back to the console logs in readable form.

Macros like jsonEncode (Option D) affect formatting, not security masking.

Comprehensive and Detailed Explanation

Nutanix Calm supports OS customization through Guest Customization , which:

Applies Sysprep for Windows

Injects configuration files

Sets hostnames, time zones, networking, and more

Runs scripts post-deployment

Sysprep is specifically executed during Windows Guest Customization .

Therefore, Option C: Guest Customization is correct.

The "Environment" construct in Nutanix Self-Service is designed specifically to abstract infrastructure details from the end user while ensuring correct placement.

Within a single Project, an administrator can define multiple Environments (e.g., "Development" and "Production").

The Development Environment is configured to map to the Development Cluster and its associated networks.

The Production Environment is configured to map to the Production Cluster and its associated networks.

When a blueprint is launched, the user (or the application profile) simply selects the target Environment. The Self-Service engine then automatically directs the provisioning to the specific cluster defined in that Environment's settings, ensuring correct placement without requiring the user to know cluster details or manual intervention.

For users to successfully deploy Marketplace Blueprints to a specific infrastructure, the Project must have a configured Environment .

The Gap: Merely adding the Account and whitelisting the Cluster in the Project settings (the "Infrastructure" tab) only authorizes access. It does not tell the Self-Service engine how to use that infrastructure (e.g., which Networks to attach, which Storage Containers to use, or what sizing policies to apply).

The Solution: The administrator must go to the Environments tab within the Project and Create a New Environment mapped to the new Account and Cluster.

Marketplace Logic: Marketplace blueprints are typically "Environment Agnostic." When a user launches one, they are prompted to select a destination Environment. If no Environment exists for the new cluster, the user cannot select it as a target for deployment.

In Nutanix Self-Service Runbooks, tasks that execute scripts (such as Shell for Linux or PowerShell for Windows) require a target destination. This target is defined as an Endpoint.

An Endpoint configures the connection details (IP address, port, connection protocol, and credentials) required to communicate with the remote machine where the script will run. Without selecting a valid Endpoint, the Runbook engine does not know where to send the script for execution.

To configure and enforce resource limits within a Nutanix Self-Service (formerly Calm) project, the specific governance component known as the Policy Engine must be active. 2

According to the Self-Service Administration and Operations Guide regarding the Policy Engine and Quotas Overview :

Enabling the Policy Engine: You enable and use the policy engine to enforce resource quota policies for infrastructure resources (compute, memory, and storage) on Nutanix and VMware accounts. 3

Prerequisite status: Until the policy engine is enabled in the Admin Center Settings, Prism Central cannot perform any quota checks or validation on resource consumption. 4

Availability: The options to define resource quota limits (such as vCPU, Memory, and Disk fields in the Project configuration) appear only when you enable the policy engine in your Prism Central instance. 5 If the policy engine is not enabled, the Quota section in the Projects pages remains unavailable. 6