vSAN supports Microsoft Windows Server Failover Cluster (WSFC) with which configuration?
A. File share witness quorum with Exchange Database Availability Groups, SQL Server AlwaysON Availability Groups (AAG)
B. Virtual raw device mapping (RDM) with Exchange Database Availability Groups, SQL Server AlwaysOn Availability Groups (AAG)
C. FCI witness quorum with Exchange Database Availability Groups, SQL Server AlwaysOn Availability Groups (AAG)
D. NFS mount witness quorum with Exchange Database Availability Groups, SQL Server AlwaysON Availability Groups (AAG)
Correct Answer is A, Not C
Sorry, by mistake typed C.
The Correct answer is A
File share witness quorum with Exchange Database Availability Groups, SQL Server AlwaysON Availability Groups (AAG)
C is correct as SQL FCI supported with shared disk.
A is incorrect, SQL Server AAG, Exchange DAG only support with non-shared disk.
Ref-
Native vSAN fully supports Microsoft cluster techniques with non-shared disks (i.e. SQL Server AAG, Exchange DAG).
Only the vSAN iSCSI Target Service supports Microsoft clustering with shared disks (i.e. SQL FCI).
vSAN 6.7 or higher is required.
RDMs for MSCS is not officially supported on vSAN.
Initiators can be either from virtual machines or physical servers. For guest initiators in virtual machines, those virtual machines can be residing on:
The same vSAN cluster that provides the iSCSI target service
An external vSAN or vSphere cluster.
vSAN Stretched Clusters are not supported.
https://kb.vmware.com/s/article/54461
It should be A as the FCI doesn’t support either Exchange DAG or SQL AAG.
Correct Ans is A