A company hosts a vSAN 7 stretched cluster for all development workloads. The original sizing of a maximum of 250 concurrent workloads in the vSAN cluster is no longer sufficient and needs to increase to at least 500 concurrent workloads within the next six months.
To meet this demand, the original 8-node (4-4-1) cluster has recently been expanded to 16 nodes (8-8-1).
Which three additional steps should the administrator take to support the current growth plans while minimizing the amount of resources required at the witness site? (Choose three.)
Answer : A, B, C
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-05C1737A-5FBA-4AEE-BDB8-3BF5DE569E0A.html
An administrator wants to check the performance metrics for the workloads and their virtual disks that are running on a vSAN cluster, but no statistical charts are displayed in the vSphere client.
Why is this behavior being seen?
Answer : C
: Some tools allow for measuring latency peaks. This unfortunately isn't ideal, as it can unfairly represent statistical outliers, which may very well occur when there is little to no I/O activity. The best way to understand the actual behavior of VM and application latencies is to observe in time based performance graphs. Depending on the level of detail, you may need to measure at the individual VMDK level. Become familiar with these graphs to determine what is normal, and what is not for that given application. This is where you can use built-in functionality of vCenter and the vSAN performance service metrics to gather this information.
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-monitoring.doc/GUID-EF27701E-7BAC-4E76-9D2F-E1C58CAAB06D.html
An organization has two vSAN clusters managed by the same vCenter Server, each providing 100TB of storage. The first cluster runs at 75% of its storage capacity, and the second cluster runs at 50% of its storage capacity.
The company also has the following:
* An iSCSI array of 300TB. which runs at 76% of its capacity
* A NAS system of 200TB, which runs at 10% of its capacity
* A Fiber channel (FC) array of 300TB, which runs at 80% of its capacity
The administrator is asked to add an additional 25TB of storage to the first cluster. The administrator is also made aware that there is no budget to purchase new hardware and that the vSAN Storage Policy Based Management must be kept in place.
Which storage option will work for this use case?
Answer : D
https://blogs.vmware.com/virtualblocks/2020/09/16/introducing-vmware-vsan-hci-mesh/
In a stretched vSAN cluster, how is Read Locality established after fail over to the secondary site?
Answer : C
In the event of a failure or maintenance event, the virtual machine is restarted on the remote site. The 100% rule continues in the event of a failure. This means that the virtual machine will now read from the replica on the site to which it has failed over. One consideration is that there is no cached data on this site, so cache will need to warm for the virtual machine to achieve its previous levels of performance.
Which statement accurately describes the result when proper VM Storage Policy Affinity Rules on a stretched vSAN cluster are set?
Answer : B
Setting proper VM/Host Group Rules and VM Storage Policy Affinity Rules are beneficial for several reasons Bandwidth is not unnecessarily sent across the inter-site link Lower inter-site bandwidth utilization In the situation where the alternate site is disconnected, the VM will continue to have access to its vmdk. from https://core.vmware.com/resource/vsan-stretched-cluster-guide#sec7341-sub5
A customer is planning to deploy a vSAN cluster to host their in-house distributed ERP system. The hardware specifications for their server nodes include:
* 2 x Intel Xeon CPU E5-2697 v3 @ 2.60GHz
* 1TB memory
Which boot device is supported for the vSAN ESXi nodes for this customer?
Answer : A
If the memory of the ESXi host has 512 GB of memory or less, you can boot the host from a USB, SD, or SATADOM device. If the memory of the ESXi host has more than 512 GB, consider the following guidelines. * You can boot the host from a SATADOM or disk device with a size of at least 16 GB. When you use a SATADOM device, use a single-level cell (SLC) device. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-B09CE19D-A3F6-408C-AE69-35F65CBE66E1.html
Due to the success of the recently deployed developer-only private cloud solution, a company has a new requirement to at least double the usable capacity in their all-flash vSAN cluster.
The vSAN cluster is deployed into a co-located datacenter that is owned by a third-party hosting company. The hosting company charges a fixed monthly cost for rack space and power consumption. The service owner has been given a limited budget for additional hardware purchases, but not for on-going co-location costs.
The current vSAN cluster has the following configuration:
* 10 vSAN Nodes with 2 CPUs (20 cores), 512 GB RAM
* 1 Disk Group per vSAN node
- 1 x 400 GB
- 4 x 1.8 TB
* De-duplication and Compression is enabled.
* vSAN Capacity is currently:
- Total: 72 TB
- Usable: ~40 TB (FTT1/RAID1) and ~60 TB (FTT1/RAID5).
As a result of any action taken, the service owner would like to ensure that overall availability of the vSAN cluster is increased.
Which two recommendations meet the requirement to increase capacity while maintaining service availability? (Choose two.)
Answer : A, C
Option A meets the requirement by adding additional SSDs to each vSAN node, which will increase the total capacity of the vSAN cluster. By installing the same type of SSDs that are currently being used, this option will also maintain the same level of service availability.
Option C meets the requirement by creating a new disk group and adding the newly installed SSDs to it. By creating a new disk group, it will allow you to use the new SSDs as a separate cache and capacity tier, which will improve the cluster's performance and increase the usable capacity.