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 12 Question 54 Discussion

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

An administrator wants to be alerted when production VMs become idle. The VMs will be determined to be idle when CPU usage is lower than 5% for more than 5 minutes. All affected VMs are categorized as Environment:Production, since they have Flow microsegmentation rules.

What should the administrator do to satisfy this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: D

To view the last two actions taken by a single VM blueprint, the administrator should go to theHistory Tab. This tab shows the history of all the actions performed on the blueprint, such as launch, update, delete, etc. The administrator can filter the history by date, action, status, and user. The history tab also provides details of each action, such as the start time, end time, duration, and logs.

The other three options are not correct because:

The AMIS tab shows the list of Amazon Machine Images (AMIs) that are available for the blueprint. The administrator can use this tab to select an AMI for the blueprint or create a custom AMI.

The service tab shows the list of services that are part of the blueprint. The administrator can use this tab to add, edit, or delete services, as well as configure the dependencies, tasks, and variables for each service.

The Metrics tab shows the performance metrics of the blueprint, such as CPU, memory, disk, and network usage. The administrator can use this tab to monitor the health and performance of the blueprint and its services.Reference:

Nutanix Certified Professional - Multicloud Automation (NCP-MCA) 6.5 Exam, page 18

Nutanix Calm User Guide, section ''Blueprint History''


Contribute your Thoughts:

0/2000 characters
Marcelle
3 months ago
Wait, are we sure 5% CPU is really idle? Seems low to me.
upvoted 0 times
...
Lai
3 months ago
Totally agree with D, simple and effective!
upvoted 0 times
...
Sue
3 months ago
Why would you reduce a CPU? That sounds risky!
upvoted 0 times
...
Lindsey
4 months ago
I think B is better, taking a snapshot could be useful.
upvoted 0 times
...
Dianne
4 months ago
Option D seems right, targeting the correct category is key.
upvoted 0 times
...
Nieves
4 months ago
I feel like option A could lead to too many alerts. We need to focus on production VMs specifically, right?
upvoted 0 times
...
Laura
4 months ago
I think option B is tempting because of the snapshot action, but it might not be necessary just for idle VMs.
upvoted 0 times
...
Stephaine
4 months ago
I'm not entirely sure, but I feel like creating an alert for all VMs might not be efficient. Wasn't there a practice question about filtering alerts by category?
upvoted 0 times
...
Ming
5 months ago
I remember we discussed the importance of targeting the correct VM category for alerts, so I think option D makes sense.
upvoted 0 times
...
Irving
5 months ago
Option A seems a bit overkill to me. Creating an alert for all VMs and then using a Playbook to send an email seems like it might generate a lot of unnecessary alerts. I'd stick to just the VMs in the correct category.
upvoted 0 times
...
Mayra
5 months ago
Hmm, I'm a bit confused. Do we need to do anything with the CPU usage threshold or is that just part of the requirement? I'm not sure if I should include that in the alert or the Playbook.
upvoted 0 times
...
Helene
5 months ago
This seems pretty straightforward. I'd go with option D - create an alert for the VMs in the correct category and use a Playbook to send an email when the alert is triggered.
upvoted 0 times
...
Louvenia
5 months ago
I think option B is the way to go. We should create an alert for the VMs in the correct category, and then use a Playbook to take a snapshot in addition to sending an email. That way we have a record of when the VMs became idle.
upvoted 0 times
...
Trinidad
5 months ago
Hmm, this is a tricky one. I'll need to think carefully about the key characteristics of a self-managing Scrum Team.
upvoted 0 times
...
Valentine
5 months ago
Ah, this is a tricky one. I'm torn between A and D - both seem plausible. I think I'll go with A, since that's the more general answer about recognizing issues, but I'm not 100% sure.
upvoted 0 times
...
Nan
5 months ago
This seems like a straightforward question about the benefits of cloud computing for startups. I'll focus on the key factors like cost savings and agility.
upvoted 0 times
...
Darnell
9 months ago
Option D is the clear winner here. Anything involving 'reducing CPU' on an idle VM is like trying to lose weight by cutting off your own limbs. Gotta keep it simple, folks!
upvoted 0 times
...
Merrilee
9 months ago
I'm a bit curious about the 'Flow microsegmentation rules' mentioned in the question. Sounds like someone's been watching too much 'Tron' during their lunch breaks.
upvoted 0 times
Lorenza
8 months ago
D) Create an alert for VMs in the correct category, create a Playbook with this alert as the trigger and send an email as the action.
upvoted 0 times
...
Veda
8 months ago
A) Create an alert for all VMs, create a Playbook with this alert as the trigger and send an email as the action.
upvoted 0 times
...
Meaghan
8 months ago
B) Create an alert for VMs in the correct category, create a Playbook with this alert as the trigger > take a snapshot > send an email as the action.
upvoted 0 times
...
Daron
8 months ago
A) Create an alert for all VMs, create a Playbook with this alert as the trigger and send an email as the action.
upvoted 0 times
...
...
Enola
10 months ago
Option C is a bit bizarre. Reducing CPU on an idle VM? That's like trying to put out a fire with gasoline. Definitely D is the correct answer here.
upvoted 0 times
Carin
9 months ago
Option D makes the most sense. It's important to set up the alert for the correct category of VMs.
upvoted 0 times
...
Susana
9 months ago
Yeah, reducing CPU on an idle VM is counterintuitive. D is the logical choice.
upvoted 0 times
...
Delsie
9 months ago
I agree, option C doesn't make sense. D is definitely the way to go.
upvoted 0 times
...
...
Melda
10 months ago
Option B sounds tempting, but taking a snapshot might be overkill for this use case. I think D is the way to go - simple and effective.
upvoted 0 times
Evan
8 months ago
I think D is the best option too. It's important to keep it simple for this alert requirement.
upvoted 0 times
...
Mirta
8 months ago
Yeah, taking a snapshot might be unnecessary for monitoring idle VMs. Option D is straightforward.
upvoted 0 times
...
Mammie
9 months ago
I agree, option D seems like the most efficient choice for this scenario.
upvoted 0 times
...
...
Shawnda
10 months ago
Hmm, I'd go with option D. It's the most straightforward way to meet the requirements, and I don't see any need for additional actions like taking a snapshot or reducing CPU.
upvoted 0 times
Maryann
9 months ago
User 3: Yeah, no need for extra steps when option D covers all the requirements.
upvoted 0 times
...
Goldie
9 months ago
User 2: Agreed, it seems like the most direct way to handle the situation.
upvoted 0 times
...
Polly
9 months ago
User 1: I think option D is the best choice here.
upvoted 0 times
...
...
Josphine
10 months ago
I'm not sure, but I think option A could also work. Creating an alert for all VMs and sending an email as the action seems like a good approach.
upvoted 0 times
...
Brittni
11 months ago
I disagree, I believe the answer is D. We should create an alert for VMs in the correct category and send an email as the action.
upvoted 0 times
...
Larue
11 months ago
I think the answer is B. We need to create an alert for VMs in the correct category and take a snapshot when they become idle.
upvoted 0 times
...

Save Cancel