Free VMware 3V0-23.25 Practice Exam with Questions & Answers | Set: 3

The correct process is to present the Fibre Channel LUNs from the storage array, rescan HBAs on each ESX host, create the VMFS datastore once, verify that the datastore is visible on all hosts, and confirm the result in vCenter. Fibre Channel storage requires correct SAN fabric zoning, LUN masking, host registration, and HBA discovery so that all hosts in the workload domain cluster can see the same shared LUN. After the array presents the LUN, each host must rescan its HBAs to discover the new storage device. VMFS is a clustered file system, so the datastore is created only once on the shared LUN. The datastore then becomes available to all hosts that have access to that device; it must not be independently formatted on each host. Creating the VMFS datastore separately on each host would risk datastore corruption or duplicate formatting. The final validation step is confirming datastore visibility and accessibility for all cluster hosts in vCenter. Reference topics: Fibre Channel Storage Model, HBA Rescan, Create VMFS Datastore, Shared VMFS Datastore Visibility.

When vSAN Data-at-Rest Encryption uses an external KMS, vCenter requests a Key Encryption Key (KEK) from the KMS and stores only the key ID, not the key itself. ESX hosts use the KEK to decrypt the Data Encryption Keys that protect the encrypted vSAN disk data. If a host reboots, it must retrieve the KEK from the KMS before its encrypted vSAN disk groups can be mounted. The guide states that when a host reboots, it does not mount its disk groups until it receives the KEK. Key persistence can allow continued operation when the key server is unavailable, but the documented persistence mechanism relies on TPM-backed key persistence across reboots. In this scenario, the host does not have a Trusted Platform Module and the KMS is temporarily unavailable. Therefore, the ESX host can boot, but the encrypted storage remains unavailable and unmounted until communication with the KMS is restored. Reference topics: vSAN Data-at-Rest Encryption, External KMS, Key Encryption Key, Encryption Key Persistence.