An administrator is tasked to install a new VMware ESX host to an existing cluster. When the installation is completed, the host is not able to be reached from the vCenter. When testing the host's…

Question

Options

• AVerify the correct TCP/IP information is configured.
• BVerify the DVS configuration in vCenter.
• CReinstall ESX on the host.
• DDisconnect and reconnect the physical network cable.

• A
  74% (50)
• B
  9% (6)
• C
  4% (3)
• D
  13% (9)

Explanation

Option A is correct because the symptoms - unreachable default gateway, DNS servers, and unresolvable hostname - collectively point to a misconfigured TCP/IP stack (wrong IP address, subnet mask, or gateway) rather than a physical or infrastructure problem. When all network targets fail simultaneously, the most logical first step is to verify the foundational network configuration on the host itself before assuming external causes.

Why the distractors are wrong:

• B (DVS configuration): A Distributed Virtual Switch issue would typically affect VM traffic or multiple hosts, not a single new host's management network at the IP layer - and the VLAN is already confirmed correct.
• C (Reinstall ESX): Reinstalling is a last resort; it's destructive and time-consuming when a simple misconfiguration is far more likely the cause.
• D (Reconnect physical cable): Physical connectivity is already ruled out - adapters are confirmed connected and the VLAN is set correctly, so the problem is logical, not physical.

Memory tip: Think of the OSI model from the bottom up - the question already eliminates Layer 1 (physical cables) and Layer 2 (VLAN), so the next layer to check is Layer 3 (IP/TCP configuration). When all IP-level targets fail on a freshly installed host, always suspect the IP settings first.

No community discussion yet for this question.