220-1101 Networking Practice Question
A user moves their laptop from a conference room to their office and connects the Ethernet cable. The laptop shows a network connection with an IP address of 169.254.22.115 and a subnet mask of 255.255.0.0. The user cannot access the internet or any network resources. Which of the following is the MOST likely cause?
⚠ Common exam trap
The trap here is that candidates see a 'valid' IP address and subnet mask and assume the issue is DNS or a faulty NIC, but the 169.254.x.x range is a clear indicator of DHCP failure, not a configuration or hardware problem.
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 DHCP server is unreachable or failed to assign an IP address
The IP address 169.254.22.115 with a subnet mask of 255.255.0.0 is an Automatic Private IP Addressing (APIPA) address, which Windows assigns when a DHCP server is unreachable or fails to respond. Since the user moved the laptop and connected via Ethernet, the most likely cause is that the DHCP server did not assign a valid IP address, leaving the device with a link-local address that cannot route to the internet or network resources.
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 DHCP server is unreachable or failed to assign an IP address
Why this is correct
The 169.254.x.x address with a 255.255.0.0 mask is an APIPA self-assigned address, generated when the client's DHCP discover broadcasts receive no offer. This indicates the DHCP server was unreachable or failed to lease an address.
- ✗
The subnet mask is incorrect
Why it's wrong here
The 255.255.0.0 mask is the standard APIPA mask paired with 169.254.x.x, so it is correct for that self-assigned address; the real fault is DHCP not responding. It is tempting because incorrect masks do break connectivity, and a wrong mask would be the correct diagnosis when a valid DHCP address cannot reach its gateway.
- ✗
The network interface card is faulty
Why it's wrong here
A faulty NIC would not produce a stable 169.254.22.115 APIPA address with a working link; APIPA specifically signals that DHCP did not respond. It is tempting because hardware faults also cause connectivity loss, and a failed NIC would be the correct diagnosis when no link or address appears at all.
- ✗
The DNS server address is misconfigured
Why it's wrong here
The 169.254.x.x address is an APIPA self-assigned address indicating DHCP failure, not DNS misconfiguration; DNS problems leave a valid DHCP-assigned address intact. It is tempting because DNS faults also cause name-resolution failures, and misconfigured DNS would be the correct diagnosis when a host holds a valid IP but cannot resolve names.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every 220-1101 question from scratch — 896 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1101 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1101 exam.