Configure and Manage vSphere Networking →mediumMultiple ChoiceObjective-mapped

VCP-DCV Configure and Manage vSphere Networking Practice Question

Exhibit

esxcli network ip dns server list
   DNSServers: 192.168.10.2, 192.168.10.3
esxcli network ip dns search list
   SearchDomains: localdomain
esxcli network ip dns suffix list
   Suffixes: localdomain
vmkping -c 3 192.168.10.2
PING 192.168.10.2 (192.168.10.2): 56 data bytes
64 bytes from 192.168.10.2: icmp_seq=0 ttl=128 time=0.456 ms
64 bytes from 192.168.10.2: icmp_seq=1 ttl=128 time=0.512 ms
64 bytes from 192.168.10.2: icmp_seq=2 ttl=128 time=0.478 ms
vmkping -c 3 hostname.localdomain
ping: unknown host hostname.localdomain

Refer to the exhibit. An administrator cannot resolve the hostname of a DNS server using the ESXi host. What is the most likely cause?

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 DNS servers are not configured correctly for the domain.

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 search domain is incorrectly set to localdomain.
Why it's wrong here
The search domain is correct for the environment.
✗
The DNS servers are unreachable.
Why it's wrong here
The ping to the IP address succeeded.
✓
The DNS servers are not configured correctly for the domain.
Why this is correct
The hostname resolution failed, indicating the DNS server cannot resolve the name.
✗
The ESXi host is not configured to use DNS.
Why it's wrong here
DNS servers are configured.

Visual reference

Go deeper

VCP-DCV Configure and Manage vSphere Networking Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question