Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix Exam NCP-MCA 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:

Glory
1 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
Barrett
2 days ago
Yeah, they should double-check the requirements before running the Playbook.
upvoted 0 times
...
Joesph
16 days ago
Maybe the admin missed a step in the manual.
upvoted 0 times
...
...
Joaquin
1 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
3 days ago
A) Nah, man, this is an AHV environment. The play should work.
upvoted 0 times
...
Oretha
8 days ago
C) Reduction of vCPU cannot be done on a VM with a running snapshot.
upvoted 0 times
...
Mabel
9 days ago
A) This play cannot be executed against a VM on AHV.
upvoted 0 times
...
...
Ardella
2 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
5 days 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
7 days ago
C) Reduction of vCPU cannot be done on a VM with a running snapshot.
upvoted 0 times
...
Rodney
22 days ago
A) This play cannot be executed against a VM on AHV.
upvoted 0 times
...
...
Melita
2 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
2 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
15 days ago
So the correct answer is actually C, not B.
upvoted 0 times
...
Emilio
16 days ago
That's a good point, the reduction of vCPU cannot be done on a VM with a running snapshot.
upvoted 0 times
...
Kenny
1 months ago
But what if the VM has a running snapshot, wouldn't that also cause the Playbook to fail?
upvoted 0 times
...
Annelle
2 months ago
I agree, the VM must be powered off first before reducing vCPU.
upvoted 0 times
...
...
Jolene
2 months ago
I believe the Playbook failed because it cannot be executed against a VM on AHV.
upvoted 0 times
...
Leota
2 months ago
I agree with Abel. The error could be due to the VM not being powered off.
upvoted 0 times
...
Abel
2 months ago
I think the Playbook failed because the VM needs to be powered off before reducing vCPU.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77