MENU
Which scenario is causing the alert and need to be addressed to allow the entities to be protected?
Suggested Answer: B
Get Premium NCP-US Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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
39 comments · newest first
CR
Craig
10 months ago
I didn't know state metadata could cause alerts, that's surprising!
TA
Tamekia
11 months ago
A seems like a problem too, multiple Recovery Plans can get messy.
MA
Malcom
11 months ago
Wait, are we sure about B? Deleting VMs could cause issues too.
JA
Javier
11 months ago
Definitely agree with C, that sounds right.
LE
Lettie
11 months ago
I think it's option C, the timestamps need to match.
SI
Simona
11 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.
KA
Kara
12 months ago
I feel like we had a practice question about deleted VMs affecting consistency groups, but I can't recall the details.
JU
Justa
12 months ago
I think option C sounds familiar; something about logical timestamps being inconsistent between clusters could definitely cause problems.
BE
Bette
1 year 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.
JE
Jeanice
1 year 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.
FE
Fernanda
1 year 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.
GA
Gail
1 year 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.
GA
Gabriele
1 year ago
This looks like a tricky question. I'll need to carefully read through the options and think about the scenarios they describe.
NO
Noel
1 year 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.
LA
Lashaun
1 year 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.
VI
Victor
2 years 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.
KE
Kenny
2 years ago
Ernie: Definitely, let's make sure everything is in sync.
IR
Ira
2 years ago
Should we check the clusters to see if the timestamps match up?
ER
Ernie
2 years ago
Agreed, that could cause some serious problems if not addressed.
SO
Sommer
2 years ago
I think C is the issue. Timestamps need to be consistent between clusters.
AD
Adolph
2 years 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!
EL
Elenore
2 years ago
D) One or more VMs or Volume Groups belonging to the Consistency Group contains state metadata
JE
Jean
2 years ago
C) The logical timestamp for one or more of the Volume Groups is not consistent between clusters
AL
Alfreda
2 years ago
B) One or more VMs or Volume Groups belonging to the Consistency Group may have been deleted
OD
Odette
2 years ago
A) One or more VMs or Volume Groups belonging to the Consistency Group is part of multiple Recovery Plans configured with a Witness.
RA
Rachael
2 years ago
I think option D is also a valid concern, state metadata in VMs can impact entity protection.
AJ
Aja
2 years 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?
IS
Isabella
2 years ago
I agree with Lucy. The logical timestamp issue is the most likely scenario causing the alert based on the options provided.
MA
Marjory
2 years ago
C) The logical timestamp for one or more of the Volume Groups is not consistent between clusters.
LI
Lindsey
2 years ago
A) One or more VMs or Volume Groups belonging to the Consistency Group is part of multiple Recovery Plans configured with a Witness.
CH
Cheryl
2 years ago
I believe option C is the problem, inconsistency in logical timestamps can lead to data protection issues.
PA
Pamela
2 years ago
I agree with Felix, having multiple Recovery Plans with a Witness can cause issues.
LU
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.
LA
Lauran
2 years ago
C) The logical timestamp for one or more of the Volume Groups is not consistent between clusters
RE
Regenia
2 years ago
B) One or more VMs or Volume Groups belonging to the Consistency Group may have been deleted
MO
Moon
2 years ago
I agree, inconsistency in logical timestamps can lead to issues with data protection.
BR
Brendan
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.
AL
Allene
2 years ago
A) One or more VMs or Volume Groups belonging to the Consistency Group is part of multiple Recovery Plans configured with a Witness.
FE
Felix
2 years ago
I think the scenario causing the alert is option A.