220-1101 Question 296
Single answerNetwork interface cardA technician installs a new PCIe network interface card (NIC) in a desktop because the onboard Ethernet port has failed. The link light on the new NIC is on, and the switch port shows a physical connection. However, the user cannot reach any network resources. In Windows, the adapter appears in Device Manager with no warning icons, but running ipconfig shows an APIPA address of 169.254.x.x. Which action should the technician take FIRST to restore connectivity?
- A
Replace the Ethernet cable because a 169.254.x.x address indicates a bad cable
- B
Configure a static IP address, subnet mask, and default gateway on the NIC
- C
Verify that the DHCP server is reachable and that the NIC is set to obtain an IP address automatically
- D
Reinstall the NIC because APIPA indicates the PCIe card is incompatible with the motherboard
Show answer and explanation
Correct answer: C
Explanation
This question tests practical NIC troubleshooting. The presence of link lights and a recognized adapter indicates that the NIC is installed and communicating at the physical layer. The key clue is the 169.254.x.x APIPA address shown by ipconfig. Microsoft documents that Windows uses Automatic Private IP Addressing when a DHCP client cannot obtain a lease. Best practice is to verify the adapter's TCP/IP settings, confirm it is configured to obtain an IP address automatically if DHCP is expected, and then check DHCP availability and network path issues such as VLAN assignment, switch configuration, or DHCP server reachability. Jumping directly to replacing the NIC, replacing the cable, or assigning a static IP skips the most likely root cause and does not follow an efficient troubleshooting process.
- A. Incorrect.
Incorrect. A bad cable can prevent connectivity, but in this scenario the NIC link light is on and the switch detects a physical connection, which strongly suggests Layer 1 is working. A 169.254.x.x APIPA address in Windows typically means the system did not receive a lease from a DHCP server, not that the cable is necessarily faulty.
- B. Incorrect.
Incorrect. Assigning a static IP might restore connectivity only if the network is designed for static addressing and the technician knows the correct settings. However, this is not the best first step. The immediate issue suggested by the APIPA address is failure to obtain a DHCP lease, so the technician should first verify DHCP reachability and adapter configuration before manually overriding settings.
- C. Correct.
Correct. In Windows, an APIPA address in the 169.254.0.0/16 range is self-assigned when the client cannot contact a DHCP server or is not configured to use DHCP. Because the NIC has link and is recognized by the OS, the next logical troubleshooting step is to confirm that the adapter is configured for automatic addressing and that DHCP is available on the network path.
- D. Incorrect.
Incorrect. Device Manager shows the adapter functioning normally, and the physical link is established, so there is no evidence that the PCIe NIC is incompatible or defective. APIPA points to an addressing issue, most commonly DHCP communication failure, rather than a hardware compatibility problem.