An administrator is setting up vSAN file services on a vSAN cluster but is unable to join the vSAN File Services to the domain.
Which two possible reasons could explain this failure? (Choose two.)
An administrator is setting up vSAN file services on a vSAN cluster but is unable to join the vSAN File Services to the domain.
Which two possible reasons could explain this failure? (Choose two.)
One possible reason for the failure could be the use of a read-only domain controller, as it cannot create machine accounts necessary for joining the domain. Another possible reason is the use of pre-created computer objects for the file services in Active Directory, which are not supported by vSAN File Services. Ensuring these conditions are met is critical for the successful joining of vSAN File Services to the domain.
A & E vSAN File Services does not support the following: Read-Only Domain Controllers (RODC) for joining domains because the RODC cannot create machine accounts. As a security best practice, a dedicated org unit must be pre-created in the Active Directory and the user name mentioned here must be controlling this organization. Pre-created computer objects for file servers are not supported. Make sure that the user provided here have sufficient privilege over the organizational unit. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-CA9CF043-9434-454E-86E7-DCA9AD9B0C09.html
A & C RODC's and Multi-Domain are not supported Reference: https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-administration/GUID-CA9CF043-9434-454E-86E7-DCA9AD9B0C09.html
My answer is A, C
A C. https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-administration/GUID-CA9CF043-9434-454E-86E7-DCA9AD9B0C09.html