After installation of a host in your test environment, you need to move it to production. The only major change that needs to be made is that the hostname of the server needs to change. What are two…

Question

Options

• ALogin to the Direct Console User Interface and change it from here.
• BEdit the Default TCP/IP Configuration from the vSphere Web Client.
• CUse the Ruby vSphere Client to send a script to the ESXi host that updates the hostname.
• DUpdate the information in DNS and the ESXi host will automatically update with these changes.

• A
  86% (50)
• C
  5% (3)
• D
  9% (5)

Explanation

There are two supported methods to change an ESXi host's hostname without manually editing configuration files on the host.

A – Direct Console User Interface (DCUI): The DCUI is the local console menu accessible on the physical host or via remote console. It provides a menu-driven interface where administrators can configure network settings, including the hostname, without touching raw config files like /etc/hosts.

B – vSphere Web Client (Default TCP/IP Configuration): Within the vSphere Web Client, you can navigate to the ESXi host → Configure → Networking → TCP/IP Configuration → Default TCP/IP Stack, and edit the hostname from there. This is a GUI-based approach that modifies the setting without direct file editing.

Why C is wrong: The Ruby vSphere Console (RVC) is a real tool, but using a custom script to update hostname is not a standard, supported administrative method for this task and is not equivalent to the two official channels above.

Why D is wrong: ESXi does not automatically pull or update its hostname based on DNS changes. DNS resolves names to IPs, but the host's configured hostname must be explicitly changed through a management interface.

No community discussion yet for this question.