Application owners require support of a Microsoft Windows Server Failover Cluster (WSFC).
Their current environment consists of the following components:
✑ vSphere 7.0 and vSAN 7.0
✑ External array supporting NFS 3.0/4.1, Server Message Block (SMB) 2.1
✑ 10 GbE storage connectivity for all devices
The solution architect is tasked with coming up with a solution to meet this requirement while utilizing their existing investments.
Which two recommendations could the architect make? (Choose two.)
AD
Reference:
https://kb.vmware.com/s/article/79616
A,C https://kb.vmware.com/s/article/79616 NO SMB supported No vSAN iSCSI Target No NFS4
This answer is VERY wrong. The KB refers to the general supportability of WSFC in VMware environments, which includes the possibility to configure it by using RDMs. However, the question states clearly that no FC Storage is available, therefore no RDM can ever be used. In other words, C is so wrong. vSAN, on the other hand, has supportability for WSFC both by sharing vmdk natively or by using iSCSI service. Right answer is A, E.
there is no RDM in the VSAN nor the Externals storage array (It support sonly NFS /SMB)
Answer is A,E https://kb.vmware.com/s/article/54461
Windows Server Failover Clusters (WSFC) using the vSAN iSCSI target service, fully transparent failover of LUNs is now possible with the iSCSI service for vSAN when used in conjunction with WSFC. This feature is incredibly powerful as it can protect against scenarios in which the host that is serving a LUN’s I/O fails. This failure might occur for any reason: power, hardware failure or link loss. In these scenarios, the I/O path will now transparently failover to another host with no impact to the application running in the WFSC
A >> vSAN native fully supports Microsoft cluster techniques with shared disks on 6.7 U3 or higher version https://kb.vmware.com/s/article/54461 B >> NFS does not support RDM, or clustered disks C >> Neither vSAN, NFS or SMB support RDM. D >> SMB 2.1 is not supported for sharing disks. WSFC can use only SMB 3.0 file shared, or attached shared storage https://learn.microsoft.com/en-us/windows-server/failover-clustering/clustering-requirements E >> You cannot have a RDM for WSFC, but you can use the vSAN iSCSI Target Service to provide an iSCSI volume to the virtual machin guest OS : https://kb.vmware.com/s/article/54461
answers are A and E confirmed with KB https://kb.vmware.com/s/article/54461
The answer is AE
https://kb.vmware.com/s/article/79616 vSAN (vSphere 7.0) Clustered VMDKs vSAN VMware fully supports a configuration of WSFC using in-guest iSCSI initiators or in-guest SMB (Server Message Block) protocol, provided that all other configuration meets the documented and supported WSFC configuration. Using this configuration in VMware virtual machines is similar to using it in physical environments.
A, C Only these two answers make sense. Storage protocols: -> FC, FCoE and Native iSCSI are fully supported with pRDMs and vVols. -> Clustered VMDKs are supported with FC only. -> NFS is not a supported storage protocol to access a clustered disk resource for WSFC. NFS backend VMDKs can be used as non-shared disks (system disk, backup, etc.) without limitations. -> vSAN supports natively clustered VMDK in vSphere 7.x -> Virtual Volumes – supported. Check with your storage vendor if the implementation of vVol includes support for WSFC on VMware vSphere. https://kb.vmware.com/s/article/79616
Nether vSAN or NFS supports RDM disks. On vSAN not even on the iSCSI service. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-E9984893-DF64-49EC-B0DB-44F8C271BCFE.html
agreed with Major88. Only Clustered VMDKs, vVols and RDMs allowed for Microsoft Windows Server Failover Cluster (WSFC) - https://kb.vmware.com/s/article/79616