5V0-22.23 Exam Dumps : VMware vSAN Specialist v2

Two characteristics of the vSAN Data-At-Rest Encryption (DARE) are that it is Software Defined and works independently of the Cache or Capacity drives installed on the Nodes, and that it continues to operate unaffected during downtime on vCenter Server. DARE is a feature that encrypts all data stored on vSAN disks using AES-256 XTS mode. It does not require Self-Encrypting Drives (SEDs) to work, as it uses software-based encryption keys that are generated by an external Key Management Server (KMS) or a vSphere Native Key Provider. DARE also does not depend on the type or size of the disks used in the vSAN cluster, as it encrypts data after all other processing, such as deduplication and compression, is performed. DARE can function even when the vCenter Server is offline or unavailable, as it uses key persistence to store the encryption keys on the ESXi hosts or in a Trusted Platform Module (TPM). The hosts can access the keys without contacting the KMS or the vCenter Server. The other options are notcorrect, as they do not describe DARE accurately. DARE does not need to be enabled together with the vSAN Data-In-Transit encryption, as they are independent features that can be enabled or disabled separately. Data-In-Transit encryption encrypts data that is transmitted between hosts in a vSAN cluster using secure sockets layer (SSL) certificates. DARE is supported on Stretched Cluster environments, as it can encrypt data across multiple sites using site affinity rules. 

To view the resynchronizing metrics, the vSAN administrator should open the Backend performance category. This category shows the performance of vSAN data components, such as read/write latency, IOPS, throughput, congestion, and resync traffic. The other categories are not relevant for this task. Disks shows the performance of physical disks in the cluster, Host Network shows the network performance of vSAN hosts, and Resvnc Latency shows the latency of resynchronization operations. References: 1, page 23; 3, section 6.4

To protect a virtual machine against a disk or disk group failure, the storage policy must have a failure tolerance method (FTM) of RAID-1 or RAID-6 and a failure to tolerate (FTT) value of at least 1. RAID-1 mirrors the data across multiple disk groups, while RAID-6 uses erasure coding to stripe the data and parity information across multiple disk groups. RAID-5 is not suitable for this scenario, as it can only tolerate one disk failure per stripe. FTT 2 or 3 would require more disk groups than available in the cluster. Therefore, the correct options are C and E. References: 1, page 8; 2, section 3.1