Configure and Manage vSphere Networking →hardMultiple ChoiceObjective-mapped

VCP-DCV Configure and Manage vSphere Networking Practice Question

Exhibit

Refer to the exhibit.

```
esxcli network ip interface list
vmk0
   Name: vmk0
   MAC Address: 00:50:56:60:00:01
   Enabled: true
   Portset: vSwitch0
   Portgroup: Management Network
   VDS Name: N/A
   IP Address: 192.168.1.10
   Subnet Mask: 255.255.255.0
   MTU: 1500

vmk1
   Name: vmk1
   MAC Address: 00:50:56:60:00:02
   Enabled: true
   Portset: dvs1
   Portgroup: iSCSI Network
   VDS Name: dvs1
   IP Address: 192.168.20.10
   Subnet Mask: 255.255.255.0
   MTU: 9000
```

An ESXi host has two VMkernel interfaces as shown in the exhibit. The iSCSI targets are on the same subnet as vmk1 and support jumbo frames. The administrator reports that iSCSI sessions are experiencing high error rates and poor performance. What is most likely the cause?

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 vDS port group for iSCSI does not have jumbo frames enabled (MTU 9000).

The iSCSI targets support jumbo frames (MTU 9000), but if the vDS port group for iSCSI is configured with the default MTU of 1500, packets will be fragmented, leading to high error rates and poor performance. The exhibit shows vmk1 is on the vDS, and the iSCSI targets are on the same subnet as vmk1, so the mismatch in MTU settings is the most likely cause. Option A is incorrect because management traffic on vmk0 is separate and does not affect iSCSI. Option B is incorrect because iSCSI VMkernel ports can be bound to a vDS. Option C is incorrect because the iSCSI network (vmk1) is on the same subnet as the iSCSI targets, so subnet mismatch is not the issue.

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 management network (vmk0) is also using the vDS, causing traffic interference.
Why it's wrong here
vmk0 is on a standard switch, not the vDS, so no interference.
✗
The iSCSI VMkernel port should not be bound to a vDS.
Why it's wrong here
iSCSI can use a vDS; binding to a vDS is not inherently problematic.
✗
The iSCSI network (vmk1) is on a different subnet than the iSCSI targets.
Why it's wrong here
The stem says targets are on the same subnet, so that's not an issue.
✓
The vDS port group for iSCSI does not have jumbo frames enabled (MTU 9000).
Why this is correct
If the vDS port group MTU is 1500, packets up to 9000 will be fragmented, causing errors. The VMkernel interface has MTU 9000, so the port group must match.

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