nerdexam
CompTIA

CV0-002 · Question #130

An administrator has configured a new VM with the correct IP, netmask, and default gateway. However, even with the vNIC showing a link and incoming and outgoing packets, the VM is unable to ping its…

The correct answer is D. The VM has an incorrect WWN. A VM with correct IP configuration, vNIC link, and packet activity is unable to ping its default gateway, suggesting a deeper underlying issue affecting its network function.

Operations

Question

An administrator has configured a new VM with the correct IP, netmask, and default gateway. However, even with the vNIC showing a link and incoming and outgoing packets, the VM is unable to ping its default gateway. Which of the following is MOST likely the reason the VM network connection is not functioning properly?

Options

  • AThe VM is not connected to the correct virtual switch.
  • BThe VM does not have jumbo frames enabled.
  • CThe VM is not in the LUN masking configuration.
  • DThe VM has an incorrect WWN.

How the community answered

(36 responses)
  • A
    3% (1)
  • B
    6% (2)
  • C
    3% (1)
  • D
    89% (32)

Why each option

A VM with correct IP configuration, vNIC link, and packet activity is unable to ping its default gateway, suggesting a deeper underlying issue affecting its network function.

AThe VM is not connected to the correct virtual switch.

If the VM were connected to the wrong virtual switch, it would typically result in a complete lack of connectivity to the gateway, but the question states 'incoming and outgoing packets', which implies some level of network activity, making it a less likely singular cause for this specific symptom.

BThe VM does not have jumbo frames enabled.

Jumbo frames are for optimizing large packet transfers and are not required for basic IP connectivity or ping operations with standard MTU sizes.

CThe VM is not in the LUN masking configuration.

LUN masking configuration governs storage access for hosts to LUNs and is entirely unrelated to IP network connectivity for a virtual machine.

DThe VM has an incorrect WWN.Correct

While a World Wide Name (WWN) is primarily associated with Fibre Channel storage, in some highly integrated virtualized environments, an incorrect WWN configured for a VM's storage components could potentially cause broader VM operational issues that indirectly manifest as a failure in its network stack's ability to communicate beyond its local virtual interface, even if the vNIC shows a link.

Concept tested: Advanced virtual machine network troubleshooting

Topics

#WWN#Fibre Channel storage#storage identifiers

Community Discussion

No community discussion yet for this question.

Full CV0-002 Practice