Explanation
Snapshots are not supported for Physical RDMsSnapshots are supported for virtual RDMs, but not if they're configured in a cluster with shared disk. I'll assume the WSFC referred to in option A is indeed using shared disk.The article referenced by David states that SQL AGs are supported and they're not using shared disk.
A) Not Supported (https://kb.vmware.com/s/article/2147661)B) Not supported (https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-F5264795-11DA-424 Not supported (https://kb.vmware.com/s/article/2147661)D) Supported (Haven't find anything saying that it's supported/unsupported. No shared storage involved, and it's documented also here:
https://storagehub.vmware.com/t/vmware-vsan/microsoft-sql-server-on-vmware-vsan-day-2-operations-and-man WFC can be upset by the freeze, but the failover timeout can be tweaked on the SQL AG to allow that) Despite snapshots of virtual RDM being supported (as per
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-0114693D-94BF-4D they are not when a WSFC is involved (according to this https://kb.vmware.com/s/article/2147661:"These activities are not supported and cause WSFC node failover: Increasing the size of disks, Hot adding memory, Hot adding CPU, Using snapshots, Pausing and/or resuming the virtual machine state, Memory over-commitment leading to virtual swapping or memory ballooning"and"In-guest clustering solutions that do not use a shared-disk configuration, such as SQL Mirroring, SQL Server Always On Availability Group (Non-shared Disk), and Exchange Database Availability Group (DAG), do not require explicit support statements from VMware")