Courseiva
Configure and Manage vSphere NetworkingmediumMultiple ChoiceObjective-mapped

VCP-DCV Configure and Manage vSphere Networking Practice Question

Exhibit

Refer to the exhibit.
[root@esxi01:~] esxcli network vswitch standard list
Standard Switch: vSwitch0
   Name: vSwitch0
   Class: cSwitch
   Num Ports: 128
   Used Ports: 3
   Configured Ports: 128
   MTU: 1500
   CDP: listen
   Beacon Enabled: false
   Beacon Interval: 0
   Uplinks: vmnic0
   Portgroups:
      Management Network
         VLAN ID: 0
         Used Ports: 1
         Uplinks: vmnic0
      VM Network
         VLAN ID: 100
         Used Ports: 1
         Uplinks: vmnic0
   VMkernel Network Adapters:
      vmk0
         Portgroup: Management Network
         IP Address: 192.168.1.10
         Subnet Mask: 255.255.255.0
         MAC Address: 00:50:56:ab:01:01

A virtual machine connected to the 'VM Network' port group is unable to obtain an IP address from the DHCP server located on the same subnet (192.168.1.0/24). The DHCP server is connected to the physical switch which is configured as an access port for VLAN 100. What is the most likely cause of the issue?

⚠ Common exam trap

Candidates may assume the physical switch uplink configuration is the only factor, overlooking that the default VM Network port group (VLAN 0) places the VM in a different VLAN than the DHCP server. The primary misconfiguration is the port group VLAN setting, not the trunk mode of the physical switch.

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

The port group should use a different VLAN ID.

The virtual machine is connected to the default 'VM Network' port group, which has VLAN ID 0 (no VLAN tagging), sending untagged traffic. The DHCP server is connected to a physical switch port configured as an access port for VLAN 100, placing it in VLAN 100. Because the VM and the DHCP server are on different VLANs, they cannot communicate at Layer 2, preventing DHCP discovery broadcasts from reaching the server. The most likely cause is that the port group should use a different VLAN ID (VLAN 100) to match the DHCP server's VLAN. Changing the port group to VLAN 100 will tag the traffic, requiring a trunk on the physical uplink, but the root cause is the VLAN mismatch, not solely the uplink configuration.

Answer analysis

Option-by-option breakdown

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

  • The physical uplink vmnic0 is not configured as a trunk on the physical switch.

    Why it's wrong here

    Incorrect. While a trunk may be needed if the port group is set to VLAN 100, the direct cause of the issue is the VLAN mismatch. The default VM Network uses VLAN 0, so even with a trunk, communication fails unless the native VLAN is 100.

  • The port group should use a different VLAN ID.

    Why this is correct

    Correct. The VM Network port group defaults to VLAN 0, placing the VM in a different VLAN from the DHCP server (VLAN 100). Configuring the port group with VLAN 100 aligns the broadcast domains and resolves the issue.

  • The standard switch has MTU of 1500 but DHCP uses 1500.

    Why it's wrong here

    Incorrect. MTU settings are not relevant to the VLAN mismatch and DHCP uses standard 1500 bytes.

  • The DHCP server is on a different VLAN.

    Why it's wrong here

    Partially true, but not the most likely cause. The DHCP server is indeed on VLAN 100, but the root issue is that the VM's port group is not set to that VLAN, not the server's placement.

  • The VMkernel port vmk0 has an IP address in the same subnet but is not required for DHCP.

    Why it's wrong here

    Incorrect. The VMkernel port vmk0 is unrelated to virtual machine DHCP traffic; it serves management functions.

Visual reference

Client DHCP Server 1 Discover (broadcast) 2 Offer (IP: 192.168.1.10) 3 Request (I accept) 4 Acknowledge (lease confirmed) DORA — the four-step DHCP lease process

About these practice questions

This VCP-DCV question is part of Courseiva's 498-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This VCP-DCV practice question is part of Courseiva's free VMware certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VCP-DCV exam.