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-US Exam - Topic 1 Question 34 Discussion

Actual exam question for Nutanix's NCP-US exam
Question #: 34
Topic #: 1
[All NCP-US Questions]

Which scenario is causing the alert and need to be addressed to allow the entities to be protected?

Show Suggested Answer Hide Answer
Suggested Answer: B

The scenario that is causing the alert and needs to be addressed to allow the entities to be protected is that one or more VMs or Volume Groups belonging to the Consistency Group may have been deleted. A Consistency Group is a logical grouping of VMs or Volume Groups that are protected together by a Protection Policy. A Protection Policy is a set of rules that defines how often snapshots are taken, how long they are retained, and where they are replicated for disaster recovery purposes. If one or more VMs or Volume Groups belonging to the Consistency Group are deleted, the Protection Policy will fail to protect them and generate an alert with the code AI303551 -- VolumeGroupProtectionFailed.Reference:Nutanix Volumes Administration Guide, page 29; Nutanix Volumes Troubleshooting Guide


Contribute your Thoughts:

0/2000 characters
Craig
3 months ago
I didn't know state metadata could cause alerts, that's surprising!
upvoted 0 times
...
Tamekia
3 months ago
A seems like a problem too, multiple Recovery Plans can get messy.
upvoted 0 times
...
Malcom
3 months ago
Wait, are we sure about B? Deleting VMs could cause issues too.
upvoted 0 times
...
Javier
4 months ago
Definitely agree with C, that sounds right.
upvoted 0 times
...
Lettie
4 months ago
I think it's option C, the timestamps need to match.
upvoted 0 times
...
Simona
4 months ago
Option D seems off to me; I thought state metadata was usually a non-issue unless it was specifically flagged in the documentation.
upvoted 0 times
...
Kara
4 months ago
I feel like we had a practice question about deleted VMs affecting consistency groups, but I can't recall the details.
upvoted 0 times
...
Justa
4 months ago
I think option C sounds familiar; something about logical timestamps being inconsistent between clusters could definitely cause problems.
upvoted 0 times
...
Bette
5 months ago
I remember we discussed how multiple Recovery Plans with a Witness could create conflicts, but I'm not sure if that's the main issue here.
upvoted 0 times
...
Jeanice
5 months ago
I feel pretty confident about this one. The wording of the options seems straightforward, and I think I know which scenario is the correct answer.
upvoted 0 times
...
Fernanda
5 months ago
This is a good test of my understanding of the concepts. I'll make sure to double-check my work before submitting my answer.
upvoted 0 times
...
Gail
5 months ago
Okay, I think I've got a handle on this. The key is to identify which scenario is causing an alert that needs to be addressed to protect the entities. Let me go through the options one by one.
upvoted 0 times
...
Gabriele
5 months ago
This looks like a tricky question. I'll need to carefully read through the options and think about the scenarios they describe.
upvoted 0 times
...
Noel
5 months ago
Hmm, I'm a bit confused by the terminology here. I'll need to make sure I understand what a "Consistency Group" and "Witness" are before I can decide on the right answer.
upvoted 0 times
...
Lashaun
5 months ago
I'm a bit confused by the wording of the question. Does the device not support 802.1X, or is it just not configured properly? I'll need to think through those two scenarios carefully.
upvoted 0 times
...
Victor
1 year ago
I'm going with C. Anything involving timestamps and clusters makes me nervous, so I'd want to get that sorted out right away.
upvoted 0 times
Kenny
1 year ago
Ernie: Definitely, let's make sure everything is in sync.
upvoted 0 times
...
Ira
1 year ago
Should we check the clusters to see if the timestamps match up?
upvoted 0 times
...
Ernie
1 year ago
Agreed, that could cause some serious problems if not addressed.
upvoted 0 times
...
Sommer
1 year ago
I think C is the issue. Timestamps need to be consistent between clusters.
upvoted 0 times
...
...
Adolph
1 year ago
Haha, this exam is really testing our knowledge of consistency groups and recovery plans. I bet the instructor is enjoying watching us all struggle with this one!
upvoted 0 times
Elenore
1 year ago
D) One or more VMs or Volume Groups belonging to the Consistency Group contains state metadata
upvoted 0 times
...
Jean
1 year ago
C) The logical timestamp for one or more of the Volume Groups is not consistent between clusters
upvoted 0 times
...
Alfreda
1 year ago
B) One or more VMs or Volume Groups belonging to the Consistency Group may have been deleted
upvoted 0 times
...
Odette
1 year ago
A) One or more VMs or Volume Groups belonging to the Consistency Group is part of multiple Recovery Plans configured with a Witness.
upvoted 0 times
...
...
Rachael
1 year ago
I think option D is also a valid concern, state metadata in VMs can impact entity protection.
upvoted 0 times
...
Aja
1 year ago
Hmm, I'm not sure. Option D about the state metadata also seems plausible. Maybe it's a trick question and there's more than one right answer?
upvoted 0 times
...
Isabella
1 year ago
I agree with Lucy. The logical timestamp issue is the most likely scenario causing the alert based on the options provided.
upvoted 0 times
Marjory
1 year ago
C) The logical timestamp for one or more of the Volume Groups is not consistent between clusters.
upvoted 0 times
...
Lindsey
1 year ago
A) One or more VMs or Volume Groups belonging to the Consistency Group is part of multiple Recovery Plans configured with a Witness.
upvoted 0 times
...
...
Cheryl
1 year ago
I believe option C is the problem, inconsistency in logical timestamps can lead to data protection issues.
upvoted 0 times
...
Pamela
1 year ago
I agree with Felix, having multiple Recovery Plans with a Witness can cause issues.
upvoted 0 times
...
Lucy
2 years ago
Option C seems like the correct answer here. If the logical timestamp is not consistent, it could definitely cause an alert and need to be addressed.
upvoted 0 times
Lauran
1 year ago
C) The logical timestamp for one or more of the Volume Groups is not consistent between clusters
upvoted 0 times
...
Regenia
1 year ago
B) One or more VMs or Volume Groups belonging to the Consistency Group may have been deleted
upvoted 0 times
...
Moon
1 year ago
I agree, inconsistency in logical timestamps can lead to issues with data protection.
upvoted 0 times
...
Brendan
1 year ago
Option C seems like the correct answer here. If the logical timestamp is not consistent, it could definitely cause an alert and need to be addressed.
upvoted 0 times
...
Allene
1 year ago
A) One or more VMs or Volume Groups belonging to the Consistency Group is part of multiple Recovery Plans configured with a Witness.
upvoted 0 times
...
...
Felix
2 years ago
I think the scenario causing the alert is option A.
upvoted 0 times
...

Save Cancel