2V0-622 · Question #60
Which two statements are true regarding Virtual SAN Fault Domains? (Choose two.)
The correct answer is A. They enable Virtual SAN to tolerate the failure of an entire physical rack. B. Virtual SAN ensures that no two replicas are provisioned on the same domain. vSAN Fault Domains protect against rack-level failures by ensuring that no two replicas of the same object are placed within the same fault domain.
Question
Which two statements are true regarding Virtual SAN Fault Domains? (Choose two.)
Options
- AThey enable Virtual SAN to tolerate the failure of an entire physical rack.
- BVirtual SAN ensures that no two replicas are provisioned on the same domain.
- CVirtual SAN ensures that all replicas are provisioned on the same domain.
- DThey require VMware High Availability (HA) to ensure component distribution across domains.
How the community answered
(28 responses)- A75% (21)
- C18% (5)
- D7% (2)
Why each option
vSAN Fault Domains protect against rack-level failures by ensuring that no two replicas of the same object are placed within the same fault domain.
Fault Domains allow an administrator to group hosts that share physical failure points (such as a rack, power circuit, or ToR switch) so vSAN treats the entire group as a single failure unit, enabling tolerance of a complete rack failure.
vSAN's placement engine enforces that replica copies and witness components of each object are distributed across distinct fault domains, guaranteeing data availability even if one entire domain fails.
Placing all replicas on the same domain would defeat the purpose of fault domains - vSAN actively prevents co-location of replicas within a single domain to ensure redundancy.
Fault Domain component distribution is handled natively by the vSAN storage policy engine and does not depend on VMware HA; HA addresses VM restart on host failure, not storage replica placement.
Concept tested: vSAN Fault Domains rack-level failure tolerance
Source: https://docs.vmware.com/en/VMware-vSAN/7.0/com.vmware.vsان.planning.doc/GUID-FE7DBC44-E2C4-4B4B-8B8E-3E6F1C2C2A8F.html
Topics
Community Discussion
No community discussion yet for this question.