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 achieve the best performance for the database virtual machines and tolerate two host failures in a vSAN OSA cluster, the administrator must use RAID-1 as the RAID configuration in the storage policy. RAID-1 is a mirroring technique that creates multiple replicas of each object across different hosts. RAID-1 provides the best performance among the available RAID configurations, as it does not involve any parity calculations or stripe splitting. To tolerate two host failures, the administrator must set the Failures to Tolerate (FTT) policy to 2, which means that each object will have three replicas. The other options are not correct. RAID-5 and RAID-6 are erasure coding techniques that split each object into data segments and parity segments across different hosts. RAID-5 can tolerate one host failure, while RAID-6 can tolerate two host failures. However, both RAID-5 and RAID-6 have lower performance than RAID-1, as they involve more complex calculations and network traffic. RAID-0 is a striping technique that splits each object into multiple stripes across different hosts. RAID-0 does not provide any data redundancy or fault tolerance, and therefore cannot tolerate any host failure. References: RAID Configurations, FTT, and Host Requirements; RAID 5 or RAID 6 Design Considerations

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