VCP-DCV Configure and Manage vSphere Networking Practice Question

• ✓ A.Port group name
• B.MTU
• C.Network adapter type (e.g., E1000)
• D.Security policy
• ✓ E.VLAN ID

Why A: For basic network connectivity of virtual machines on a vSphere Standard Switch, a port group must be created. Two essential settings are the port group name (to identify the network) and a VLAN ID (to associate the VMs with the correct VLAN; VLAN 0 is the default untagged VLAN). Without a name, the port group cannot be created; without a VLAN ID, VMs may not be properly segmented or may lack network access. Other options like MTU, network adapter type, and security policy are not essential for basic connectivity.

• ✓ A.VLAN ID
• B.Uplink teaming policy
• C.Number of ports
• ✓ D.Port group name
• E.Traffic shaping policy

Why A: A VLAN ID must be specified to define the VLAN membership for the distributed port group, ensuring proper network segmentation and traffic isolation. The port group name is required as a unique identifier for administrative management and reference within the vSphere environment.

• A.The vSwitch has only one uplink.
• B.The virtual machines have duplicate MAC addresses.
• ✓ C.The physical switch port is not configured to pass VLAN 100.
• D.The virtual machines are using different subnets.

Why C: The issue is that VMs on VLAN 100 can communicate among themselves but not with the physical network. This indicates that VLAN tagging is working within the vSwitch (inter-VM communication works), but the physical switch port is not configured to pass VLAN 100 traffic. The uplink from the ESXi host to the physical switch must be set as a trunk port allowing VLAN 100, or if using an access port, it must be set to VLAN 100. Option A (only one uplink) is sufficient for connectivity. Option B (duplicate MAC addresses) would cause issues even locally. Option D (different subnets) would also affect local communication, but local communication works, so these are not the cause.

• A.The vDS is not configured with a VLAN trunking policy.
• B.The VM's network adapter is configured with the wrong MAC address.
• C.The distributed port group has forging transmits set to reject.
• ✓ D.The physical switch ports connecting the ESXi hosts are not configured as trunk ports for the VLAN.

Why D: The VM can communicate only with other VMs on the same ESXi host because VLAN-tagged frames cannot pass through the physical switch ports to other hosts. For VMs on the same VLAN to communicate across hosts, the physical switch ports connecting the ESXi hosts must be configured as trunk ports that allow the relevant VLAN. Option A is incorrect because the vDS does not require a separate VLAN trunking policy; the port group VLAN ID handles tagging. Option B is incorrect because the MAC address is automatically assigned and would not cause host-only communication. Option C is incorrect because the 'forging transmits' security policy controls MAC address changes, not basic connectivity.