2V0-21.23 Question 255
Single answerAn organization is implementing a secure boot process for its ESXi 8.0 hosts to meet compliance requirements. During the setup, the administrator enables UEFI Secure Boot in the host's firmware and ensures the installation of VMware-signed bootloader and kernel modules. However, after rebooting, the host fails to boot successfully. What step could the administrator have missed to ensure a secure boot process?
- A
Updating the host's firmware to the latest version supported by VMware
- B
Enabling VMkernel logging for secure boot verification
- C
Verifying that the host's hardware supports TPM (Trusted Platform Module)
- D
Ensuring the ESXi host has a trusted certificate chain for the Secure Boot process
Show answer and explanation
Correct answer: A
Explanation
Secure Boot on ESXi requires the host's firmware to support UEFI Secure Boot. If the firmware is outdated or incompatible, the host may fail to boot. Updating the firmware ensures it supports the required UEFI Secure Boot features, allowing the host to boot securely with VMware-signed bootloader and kernel modules.
- A. Correct.
Updating the host's firmware is crucial to ensure compatibility with secure boot and UEFI requirements. Outdated firmware may not work properly with UEFI Secure Boot, causing boot issues.
- B. Incorrect.
Enabling VMkernel logging is useful for diagnostics but is unrelated to the secure boot process or resolving boot failures caused by UEFI Secure Boot.
- C. Incorrect.
While TPM support enhances security, it is not a mandatory requirement for Secure Boot in ESXi. Secure Boot can function without TPM as long as the UEFI Secure Boot process is properly configured.
- D. Incorrect.
A trusted certificate chain is important for secure communications but is not directly related to the Secure Boot process on ESXi hosts.