Pass the Nutanix NCM-MCI NCP-MCI-6.10 Questions and answers with ExamsMirror

TheBully VMs Listview in Prism Central’sIntelligent Operationsidentifies VMs that are consumingexcessive resources(CPU, memory, or storage IO) and causing resource starvation for other VMs.

From theNutanix ECA documentation:

“Bully VMs List identifies virtual machines with high resource consumption, enabling administrators to investigate and take action to prevent performance degradation in other VMs.”

The other options:

A (Constrained VMs): Shows VMs that are being starved of resources.

C (Inactive VMs): Shows VMs that are using little to no resources.

D (Overprovisioned VMs): Shows VMs with allocated resources beyond actual usage.

In a scale-out Prism Central deployment, using an FQDN (Fully Qualified Domain Name) enables load balancing across multiple Prism Central instances.

Option A (Load balancing) is correct:

When anFQDN is used, Nutanixautomatically distributes trafficbetween multiple Prism Central nodes, improving performance.

Option B (Resiliency) is incorrect:

Resiliency is achieved throughcluster redundancy, not by using an FQDN.

Option C (Segmentation) is incorrect:

Segmentationrelates to network isolationrather than FQDN-based load balancing.

Option D (SSL Certificate) is incorrect:

SSL certificatescan be applied to both FQDN and Virtual IP configurations.

LCM (Life Cycle Manager) fetches software updates from Nutanix’s repositories, requiring access to specific URLs.

Option A (download.nutanix.com) is correct:

This domainhosts all software update filesfor AOS, AHV, and other Nutanix components.

Option C (release-api.nutanix.com) is correct:

This domain is used forLCM to fetch update metadataand check for new versions.

Option B (mynutanix.com) is incorrect:

This domain is used foraccount management, not LCM updates.

Option D (portal.nutanix.com) is incorrect:

TheNutanix support portal is not used for automated LCM updates.

Multicast traffic can generate unnecessary overhead if it is not properly managed.IGMP Snooping (Option C)ensures thatmulticast packets are only sent to VMs that have requested them, rather than broadcasting to all VMs.

Option C (IGMP Snooping) is correct:

Itreduces unnecessary multicast trafficby ensuring that only subscribed VMs receive the packets.

It is supportednatively in AHV networking.

Option A (LACP) is incorrect:

Link Aggregation Control Protocol (LACP)improves bandwidth and redundancy but doesnot control multicast traffic.

Option B (UDP) is incorrect:

UDP (User Datagram Protocol) is a transport protocol, not a network optimization feature.

Option D (Network Segmentation) is incorrect:

Segmentation (VLANs, VPCs) isolates networksbut does not optimizemulticast traffic specifically.

The Nutanix ECA course covers migration options for VMs in multi-cluster environments, particularly when minimizing downtime is critical, such as during scheduled maintenance. The scenario involves two identical clusters with guest VMs using pass-through GPUs, managed by separate Prism Central instances, requiring a migration method that ensures minimal disruption.

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

Module: VM Management, Section: Cross-Cluster Live Migration"Cross-Cluster Live Migration allows administrators to migrate VMs between clusters managed by different Prism Central instances with minimal downtime. This feature supports live migration of VMs with pass-through GPUs, ensuring continuous operation during maintenance activities."

Module: Cluster Management, Section: Migration Strategies"For scenarios requiring minimal downtime, such as planned maintenance, Cross-Cluster Live Migration is the preferred method. It enables seamless VM migration across clusters, even those managed by separate Prism Central instances, while maintaining VM availability."

Explanation of Options:

A. Run a Recovery Plan planned failoverThis is incorrect. A Recovery Plan planned failover is part of Nutanix’s disaster recovery (DR) solution, used to execute failover for Protection Domains in scenarios like site failure. It is not designed for routine maintenance migrations and may involve downtime, especially for VMs with pass-through GPUs, as failover requires VM restart on the target cluster. The ECA course states:"Recovery Plans are used for DR failover, not for live migrations during maintenance, and may result in downtime."

B. Use Cross-Cluster Live MigrationThis is the correct answer. Cross-Cluster Live Migration, introduced in later AOS versions, allows VMs to be migrated between clusters, even those managed by different Prism Central instances, with minimal downtime. The ECA course confirms that this feature supports VMs with pass-through GPUs, as the migration process preserves VM state and connectivity. This method is ideal for planned maintenance, ensuring VMs remain operational.

