Configure and Manage vSphere Networking →hardMultiple Choice

VCP-DCV Configure and Manage vSphere Networking Practice Question

Exhibit

esxcli network ip connection list | grep -E "443|80"
tcp   0   0  192.168.100.10:443   192.168.100.20:54321  ESTABLISHED  new-socket
tcp   0   0  192.168.100.10:80    192.168.100.30:12345  TIME_WAIT    new-socket
tcp   0   0  ::ffff:192.168.100.10:443  ::ffff:192.168.100.40:65432  ESTABLISHED  new-socket
netstat -an | grep -E "443|80"
tcp        0      0 192.168.100.10:443         0.0.0.0:*               LISTEN
tcp        0      0 192.168.100.10:80          0.0.0.0:*               LISTEN
tcp6       0      0 :::443                     :::*                    LISTEN

Refer to the exhibit. An administrator notices that the ESXi host is listening on both IPv4 and IPv6 for HTTPS. However, IPv6 traffic is not being forwarded to the host. Which configuration change is most likely needed?

⚠ Common exam trap

The trap is focusing on the listener/service state ('it's listening on IPv6, so IPv6 must be enabled') and overlooking that a bound listener without an IPv6 default gateway cannot route replies to off-subnet clients — candidates often pick switch-level or disable-IPv6 options instead of the host routing fix.

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

✓

Configure a default gateway for the IPv6 stack on the host.

If the ESXi host is listening on IPv6 for HTTPS but IPv6 traffic isn't being forwarded to it, the host likely lacks a default gateway for its IPv6 stack. Without an IPv6 default gateway, the host can communicate on-link but cannot route replies to off-subnet IPv6 clients, so forwarded traffic never returns. Configuring an IPv6 default gateway on the host resolves the routing gap.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Configure a default gateway for the IPv6 stack on the host.
Why this is correct
Without a default IPv6 gateway, the host can receive IPv6 traffic on its local subnet but cannot route replies beyond it, so forwarded IPv6 packets fail. Configuring the gateway satisfies the stem's requirement that IPv6 traffic reach the host across subnets, restoring bidirectional HTTPS connectivity.
✗
Disable IPv6 and use only IPv4.
Why it's wrong here
Disabling IPv6 removes the listener but does not make the host reachable over IPv6; the stem states IPv6 traffic is not being forwarded, so the routing or upstream forwarding path must be fixed. IPv4-only is valid when IPv6 is genuinely unused and no IPv6 clients or services depend on the host.
✗
Remove the IPv4 HTTPS listener to force IPv6.
Why it's wrong here
Removing the IPv4 HTTPS listener does not cause IPv6 traffic to be forwarded; the host already listens on IPv6, so the fault lies in network forwarding, not listener configuration. It is tempting when dual-stack listeners appear to compete, but disabling IPv4 would only break existing IPv4 management access.
✗
Enable IPv6 on the vSphere Distributed Switch.
Why it's wrong here
The host already listens on IPv6, so the distributed switch is not preventing the listener from binding; the missing element is IPv6 forwarding on the VMkernel interface or upstream network. It is tempting because the vDS carries traffic, but enabling IPv6 there does not configure the host's own IPv6 routing.

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