nerdexam
Broadcom-VMware

2V0-622D · Question #107

A new virtual machine cannot reach its default gateway. - The vSphere administrator checks that the virtual machine's vmnic is connected to the correct portgroup, and that the portgroup is on the corr

The correct answer is B. The wrong VLAN ID has been added to the portgroup.. A wrong VLAN ID on the portgroup isolates only VMs on that specific portgroup while leaving other VMs on the distributed switch unaffected.

Section 2 – Configure and Administer vSphere 6.5 Networking

Question

A new virtual machine cannot reach its default gateway.

  • The vSphere administrator checks that the virtual machine's vmnic is

connected to the correct portgroup, and that the portgroup is on the correct virtual switch

  • This is the only virtual machine on this portgroup
  • Other virtual machines that are on the host and connected to the same

Distributed switch are running as normal

  • The Distributed Switch has only one uplink

Which could be the cause of this issue?

Options

  • ABlock All Ports has been selected on the Distributed Switch.
  • BThe wrong VLAN ID has been added to the portgroup.
  • CThe VLAN has not been configured in virtual machine hardware settings.
  • DThe physical adapter is down.

How the community answered

(56 responses)
  • A
    13% (7)
  • B
    77% (43)
  • C
    4% (2)
  • D
    7% (4)

Why each option

A wrong VLAN ID on the portgroup isolates only VMs on that specific portgroup while leaving other VMs on the distributed switch unaffected.

ABlock All Ports has been selected on the Distributed Switch.

Enabling Block All Ports on the Distributed Switch would disrupt all VMs connected to that switch, but the scenario states other VMs on the same Distributed Switch are operating normally.

BThe wrong VLAN ID has been added to the portgroup.Correct

When a portgroup is assigned an incorrect VLAN ID, traffic from VMs on that portgroup is tagged or filtered incorrectly, preventing communication with the default gateway on the correct VLAN. Because this is the only VM on this portgroup, the misconfiguration affects only this VM while all others on different portgroups continue operating normally. Correcting the VLAN ID on the portgroup to match the upstream physical switch configuration would restore connectivity.

CThe VLAN has not been configured in virtual machine hardware settings.

VLAN configuration in vSphere is managed at the portgroup or switch level, not within the virtual machine's hardware settings, so this is not a valid or applicable configuration option.

DThe physical adapter is down.

Since the Distributed Switch has only one uplink, a downed physical adapter would sever connectivity for all VMs on that switch, not just the single VM on the isolated portgroup.

Concept tested: vSphere Distributed Switch VLAN portgroup misconfiguration

Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-7225A28C-DAAB-4E90-AE8C-795A755FBE27.html

Topics

#VLAN#distributed switch#network troubleshooting#portgroup

Community Discussion

No community discussion yet for this question.

Full 2V0-622D Practice