Why Does ESXi Certificate Verification Fail Even with Matching Thumbprint?
This VCP-DCV practice question tests your understanding of vsphere security. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
```
~ # openssl x509 -in /etc/vmware/ssl/rui.crt -noout -fingerprint -sha256
SHA256 Fingerprint: AB:CD:EF:12:34:56:78:90:AB:CD:EF:12:34:56:78:90:AB:CD:EF:12:34:56:78:90:AB:CD:EF:12:34:56:78:90
```
An administrator is adding an ESXi host to vCenter Server and is prompted to verify the host's certificate thumbprint. The administrator compares it to the output above and it matches. However, the add operation fails with a certificate verification error. What else could be the issue?
Exhibit
Refer to the exhibit.
```
~ # openssl x509 -in /etc/vmware/ssl/rui.crt -noout -fingerprint -sha256
SHA256 Fingerprint: AB:CD:EF:12:34:56:78:90:AB:CD:EF:12:34:56:78:90:AB:CD:EF:12:34:56:78:90:AB:CD:EF:12:34:56:78:90
```
A
The vCenter Server's certificate is invalid
Why wrong: The error is about the ESXi host's certificate, not vCenter Server's.
B
The certificate has expired
Why wrong: An expired certificate would have a different thumbprint or would be rejected earlier; the thumbprint match suggests the certificate is current.
C
The certificate is not signed by a trusted Certificate Authority
Why wrong: Self-signed certificates are common and can be used with thumbprint verification; missing CA trust is not the issue here.
D
The certificate common name does not match the hostname
If the certificate's CN does not match the host's FQDN, vCenter will reject the certificate during verification.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The certificate common name does not match the hostname
When adding an ESXi host to vCenter Server, the thumbprint verification ensures the host's certificate fingerprint matches what is expected, but it does not validate the certificate's subject attributes. If the certificate's Common Name (CN) does not match the ESXi host's FQDN or IP address used during the add operation, vCenter Server will reject the connection with a certificate verification error, even if the thumbprint is correct. This is because vCenter Server performs hostname verification as part of TLS/SSL certificate validation to prevent man-in-the-middle attacks.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 vCenter Server's certificate is invalid
Why it's wrong here
The error is about the ESXi host's certificate, not vCenter Server's.
✗
The certificate has expired
Why it's wrong here
An expired certificate would have a different thumbprint or would be rejected earlier; the thumbprint match suggests the certificate is current.
✗
The certificate is not signed by a trusted Certificate Authority
Why it's wrong here
Self-signed certificates are common and can be used with thumbprint verification; missing CA trust is not the issue here.
✓
The certificate common name does not match the hostname
Why this is correct
If the certificate's CN does not match the host's FQDN, vCenter will reject the certificate during verification.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume thumbprint verification alone guarantees certificate validity, overlooking that vCenter Server also performs hostname matching as part of TLS certificate validation.
Detailed technical explanation
How to think about this question
During ESXi host addition, vCenter Server performs TLS handshake and validates the host certificate against the provided thumbprint. However, it also enforces hostname verification per RFC 2818, checking that the certificate's CN or Subject Alternative Name (SAN) matches the hostname or IP address used to connect. In vSphere 7.0 and later, VMware Certificate Authority (VMCA) issues certificates with the hostname embedded, but if a custom certificate is used with a mismatched CN, the operation fails with a generic certificate verification error, even if the thumbprint matches.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the VCP-DCV exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
vSphere Security — This question tests vSphere Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The certificate common name does not match the hostname — When adding an ESXi host to vCenter Server, the thumbprint verification ensures the host's certificate fingerprint matches what is expected, but it does not validate the certificate's subject attributes. If the certificate's Common Name (CN) does not match the ESXi host's FQDN or IP address used during the add operation, vCenter Server will reject the connection with a certificate verification error, even if the thumbprint is correct. This is because vCenter Server performs hostname verification as part of TLS/SSL certificate validation to prevent man-in-the-middle attacks.
What should I do if I get this VCP-DCV question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.