NCP-MCI-6.10 Nutanix Certified Professional - Multicloud Infrastructure (NCP-MCI v6.10) Free Practice Exam Questions (2026 Updated)

To create a custom Intelligent Operations report and run it across multiple Prism Central instances, administrators must export the report configuration from one Prism Central instance and then import it into the others. This process leverages the .rpt file format, which encapsulates the report’s configuration details, including data sources, visualization preferences, and thresholds.

From theNutanix Enterprise Cloud Administration (ECA)course materials:

“Administrators can create custom Intelligent Operations reports in Prism Central and export the configuration as a .rpt file. This exported file can then be imported into other Prism Central instances, ensuring consistency across environments without requiring manual recreation of the report’s details.”

Additionally:

“The export/import feature for reports ensures that custom dashboards and reports can be easily migrated or replicated across multiple Prism Central instances, enabling a standardized approach to monitoring and analytics in a multicloud environment.”

This clearly indicates that the recommended and supported method for sharing or replicating custom reports across multiple Prism Central instances is by exporting and importing the report configurations in .rpt format. This approach avoids the need for manual recreation and ensures that the reports maintain their intended configuration and layout across different instances.

VM templates in Nutanix are supported only when the VM’s disks reside on storage containers configured with Replication Factor 2 (RF2) or higher.

Option C (VM has disks on RF2 containers) is correct:

VM templates requirea minimum RF2 for fault tolerance.

RF1 containers do not meet Nutanix best practices for VM templates.

Option A is incorrect:

VMs protected by Protection Domains can be cloned, but this is different from creating a VM template.

Option B is incorrect:

Agent VMs (e.g., Witness VMs) or Prism Central cannot be used as VM templates.

Option D is incorrect:

Nutanix VM templates are natively supported on AHV, not ESXi.

Protection Domains (PDs) in Nutanix ensure that entire applications and their associated data are protected during failover.However,Volume Groups (VGs) are not automatically includedunless explicitly configured.

Option A (Select "Auto protect related entities") is correct:

This setting ensures thatassociated Volume Groups, networks, and other dependencies are included in the Protection Domainautomatically.

Without enabling this, only the VM itself would be protected, leading tomissing application data upon failover.

Option B (Manually add Volume Groups to Protected Entities) is correct:

If"Auto protect related entities" is not enabled, the administrator mustmanually add Volume Groups to the Protection Domain.

This ensures that bothVMs and their attached Volume Groupsare replicated and recovered together.

Option C (Place Volume Groups in a separate Protection Domain) is incorrect:

Separating Volume Groups into a different PDdoes not guarantee they failover together with VMs.

It is best practice tokeep related VMs and Volume Groups in the same PD.

Option D (Use application-consistent snapshots) is incorrect:

Whileapplication-consistent snapshots improve data integrity, theydo not fix missing Volume Groups in failover scenarios.

By default, Nutanix Prism Central retains the last 10 instances of a report if no retention policy is configured.

Option B (10) is correct:

Nutanixstores up to 10 reports, after which older reports areautomatically deleted.

Options A (5), C (15), and D (20) are incorrect:

Whileretention policies can be customized, thedefault setting is 10 reports.

In a Nutanix cluster, Replication Factor 2 (RF2) means that each piece of data has two copies: a primary and a replica. To safely remove a node while ensuring data redundancy and cluster health, the system must have enough nodes to maintain the RF2 protection and complete the removal.

From the Nutanix Enterprise Cloud Administration (ECA) documentation:

“The minimum number of nodes required for a safe host removal in an RF2 cluster is four. This ensures that even after removing a node, there are enough remaining nodes to continue hosting the primary and replica data copies, meeting the RF2 requirement.”

The logic is:

In a 3-node RF2 cluster, there isn’t enough redundancy to safely remove a node without impacting data availability.

A 4-node RF2 cluster allows safe removal of one node while still ensuring two copies of all data remain.

Thus, the minimum number of nodes required for a safe host removal in an RF2 cluster is 4

Nutanix Life Cycle Manager (LCM) relies on validated firmware and driver bundles for hardware components. For GPU-enabled hosts, LCM documentation states:

“GPU-enabled AHV hosts require GPU driver bundles to be uploaded manually via the Direct Uploads mechanism so that LCM can validate and upgrade the necessary GPU components during workflow execution.”

GPU drivers are vendor-specific and not always available in the standard catalog, so the administrator must upload them before LCM can orchestrate the upgrade.

Running in dark site mode does not provide missing GPU bundles. Creating agent VMs is unrelated to GPU driver operations. Updating NCC improves validations but does not provide GPU support files.

Therefore, Direct Uploads of GPU driver bundles is required.

The Intelligent Operations and Analysis Dashboard in Prism Central supports generating ad-hoc reports. These reports are temporary artifacts and are not designed for long-term storage. Internal documentation states, “Generated reports are retained for 24 hours and then automatically purged by the system to prevent report accumulation and data bloat.” This automatic cleanup is part of the reporting subsystem and applies regardless of user role or storage location. The reports are not stored in Prism Element, nor are they archived automatically. Therefore, after the 24-hour retention window, the system removes them, explaining why the user could not find the previously generated report.