Supporting Extract:"Cross-Cluster Live Migration minimizes downtime by transferring VM state and data live, supporting complex configurations like pass-through GPUs, making it suitable for maintenance scenarios."

C. Perform a Nutanix Move migration planThis is incorrect. Nutanix Move is a tool for migrating VMs from non-Nutanix environments (e.g., VMware or Hyper-V) to a Nutanix cluster, not for migrations between Nutanix clusters. It is not optimized for live migrations within a Nutanix environment and may involve downtime. The ECA course notes:"Nutanix Move is designed for external-to-Nutanix migrations, not for intra-Nutanix cluster migrations, and is not suitable for minimizing downtime."

D. Migrate Asynchronous Protection DomainsThis is incorrect. Migrating Asynchronous Protection Domains involves replicating snapshots to a remote cluster for DR purposes, not live VM migration. This process is asynchronous, involves downtime during failover, and is not suitable for maintenance scenarios requiring minimal disruption. The ECA course clarifies:"Asynchronous Protection Domains are used for DR replication, not for live VM migration, and require VM restart during failover."

Additional Context from ECA:

Cross-Cluster Live Migration: This feature leverages Nutanix’s hypervisor-agnostic migration capabilities, ensuring that VMs with pass-through GPUs are migrated seamlessly. The process involves copying VM memory and state while keeping the VM running, minimizing downtime to seconds or less.

Maintenance Scenario: For scheduled maintenance, Cross-Cluster Live Migration ensures that VMs remain available, which is critical for GPU-intensive workloads that cannot tolerate extended downtime.

Supporting Reference from Web Results:

The Nutanix Support Portal (https://portal.nutanix.com) aligns with the ECA documentation: "Cross-Cluster Live Migration supports live VM migration between clusters, including those with pass-through GPUs, ensuring minimal downtime for maintenance tasks."

Storage Policies in Nutanix allow administrators to configuredata protection and performance settingsat thestorage container level.

Replication Factor (RF)definesthe number of copies of datastored across nodes for fault tolerance.

Encryptionensures thatdata at rest is protectedvia Nutanix-native encryption methods.

Option A (Storage Containers and Volume Groups)refers tostorage organization, not policies.

Option C (Shares and Object Stores)applies tofile and object storage services, not VM storage policies.

Option D (Data Protection and Security)is a broad term but does not definespecific policy attributes.

Enabling "Cluster Lockdown" in Nutanix is the best security measure to prevent password-based SSH logins.

Option C (Enable Cluster Lockdown) is correct:

Cluster Lockdowndisables password-based SSHandrequires key-based authentication.

Option A (Rename the nutanix user) is incorrect:

The Nutanix useris a system accountand cannot be renamed.

Option B (Block port 22) is incorrect:

This wouldprevent all SSH connections, includingkey-based logins, making administration difficult.

Option D (Delete the nutanix user) is incorrect:

Thenutanix useris required for system operations and cannot be removed.

Windows Defender Credential Guard requires UEFI firmware and Secure Boot to function properly.

Option B (Enable UEFI with Secure Boot) is correct:

Credential Guardrequires a UEFI-based boot moderather thanLegacy BIOS.

Secure Boot ensures only trusted OS components load, reducing attack surface for credential theft.

Option A (Update vCPU to 8) is incorrect:

Increasing vCPUs does not impactCredential Guard compatibility.

Option C (Use Windows Server 2022) is incorrect:

Windows Server 2019supports Credential Guard; upgrading to 2022 isnot required.

Option D (Update Memory to 16GB) is incorrect:

Credential Guard has no minimum RAM requirementbeyond general OS needs.

For NutanixDisaster Recovery (DR) protection policies, thefirst stepis to establish a connection between theProduction cluster and the DR site, which is done by creating anAvailability Zone (AZ) (Option B).

Availability Zones (AZs) define remote sites for replicationand are a requirement for configuring protection domains and disaster recovery plans.

Option A (Installing NGT)is not necessary for setting up replication but is useful for application-consistent snapshots.

Option C (Converting the source cluster to AHV)is not required, as Nutanix supports cross-hypervisor DR betweenESXi and AHV.

Option D (Creating a point-in-time snapshot)is a later step after setting up theAvailability Zone and Protection Policy.