An administrator is troubleshooting intermittent network connectivity issues on an AHV host and runs the...

Incrementing rx_crc_errors usually point to a Layer 1 or physical-path problem, not a CPU or memory issue. CRC errors mean frames are arriving corrupted, and the most common reasons are a faulty cable, damaged transceiver, bad port, or another physical medium issue between the AHV host and the switch. Because the CRC counter is specifically increasing while other counters like missed, FIFO, and general rx errors remain low, this strongly suggests corruption during transmission rather than host overload. That makes B the correct answer.

A duplex mismatch can cause broader link-performance problems, but the pattern of steadily rising CRC errors is much more classically tied to bad physical media. MTU issues usually show fragmentation or packet-handling problems, not CRC corruption itself. CPU saturation does not create on-the-wire checksum corruption. In Nutanix troubleshooting, when CRC counters rise repeatedly, the correct operational response is to inspect and swap the cable or optics, verify switch-port health, and test the NIC path physically. So B is the strongest technical match.