VCP-DCV Configure and Manage vSphere Networking Practice Question
A vSphere administrator is troubleshooting a virtual machine that cannot communicate on the network. The VM is connected to a port group on a vSphere Standard Switch. The administrator verifies that the physical switch port is configured as an access port for VLAN 10, and the port group VLAN ID is set to 10. The VM's guest OS has a static IP address in the correct subnet. Which step should the administrator take next to diagnose the issue?
⚠ Common exam trap
The trap here is overlooking the VM's adapter settings and instead assuming a mismatch between the physical switch and port group, even though they are already aligned.
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
✓
Check the virtual machine's network adapter settings to ensure it is connected and the correct port group is selected.
The physical switch and port group VLAN configurations are correct. The next logical step is to verify the VM's network adapter settings, as a disconnected adapter or wrong port group is a common cause. Checking the adapter is non-disruptive and directly addresses the VM's connectivity. Other options involve changing correct configurations or taking unnecessary actions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Change the port group VLAN ID to 4095.
Why it's wrong here
Setting the port group VLAN ID to 4095 would enable Virtual Guest Tagging, requiring the guest OS to tag traffic. The guest is not tagging (it has a static IP in the correct subnet, implying untagged traffic). This change would break connectivity further. The current VLAN ID 10 is correct for the access port configuration.
- ✓
Check the virtual machine's network adapter settings to ensure it is connected and the correct port group is selected.
Why this is correct
The most likely cause is that the VM's network adapter is disconnected or connected to the wrong port group. Verifying the adapter's connection status and port group assignment is a fundamental troubleshooting step. If the adapter is disconnected or on a different port group, the VM will not communicate. This should be checked before more complex diagnostics.
- ✗
Verify that the physical switch port is configured as a trunk.
Why it's wrong here
The physical switch port is already configured as an access port for VLAN 10, which is correct for a standard switch with VLAN ID 10 on the port group. Changing it to a trunk would not match the port group configuration and could cause further issues. The problem is likely not the physical switch port mode, since it aligns with the port group.
- ✗
Restart the management agents on the ESXi host.
Why it's wrong here
Restarting management agents is a drastic step and unlikely to resolve a single VM's connectivity issue. It could disrupt host management and other VMs. The problem is isolated to one VM, so the focus should be on the VM's configuration, not host-level services. This is not an appropriate next step.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 281 original VCP-DCV practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official VMware exam blueprint
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.