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 vSphsrs Host Client using the FQDN for the exxi101 and complete the configuration (Choose three.)
- Ensure a DNS A Record Is created for the VMware ESXI host on the corporate DNS servers.
- Update the VMware ESXI Management Network DNS configuration to use the corporate DNS servers for name, resolution.
- Update the VMware ESXI Management Network IPv4 configuration to use a static a IPv4 address.
- Configure at least two network adapters for the VMware ESXI Management Network.
- Set the value of the VMware ESXI Management Network VLAN ID to 10.
- Disable IPv6 for the VMware ESXI Management Network.
Answer(s): A,B
Explanation:
To successfully log into the vSphere Host Client using the FQDN for the ESXi host, the administrator needs to ensure a DNS A Record is created for the VMware ESXi host on the corporate DNS servers, which maps its FQDN to its IP address; and update the VMware ESXi Management Network DNS configuration to use the corporate DNS servers for name resolution, which allows resolving its FQDN.
Reference:
https://docs.vmware.com/en/VMware-
vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-D2F9C9A9-5F2C-4F1C-BF76- EA1CDBEEFC2D.html https://docs.vmware.com/en/VMware- vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-9F1D4E96-3392-4681-A00C- B05D58A422F8.html
Reveal Solution Next Question