A failed storage controller has two vSAN disk groups attached. The components contained on the drives in those disk groups are marked Degraded. vSAN reports that some objects do not comply with their assigned storage policy.
How is the compliance issue resolved?
When a storage controller fails and vSAN components are marked as Degraded, the repair process is initiated only after the CLOM (Cluster Object Manager) Repair Delay Timer expires. This delay is intended to handle transient issues without causing unnecessary rebuilds. Immediate rebuilding does not take place; instead, the system waits to see if the problem resolves on its own before starting the repair.
During planned maintenance of a four-node vSAN cluster, an outsourced IT contractor accidentally removed a 2.5" SSD cache disk from one of the vSAN nodes.
The storage policy has been configured with FTT=1 RAID 1, and the disk management UI marked the disk group as absent.
Which remediation steps should the administrator select to ensure VMs become compliant with the storage policy as soon as possible?
When a disk group is marked as absent due to the removal of a cache disk in a vSAN cluster, it's important to quickly ensure that the VMs are compliant with the storage policy. With FTT=1 RAID 1, the vSAN cluster can tolerate the failure of one host or its components. Given that there are still three operational nodes, the optimal remediation step is to use the vSAN Health Check to retest and then repair the objects immediately. This will resynchronize the absent objects on the remaining available hosts in the cluster, making the VMs compliant as soon as possible.
A 3-node All-Flash vSAN cluster has this configuration:
✑ One disk group per host
✑ All disk groups have identical make & model disks of an 800GB NVMe SSD cache and 2x 4TB SAS SSDs each
An administrator has been tasked with expanding storage capacity by adding one additional disk group with this configuration:
✑ 1.6TB SAS SSD cache and 1x 4TB SAS SSDs
Assuming all the disks are compliant with the vSAN HCL, which is true?
The additional disk group would make this cluster an unsupported configuration. In vSAN clusters, all disk groups within a host should ideally have a consistent configuration, including the type and size of cache and capacity drives. Mixing different types of SSDs (such as NVMe and SAS) and having different cache sizes among disk groups can create performance issues and inconsistencies. VMware best practices recommend homogeneity in disk group configurations to ensure optimal performance and supportability.
Which two statements are true about enabling deduplication and compression on an All-Flash vSAN cluster with data? (Choose two.)
On-disk format version 3.0 or later is required to support deduplication and compression, and enabling these features on an All-Flash vSAN cluster with existing data requires data evacuation and a disk format upgrade of all the disk groups.
Which two statements regarding networking are true for a vSAN Stretched Cluster? (Choose two.)
For a vSAN Stretched Cluster, a 5ms RTT or less is required between the data sites, ensuring low latency for efficient data replication across sites. Additionally, the cluster can utilize either Layer 2 or Layer 3 communication for the vSAN network, providing flexibility in the network configuration that can match various network topologies.