2V0-21-23 practice question 9 of 25

administrator successfully installs VMware ESXi onto the first host of a new vSphere duster but makes no additional configuration changes. When…

Full set: 107 questions
administrator successfully installs VMware ESXi onto the first host of a new vSphere duster but makes no additional configuration changes. When attempting to log into the vSphere Host Client using the Fully Qualified Domain Name (FQDN) of the host, the administrator receives the following error message: ‘’server Not Found –we can’t connect to the server at esxit101.corp.local.’’ • Host FQDN: esxi 101. Corp. local • Management VLAN ID: 10 • DHCP: No • Management IP Address: 172.16.10.101/24 • Management IP Gateway: 172.16.10.1 • Corporate DNS Servers: 172.16.10.5, 172.16.10.6 • DNS Domain: corp.local Which three high level tasks should the administrator complete, at a minimum, in order to successfully log into the the vSphsrs Host Client using the FQDN for the exxi101 and complete the configuration (Choose three.)
Answer options
A: Ensure a DNS A Record Is created for the VMware ESXI host on the corporate DNS servers, Correct answer
B: Update the VMware ESXI Management Network DNS configuration to use the corporate DNS servers for name, resolution, Correct answer
C: Update the VMware ESXI Management Network IPv4 configuration to use a static a IPv4 address. Correct answer
D: Configure at least two network adapters for the VMware ESXI Management Network.
E: Set the value of the VMware ESXI Management Network VLAN ID to 10.
F: Disable IPv6 for the VMware ESXI Management Network.
Correct Answer:
A. Ensure a DNS A Record Is created for the VMware ESXI host on the corporate DNS servers,; B. Update the VMware ESXI Management Network DNS configuration to use the corporate DNS servers for name, resolution,; C. Update the VMware ESXI Management Network IPv4 configuration to use a static a IPv4 address.
Explanation

The browser error shows that the client cannot resolve the host name.
1) A forward (A) record that maps esxi101.corp.local → 172.16.10.101 must exist on the corporate DNS servers so the client can translate the FQDN.
2) ESXi itself must know where to send DNS queries and advertise its correct host and domain names; therefore its Management Network DNS settings must be pointed at the corporate DNS servers.
3) Because no DHCP service is available, the Management Network needs a manually assigned, static IPv4 address (172.16.10.101/24) so that the A-record has a reachable target. These three steps are the minimum required to log in with the FQDN and finish host configuration.

Why Incorrect

D. A single NIC is fully supported for the Management Network; additional adapters are optional for redundancy, not name-resolution.
E. VLAN tagging may or may not be needed (depends on switch configuration); it is not inherently required for DNS/FQDN reachability.
F. IPv6 settings do not affect IPv4 DNS resolution or the ability to reach the host by its IPv4 FQDN.

References

1. VMware vSphere Installation and Setup 7.0, “Configure the Management Network – Set Static IPv4 Address,” pp. 66-67.

2. VMware vSphere Networking 7.0, “Configuring DNS and Routing for ESXi,” Section 3.3, pp. 31-33.

3. VMware KB 1005569, “DNS requirements for ESX/ESXi hosts and vCenter Server” (para. 1-3).

4. VMware vSphere Networking 7.0, “Host Name and Domain Settings,” pp. 34-35 (shows need for DNS servers and forward record).

Scroll to Top