Nutanix Certified Professional - Multicloud Automation Free Sample Questions

Nutanix Calm provides a native integration for external key/value-based secret stores like HashiCorp Vault. By defining a variable of type 'Secret', the administrator can directly reference a secret stored in Vault. Calm securely retrieves the value at runtime and injects it into the script or application, preventing the secret from being exposed in the blueprint definition or logs. This is the most secure and streamlined method. While an eScript could work, it requires custom coding and credential management within the script, which is less secure than the native integration. Runtime variables would expose the secret to the end-user, violating the security requirement.

The log indicates a specific 'Authentication Error' at the 'VM Powershell' action step. This action executes a script inside the guest OS of the target VM. An authentication error at this stage points directly to the credentials (username/password) used to log in to the guest OS. The 'VM Snapshot' action succeeded because it is an API call to the hypervisor (AHV/ESXi) and does not require guest OS credentials. A network connectivity issue would likely result in a 'Connection Timed Out' error, not an authentication error. The Slack notification failure is a symptom of the playbook halting on error, not the cause.

X-Play Playbooks are ideal for event-driven automation. The Incident Response process is triggered by an event (a VM alert), making a Playbook the perfect fit for this reactive, cross-system workflow.

Calm Runbooks are designed for procedural, on-demand task automation that can be executed by a user. The Application Update is a specific, user-initiated sequence of tasks, which is the primary use case for a Runbook. It provides a simple, repeatable way for a developer to perform this action.

Nutanix Calm blueprints have a built-in dependency management system. By dragging a connector from the database service to the web server service in the visual editor, the administrator creates a dependency. This explicitly tells Calm to complete the 'Create' action of the web server service before starting the 'Create' action of the database service, ensuring the correct orchestration sequence. Using a delay is unreliable as the web server configuration time can vary. Placing tasks in the Application Profile does not control the order of service creation.

False. Published Marketplace blueprints are immutable to ensure consistency and stability for consumers. To update a Marketplace item, an administrator must first edit the source blueprint, save the changes, and then publish it as a new version to the Marketplace. Consumers can then choose to use the new version for future deployments.

The 'Projects' configuration page in Prism Central (under Administration) is the central location for managing project settings, including resource quotas. This page displays a summary of all projects, showing the configured quotas (VCPUs, Memory, Storage) and the current usage for each. An administrator can directly compare the student project's usage against its defined limits here to validate the quota exceeded error. The Audit trail shows actions but doesn't aggregate resource usage. The Tasks view shows individual task status, not resource totals.

The correct method for deploying a variable number of identical VMs is to define the service as an array, also known as using replicas. In the blueprint, you can set the replica count to be determined by a runtime variable. This exposes a field to the user at launch time, allowing them to specify the desired number of instances. Calm then orchestrates the creation of that many identical VMs, which can be referenced using the @@{calm_array_index}@@ macro.

This is the most critical flaw. While the proposed X-Play playbook can technically clone a VM, the new VM will exist outside of the Calm application's awareness. This means it won't be part of the application's lifecycle (e.g., updates, scaling down, deletion), breaking the application-centric model. The correct approach is to have the X-Play playbook trigger the 'Scale Out' custom action on the Calm application itself. This action, defined within the blueprint, would properly increment the web tier replica count, ensuring the new VM is a managed part of the application.

After a blueprint is published, it enters a pending state in the Marketplace Manager. A Calm administrator must explicitly approve the blueprint before it becomes visible to any projects.

Approving the blueprint makes it available globally, but access is controlled on a per-project basis. The administrator must go into the Marketplace Manager, select the approved blueprint, and explicitly assign it to the production project to make it visible and usable there.

The yum command is used on CentOS to install packages from a repository. An 'Unable to find a match' error, followed by an exit code of 1, strongly indicates that the yum utility could not reach its configured repositories to find the httpd package. This is almost always due to a network issue, such as missing DNS settings, incorrect IP configuration, or firewall rules blocking access from the VM to the repository servers (either on the internet or on the corporate network).