An architect is designing for a production vSAN cluster, and the customer introduced these requirements related to File Services:
✑ A minimum of 12 files shares.
✑ 30TB NFS capacity to mount workload VMs.
What should be the architect's recommendations?
The architect should raise concerns regarding support when running VMs on an NFS share as a risk. Running VMs directly on an NFS share is generally not recommended in a vSAN environment due to support limitations. It is important to address this potential issue before proceeding with the design to ensure the solution will be supported and reliable.
I would go for C as VSAN NFS shares as I wouldn't recommend running VMs on it
Correct answer is C. On the vSAN File Services section, the 2nd question gives the answer. https://core.vmware.com/resource/vsan-frequently-asked-questions-faq#section5
i go with c - you're not allowed to run vms on the nfs share
I believe answer should be C
Ignore im incorrect
customer require enable vSAN File Service, vSAN File Service will provide 30T NFS file service.
As per Oornitorrinco's link: "No, it is not supported to mount NFS to ESXi for the purpose of running virtual machines. The NFS shares may be used to mount NFS directly to virtual machines running on the vSAN cluster, but may not be used to store VMDKs for running virtual machines."
Agreed with answer D - as per below - Maximum of 64 active FS containers/protocol stacks are provisioned when using vSAN 7.0 U2 - With 7.0 U1 it was 32 active FS containers at most - With 7.0 it was 8 active FS containers at most - Maximum number of shares per cluster is 100 starting vSAN 7.0 U2 - Maximum size of the file share is equal to the maximum available capacity of the vSAN cluster - FS VMs are provisioned with 4 vCPUs and 8GB of memory
how does this relate to the question?