Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix NCP-BC Exam - Topic 1 Question 11 Discussion

Posted by Arlean on Jul 20, 2026 at 10:05 PM

An administrator configures a VM-VM Anti-Affinity policy for a web application cluster to ensure high availability. The application is protected by a Protection Policy in Prism Central. A failover occurs, moving the VMs to the recovery site.

What determines whether the VM-VM Anti-Affinity rules are active on the recovery site?

Suggested Answer: B

Get Premium NCP-BC Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
12 comments · newest first
LA
Laquita 1 month ago
I lean towards D. The checkbox must be selected to enforce it.
JE
Jerry 1 month ago
I feel like B is correct. Anti-Affinity isn't supported in DR.
MI
Mi 1 month ago
I think it's C. The policy needs to exist at the recovery site.
LE
Leah 2 months ago
D) sounds right, you gotta check that box for it to work!
KR
Kristian 2 months ago
Wait, I thought Anti-Affinity was always enforced in DR?
AN
Antonio 2 months ago
C) is the way to go, you need the policy at the recovery site.
WA
Wava 2 months ago
I disagree, B) makes more sense since DR has limitations.
LO
Louisa 2 months ago
A) is correct, the rules are tied to VM metadata.
TA
Tasia 2 months ago
From what I remember, if the Anti-Affinity policy isn't replicated to the recovery site, it won't be active, so I think C is the right choice.
TA
Tanesha 3 months ago
I’m a bit confused about whether the "Enforce Anti-Affinity" checkbox plays a role in this scenario. I feel like it might be important.
LO
Louvenia 3 months ago
I think we practiced a similar question, and I recall that the Anti-Affinity policies need to be present at the recovery site to be active.
CY
Cyril 3 months ago
I remember studying that Anti-Affinity rules are tied to VM metadata, but I'm not sure if they carry over during a failover.
0/2000 characters

Save Cancel