Courseiva
vSphere Security →mediumMultiple Choice

vSphere Trust Authority: ESXi Attestation, TPM, and Key Provider Services

An organization is using vSphere Trust Authority (vTA) to secure ESXi hosts. A newly added ESXi host fails to attest with the Trust Authority. The administrator verifies that the host is connected to the vTA cluster and the trust relationship is configured. What is the most likely cause of the attestation failure?

⚠ Common exam trap

VCP-DCV often tests the distinction between host-level TPM (physical, required for vTA attestation) and guest-level vTPM (virtual, used for VM encryption), so candidates who see 'TPM' and pick the vTPM option fall into the trap.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The TPM on the ESXi host is disabled or not properly initialized.

vSphere Trust Authority attestation depends on a functioning, properly initialized TPM 2.0 on each ESXi host. The host's TPM measures the boot process (UEFI Secure Boot, bootloader, VMkernel modules) and produces quotes that the Trust Authority verifier compares against a trusted baseline. If the TPM is disabled in BIOS/UEFI or has not been initialized (no Endorsement Key taken ownership), the host cannot produce valid attestation quotes, so attestation fails even though the trust relationship and network connectivity are fine.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    The Trust Authority's network is isolated from the ESXi host's management network.

    Why it's wrong here

    vTA requires network connectivity but not necessarily the same network.

  • ✗

    The ESXi host is not in the same cluster as the Trust Authority.

    Why it's wrong here

    Attesting hosts are deliberately kept in a separate cluster from the Trust Authority cluster; membership in the same cluster is not required and is in fact discouraged. It is tempting because cluster membership usually governs trust relationships, but vTA works across clusters once the trust and network path are configured.

  • ✗

    The ESXi host does not have a virtual Trusted Platform Module (vTPM) attached.

    Why it's wrong here

    vTA attestation validates boot measurements and host identity; a vTPM is not a prerequisite for attesting to the Trust Authority. It is tempting because vTPMs underpin features such as VM encryption and virtual TPM-based attestation in other contexts, but their absence does not cause vTA attestation failure.

  • ✓

    The TPM on the ESXi host is disabled or not properly initialized.

    Why this is correct

    Attestation requires a healthy, enabled TPM to produce the quoted measurements the Trust Authority verifies. If the TPM is disabled or uninitialised, the host cannot generate valid attestation evidence, so the vTA cluster rejects it even though connectivity and trust configuration are correct.

About these practice questions

One of 281 original VCP-DCV practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar VCP-DCV questions

Written by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

This VCP-DCV practice question is part of Courseiva's free VMware certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VCP-DCV exam.