Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix NCP-MCI Exam - Topic 3 Question 48 Discussion

The administrator expanded a Nutanix cluster repurposed nodes from a decommissioned cluster. The administrator has validated the following:* Same number of cores, amount of memory and storage* The nodes are on the same subnet* The nodes are running the same version of AOS and AHVAfter the nodes were added the administrator discovered that VMs cannot be migrated to the recently added nodes.What would be the reason for this issue?
C) The VMs were created on new generation of CPU and must be power-cycled to renegotiate new features.
A) The nodes firmware needs to be updated using LCM before the VMs will be able to migrate.
B) An Acropolis Dynamic Scheduler (ADS) task is running and the VMs will migrate when it completes.
D) The VMs have VM-VM affinity rules and cannot migrate until affinity rules are updated.

Nutanix NCP-MCI Exam - Topic 3 Question 48 Discussion

Actual exam question for Nutanix's NCP-MCI exam
Question #: 48
Topic #: 3
[All NCP-MCI Questions]

The administrator expanded a Nutanix cluster repurposed nodes from a decommissioned cluster. The administrator has validated the following:

* Same number of cores, amount of memory and storage

* The nodes are on the same subnet

* The nodes are running the same version of AOS and AHV

After the nodes were added the administrator discovered that VMs cannot be migrated to the recently added nodes.

What would be the reason for this issue?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Sherita
3 days ago
I’m a bit confused about the ADS task. Does it really block migrations, or is that just for load balancing?
upvoted 0 times
...
Joana
8 days ago
I think I saw a practice question about VM-VM affinity rules affecting migrations. Could that be relevant?
upvoted 0 times
...
Annett
13 days ago
I remember something about firmware needing to be updated for new nodes, but I'm not sure if that's the main issue here.
upvoted 0 times
...

Save Cancel