New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix NCP-MCA Exam - Topic 5 Question 72 Discussion

Actual exam question for Nutanix's NCP-MCA exam
Question #: 72
Topic #: 5
[All NCP-MCA Questions]

Refer to the exhibit.

An administrator created the Playbook shown in the exhibit to allow for manual reduction of vCPU count on any selected VM within their environment. During a test run of the play on one of the VMs running in development, the administrator ran into an error that the Playbook cannot be completed against the selected VM.

Here are the details of the affected VM:

VM Name: VM2

vCPU: 4

RAM: 8 GB

OS: Windows 2016

Hypervisor: AHV

What caused this Playbook to fail?

Show Suggested Answer Hide Answer
Suggested Answer: A

A Category in Nutanix is a grouping of entities (such as VMs, hosts, clusters, etc.) into a key-value pair. Categories are used to organize and manage resources more effectively by tagging them with meaningful identifiers.


Nutanix documentation on Categories.

Nutanix Best Practices for Using Categories.

Contribute your Thoughts:

0/2000 characters
Georgiann
3 months ago
Seems odd, but could it really go below the minimum vCPU?
upvoted 0 times
...
Darrin
3 months ago
Wait, can you really not change vCPU with a snapshot running?
upvoted 0 times
...
Beatriz
3 months ago
Definitely not AHV related, that's a common misconception.
upvoted 0 times
...
Refugia
4 months ago
I think it's because of the running snapshot issue.
upvoted 0 times
...
Yoko
4 months ago
The VM needs to be powered off before vCPU can be reduced.
upvoted 0 times
...
Jillian
4 months ago
I recall that reducing vCPU could cause issues if it goes below a certain threshold. Is there a minimum requirement for this VM?
upvoted 0 times
...
Judy
4 months ago
I'm not entirely sure, but I feel like AHV might have specific limitations on vCPU adjustments. Maybe that's why it's failing?
upvoted 0 times
...
Samira
4 months ago
I think I saw a similar question where it mentioned something about snapshots affecting vCPU changes. Is that relevant in this case?
upvoted 0 times
...
Wayne
5 months ago
I remember something about needing to power off the VM before making changes to the vCPU count. Could that be the issue here?
upvoted 0 times
...
Rodolfo
5 months ago
I'm a bit confused here. The details about the VM seem pretty straightforward, but I'm not sure which option best explains the failure. I'll need to think this through a bit more carefully.
upvoted 0 times
...
Mattie
5 months ago
The question also doesn't say anything about the VM having a running snapshot, so I don't think option C is correct either. I'm leaning towards option D, since the play might be trying to reduce the vCPU below the minimum.
upvoted 0 times
...
Rory
5 months ago
Hmm, I'm not sure about this one. The question doesn't mention anything about the VM needing to be powered off, so I don't think option B is the right answer.
upvoted 0 times
...
Nakita
5 months ago
I'm pretty sure this has to do with the hypervisor. The question mentions the VM is running on AHV, so option A seems like the most likely cause of the failure.
upvoted 0 times
...
Glory
10 months ago
I dunno, this whole thing sounds like a case of 'user error' to me. Maybe the admin needs to take a step back and read the manual a little more carefully. Or, you know, just ask Alexa for help. She's always down to troubleshoot some server shenanigans.
upvoted 0 times
Carin
8 months ago
Alexa could probably figure this out in no time.
upvoted 0 times
...
Barrett
8 months ago
Yeah, they should double-check the requirements before running the Playbook.
upvoted 0 times
...
Joesph
9 months ago
Maybe the admin missed a step in the manual.
upvoted 0 times
...
...
Joaquin
10 months ago
A, huh? Nah, man, this is an AHV environment. Surely the play should work, right? Unless... the admin forgot to pay their hypervisor subscription. Gotta keep those licenses up to date, folks!
upvoted 0 times
Mike
8 months ago
A) Nah, man, this is an AHV environment. The play should work.
upvoted 0 times
...
Oretha
9 months ago
C) Reduction of vCPU cannot be done on a VM with a running snapshot.
upvoted 0 times
...
Mabel
9 months ago
A) This play cannot be executed against a VM on AHV.
upvoted 0 times
...
...
Ardella
10 months ago
D? Really? Reducing vCPU below the minimum? That's like trying to take the engine out of a car while it's still running. Not gonna end well.
upvoted 0 times
Tyra
8 months ago
Yeah, trying to reduce vCPU below the minimum is definitely risky. It's like messing with the core functionality of the VM.
upvoted 0 times
...
Shelton
9 months ago
C) Reduction of vCPU cannot be done on a VM with a running snapshot.
upvoted 0 times
...
Rodney
9 months ago
A) This play cannot be executed against a VM on AHV.
upvoted 0 times
...
...
Melita
10 months ago
Hold up, are we sure it's not C? I mean, a snapshot could definitely throw a wrench in the works here. Gotta make sure that VM is clean before trying to mess with the hardware.
upvoted 0 times
...
Sheridan
10 months ago
Hmm, I think the correct answer is B. The documentation clearly states that the VM needs to be powered off before reducing vCPU. Trying to do it on a running VM is a big no-no.
upvoted 0 times
Thea
9 months ago
So the correct answer is actually C, not B.
upvoted 0 times
...
Emilio
9 months ago
That's a good point, the reduction of vCPU cannot be done on a VM with a running snapshot.
upvoted 0 times
...
Kenny
10 months ago
But what if the VM has a running snapshot, wouldn't that also cause the Playbook to fail?
upvoted 0 times
...
Annelle
10 months ago
I agree, the VM must be powered off first before reducing vCPU.
upvoted 0 times
...
...
Jolene
10 months ago
I believe the Playbook failed because it cannot be executed against a VM on AHV.
upvoted 0 times
...
Leota
11 months ago
I agree with Abel. The error could be due to the VM not being powered off.
upvoted 0 times
...
Abel
11 months ago
I think the Playbook failed because the VM needs to be powered off before reducing vCPU.
upvoted 0 times
...

Save Cancel