NCP-MCA Exam Dumps - Nutanix Certified Professional - Multicloud Automation (NCP-MCA 6.10) Exam

When troubleshooting or optimizing blueprints where complex operations (like Provisioning combined with detailed Network Configuration) frequently fail, the recommended best practice is to split the steps into smaller tasks.

In Nutanix Self-Service (Calm), theAudittab provides a sequential log of every task executed during an application's lifecycle. If provisioning and network configuration are bundled into a "single step" (e.g., a large script or a single package install), a failure makes it difficult to determine if the issue was with the VM creation, the OS boot, or the specific network parameter application.

By splitting the logic into distinct tasks (e.g., Task 1: Provision VM, Task 2: Configure Network), the administrator can:

Isolate the failure:The Audit log will clearly show "Provision VM: Success" and "Configure Network: Failed".

Validate inputs:It ensures the VM is fully available before attempting configuration.

Improve Auditing:Granular logs allow for faster root cause analysis of the "misconfigured parameters."

Retrying (Option B) or adding delays (Option D) are reactive measures that do not address the root cause of configuration errors, and disabling logging (Option C) hinders troubleshooting.

When configuringHTTP Endpointswithin Nutanix Self-Service (to be used by tasks for making API calls), the system provides security controls to ensure trust.

Verify TLS Certificate:This specific checkbox setting in the Endpoint configuration determines whether the Self-Service engine validates the SSL/TLS certificate of the target server.

Security:Checking this box ensures that the connection is secure and that the target identity is verified (preventing Man-in-the-Middle attacks). Unchecking it allows connections to servers with self-signed or invalid certificates (often used in dev/test), but forsecure access, verifying the certificate is the required configuration.

Options A (SSH) and C (Static IP) are unrelated to the security of an outbound HTTP API call. Option B (Proxy) relates to routing, not the security handshake itself.

To provide users with access to Nutanix Self-Service (formerly Calm), an administrator must configure Role-Based Access Control (RBAC) within the context of a Project.

Access to Self-Service is not global; it is defined at the Project level.1An administrator must:

Add the user (or their Active Directory group) to a Project.

Assign a Roleto that user within the project.

Project Admin:Full control over the project.2

Developer:Can create blueprints and applications.

Consumer:Can only launch blueprints available in the Marketplace.3

Operator:Can perform day-2 operations on existing applications.4

Without an assigned role in a project, a user cannot access the Self-Service portal features or view any blueprints.

To configure access to a new cloud target (such as Oracle Cloud, AWS, Azure, or GCP) within Nutanix Self-Service (formerly Calm), the administrator must define the connection in theProviderssection.

Providers (Settings):This is the foundational configuration area where connection details, API endpoints, and authentication credentials for external infrastructure are defined. Before any Project, Environment, or Blueprint can utilize a new cloud, the "Account" or "Provider" definition must be created here.

Workflow:The administrator navigates to theProviders(or "Cloud Providers") tab, selects the provider type (using a plugin or generic provider if Oracle Cloud is not natively listed in the version), and inputs the necessary region and credential information.

Differentiation:

Environments (B)are subsets of a provider assigned to a specific Project.

Marketplace (A)is for publishing applications, not configuring infrastructure connections.

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.