MENU
An administrator has configured AHV Metro Availability with Witness and is testing failover scenarios.
During testing, the administrator disconnects the primary and recovery clusters but Prism Central remains connected to the recovery site.
What are two expected system behaviors? (Choose two.)
Suggested Answer: A, C
Get Premium NCP-MCI-6.10 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
When connectivity between Metro clusters is lost, Nutanix Metro Availability ensures data integrity using Witness for automatic failover.
Option A (Guest VM I/O operations pause until connectivity is restored) is correct:
Metro Availability enforces data consistency, so I/O operations pause until failover is confirmed.
Option C (Guest VMs failover automatically to the recovery cluster) is correct:
The Witness VM detects the failure and initiates an automatic failover to the secondary cluster.
Option B is incorrect:
Prism Central does not control VM failover in Metro Availability.
Option D is incorrect:
The primary cluster is unreachable, so VMs cannot continue running there.
Nutanix Metro Availability Guide How Witness Handles Failover Scenarios
Nutanix KB I/O Freezing and Failover Behavior in Metro Clusters
37 comments · newest first
DE
Desiree
10 months ago
Totally agree with A, but C is a bit iffy for me.
KA
Karma
10 months ago
D seems wrong, they should failover if disconnected.
DE
Denise
10 months ago
Wait, how can VMs keep running if both clusters are down?
PE
Percy
10 months ago
I think B is misleading, connectivity to the primary site doesn't matter here.
ST
Stacey
11 months ago
A and C are correct!
SO
Soledad
11 months ago
I practiced a similar question, and I think the I/O operations would pause until the primary site is back online, but I’m not completely confident.
LI
Lina
11 months ago
I feel like the guest VMs would continue running on the primary cluster since Prism Central is still connected to the recovery site.
TI
Tina
11 months ago
I think the VMs might failover automatically to the recovery cluster, but I need to double-check how the witness setup affects that.
LA
Lajuana
11 months ago
I remember something about I/O operations freezing when there's a disconnect, but I'm not sure if it's just for the primary site or both.
GL
Glory
12 months ago
This is a tricky one. I'll need to think through the different options carefully and make sure I understand the expected system behaviors in this specific scenario. The wording of the question is important, so I'll read it a few times to make sure I don't miss anything.
HU
Huey
12 months ago
I think the key here is that the primary and recovery clusters are disconnected, but Prism Central is still connected to the recovery site. That should mean the guest VMs don't fail over, but their I/O operations might pause until connectivity is restored.
AN
Angella
1 year ago
Okay, let's see. If Prism Central is still connected to the recovery site, I'm guessing the guest VMs won't automatically fail over. But I'm not sure if the I/O operations will pause or if the VMs will continue running on the primary cluster.
CA
Cathrine
1 year ago
Hmm, this question seems to be testing our understanding of AHV Metro Availability with Witness. I'll need to carefully consider the different scenarios and system behaviors.
LO
Lou
2 years ago
I'm with Melda on this one. B and C make the most sense to me. Unless the admin has a teleportation device, I don't see how the VMs can keep running on the primary cluster.
RI
Rima
1 year ago
Yeah, it makes sense for the VMs to failover to the recovery cluster in this scenario.
KR
Kristeen
1 year ago
I agree, it seems like the most logical outcome.
AR
Artie
1 year ago
C) Guest VMs failover automatically to the recovery cluster.
HO
Hortencia
1 year ago
B) Guest VM I/O operations pause (freeze) until connectivity between Prism Central and the primary site is restored.
GE
Gearldine
1 year ago
So, it's safe to say that guest VM I/O operations would pause until connectivity is restored and the VMs would automatically failover to the recovery cluster.
NI
Nina
1 year ago
Exactly, it wouldn't make sense for the VMs to keep running on the primary cluster if there is no connectivity.
CR
Craig
1 year ago
Yeah, if the primary and recovery clusters are disconnected, it makes sense for the VMs to failover to the recovery cluster.
CH
Chantell
1 year ago
User B
RO
Rosann
1 year ago
User A
SH
Sheldon
1 year ago
I agree with you, B and C seem like the most logical options.
EL
Elfrieda
2 years ago
I believe option D is incorrect. VMs should not continue to run on the primary cluster if connectivity is lost.
JO
Jonell
2 years ago
I'm not sure about option C. I think VMs might not failover automatically unless configured to do so.
ME
Melda
2 years ago
Ha! Guess the admin forgot to bring their magic wand to restore connectivity. Jokes aside, I'd go with B and C.
TR
Truman
2 years ago
I agree with Alesia. Option B also makes sense because Prism Central needs to communicate with the primary site for VM operations.
ED
Edna
2 years ago
I'm not sure about D, since the question says the primary and recovery clusters are disconnected. I think A and C are the right answers.
VI
Vivienne
1 year ago
That makes sense. So D is not correct in this scenario.
SE
Sena
1 year ago
Yes, I agree. Guest VM I/O operations will pause and VMs will failover to the recovery cluster.
GL
Glory
1 year ago
I think A and C are the right answers.
AL
Alesia
2 years ago
I think option A is correct because VM I/O operations should pause when connectivity is lost.
FI
Fidelia
2 years ago
C and D seem like the correct answers. The VMs should fail over automatically to the recovery cluster, but they should also continue running on the primary cluster until connectivity is restored.
KR
Kristel
2 years ago
That makes sense. The VMs should switch over to the recovery cluster, but it's good that they keep running on the primary cluster too.
ME
Merlyn
2 years ago
D) Guest VMs continue to run on the primary cluster.
PA
Paris
2 years ago
C) Guest VMs failover automatically to the recovery cluster.