During cluster expansion, Nutanix uses the Controller VM discovery service, which relies on multicast-based node advertisement. The internal architecture documentation states:

“Node discovery during cluster expansion requires IPv4 multicast to be enabled and permitted on the switching infrastructure.”

This allows new nodes to announce themselves to the existing cluster through standard Nutanix discovery packets.

IPv6 multicast is not used for node discovery. Matching AOS or hypervisor versions is recommended for compatibility but not required for discovery itself. These are post-discovery compatibility concerns, not prerequisites.

Thus, IPv4 multicast is required for automatic node discovery.

BMC (Baseboard Management Controller) updates can be applied per-node in Nutanix LCM, unlike AOS or AHV, which require cluster-wide upgrades.

Option B (BMC) is correct:

BMC firmwarecontrols remote management and power cycling of individual nodes.

Updating BMCdoes not impact the entire clusterand can be done per node.

Option A (AOS) is incorrect:

AOS upgrades affect the entire clusterand require cluster-wide consistency.

Option C (NCC) is incorrect:

NCC updatesapply across all nodes simultaneously, ensuring uniformity in checks.

Option D (AHV) is incorrect:

AHV updates require coordinated upgrades across hoststo maintain VM availability.

In Nutanix Prism Central, if anadministrator is also an approverfor an approval policy, it can result in repeated prompts for approvals even after the original request is approved. This occurs because the system requires the approver (who is also the requester) to explicitly confirm actions involving protected snapshots to maintain compliance and avoid accidental deletion.

From theNutanix ECA documentation:

“When an administrator is configured as an approver in the approval policy, repeated approval requests may occur because the same user must explicitly confirm actions they initiated, such as deleting protected snapshots. This ensures administrative actions are fully deliberate.”

The Nutanix ECA course covers various methods for organizing and managing virtual machines (VMs) within a Nutanix environment, particularly in Prism Central. The question focuses on easily grouping a set of VMs, which requires a mechanism that is flexible, scalable, and straightforward to apply across multiple VMs for management, reporting, or policy application.

Extract from Nutanix Enterprise Cloud Administration (ECA) Course Documents:

Module: Prism Central Management, Section: Entity Organization"Tags provide a flexible way to group entities such as VMs in Prism Central. Tags are key-value pairs that can be assigned to VMs to categorize them for management, reporting, or policy enforcement. They are easy to apply and can be used to group VMs dynamically across clusters."

Module: VM Management, Section: Grouping VMs"To group a set of VMs for simplified management, Tags are the recommended approach. Unlike Categories, which are used for role-based access control and policy enforcement, Tags are lightweight and ideal for custom grouping without additional configuration overhead."

Explanation of Options:

A. Catalog ItemsThis is incorrect. Catalog Items in Nutanix are used within the Nutanix Calm or Marketplace to manage application blueprints or service offerings, not for grouping VMs. The ECA course states:"Catalog Items represent deployable applications or services in the Marketplace, not a mechanism for grouping existing VMs."They are unrelated to VM organization.

B. LabelsThis is incorrect. The term "Labels" is not used in Nutanix ECA documentation for grouping VMs. While Labels may be a generic term in other platforms, Nutanix uses "Tags" or "Categories" for similar purposes. The ECA materials do not reference Labels as a feature in Prism Central or Prism Element for VM grouping.

C. ProjectsThis is incorrect. Projects in Nutanix Prism Central are used to manage resources, users, and policies for a group of workloads, typically for multi-tenancy or resource allocation. While VMs can be associated with Projects, this involves additional configuration (e.g., assigning users, quotas, and policies) and is not the easiest way to group VMs. The ECA course notes:"Projects are used for resource governance and multi-tenancy, requiring additional setup compared to Tags for simple VM grouping."

D. TagsThis is the correct answer. Tags are lightweight, user-defined key-value pairs that can be applied to VMs in Prism Central to group them for management, monitoring, or reporting purposes. The ECA course emphasizes that Tags are easy to assign and manage, making them ideal for grouping VMs without the overhead of other mechanisms like Categories or Projects. Tags can be applied to multiple VMs at once and used in searches, dashboards, or scripts.

Supporting Extract:"Tags allow administrators to quickly group VMs by assigning custom key-value pairs, such as ‘Department: HR’ or ‘Environment: Production.’ They are ideal for ad-hoc grouping and can be leveraged in Prism Central for filtering and management tasks."

Additional Context from ECA:

Tags are managed in Prism Central under theEntities > Tagssection, where administrators can create, assign, and manage Tags for VMs and other entities. The ECA course highlights their simplicity:"Tags require minimal configuration and can be applied to VMs in bulk, making them the easiest method for grouping."

Unlike Categories, which are used for policy enforcement (e.g., security or placement policies), Tags are purely for organizational purposes, aligning with the question’s focus on ease of use.

Supporting Reference from Web Results:

The Nutanix Bible (https://www.nutanix.com/go/the-nutanix-bible) aligns with the ECA documentation: "Tags in Prism Central provide a simple and flexible way to organize VMs and other entities, enabling administrators to group resources for management or reporting without complex configurations."