220-1101 Hardware and Network Troubleshooting Practice Question
A user reports that their wired desktop computer intermittently loses network connectivity. The technician checks the Ethernet cable and observes that it is not securely clicked into the NIC port. The cable appears undamaged and the connector is intact. Which of the following is the MOST likely cause of the intermittent connectivity?
⚠ Common exam trap
The trap here is that candidates may overthink the issue and select a higher-layer problem (like DHCP or IP addressing) when the physical layer symptom (visibly loose cable) is the obvious and correct answer.
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
✓
Loose cable connection
The technician observed that the Ethernet cable is not securely clicked into the NIC port. A loose physical connection at the RJ45 connector can cause intermittent link drops because the electrical contacts may momentarily lose continuity, triggering a link flap. This is the most direct cause given the cable and connector appear undamaged.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Faulty switch port
Why it's wrong here
While a faulty switch port can also cause sporadic connectivity, it is a less immediate hypothesis here because the technician has already observed that the cable is not securely clicked into place. A defective switch port typically shows other signs, such as the port LED staying off or amber even with a known-good cable connected, or errors on other devices using that same port. The correct troubleshooting order is to address the obvious physical issue first; only if the problem continues after reseating the cable should the switch port be tested with a different port or a known-good cable.
When this WOULD be correct
A faulty switch port would be correct if the cable is securely connected and undamaged, but the port's link light is off or erratic, and other devices on the same switch experience similar issues.
- ✗
Incorrect IP address
Why it's wrong here
An incorrect IP address on a static configuration would cause either complete absence of network connectivity or consistent failure to communicate with the subnet gateway, not intermittent drops. Dynamic IP problems usually appear at boot or during lease renewal, and result in APIPA (169.254.x.x) addressing or a persistent 'no network access' state. Because the NIC can still pass traffic between link flaps, the IP stack is functioning at Layer 3; the physical-layer symptom points away from IP misconfiguration.
When this WOULD be correct
A user reports that a wired desktop cannot connect to the network at all, but other devices on the same switch work fine. The technician checks the IP configuration and finds a static IP set to a different subnet. In this scenario, incorrect IP address is the cause.
- ✓
Loose cable connection
Why this is correct
A loose cable is the most direct physical-layer cause of intermittent network drops. When the RJ45 connector is not fully latched, vibration or movement can momentarily break contact between the cable pins and the NIC port, causing the link to flap. This produces symptoms exactly like those described: connectivity comes and goes, often unnoticed by the user until the cable is touched. The technician should first reseat the cable until it clicks firmly and verify the link LED remains stable.
- ✗
DHCP server issue
Why it's wrong here
A DHCP server issue would affect the assignment or renewal of an IP address, typically producing a total loss of connectivity or a fallback to APIPA addressing until the server responds. Once a client already holds a valid lease, DHCP has no direct influence on the physical link state; intermittent drops caused by a loose cable occur at Layer 1 and do not correlate with DHCP timing. The visible loose connector provides a clear physical explanation, whereas a DHCP failure would not cause the link LED to blink or the cable to be unseated.
When this WOULD be correct
A user reports that their computer cannot connect to the network after a power outage. Other devices on the same subnet are working. The technician checks the cable and finds it securely connected. In this scenario, a DHCP server issue (e.g., server not responding after reboot) would be the most likely cause.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 220-1101 exam frequently reuses these exact scenarios with slightly different constraints.
✓Loose cable connectionCorrect answer▾
Why this is correct
A loose cable is the most direct physical-layer cause of intermittent network drops. When the RJ45 connector is not fully latched, vibration or movement can momentarily break contact between the cable pins and the NIC port, causing the link to flap. This produces symptoms exactly like those described: connectivity comes and goes, often unnoticed by the user until the cable is touched. The technician should first reseat the cable until it clicks firmly and verify the link LED remains stable.
✗Faulty switch portWrong answer — click to see why▾
Why this is wrong here
The technician observed the cable is not securely clicked into the NIC port, indicating a physical connection issue. A faulty switch port would typically cause persistent or no connectivity, not intermittent loss tied to a loose cable.
★ When this WOULD be the correct answer
A faulty switch port would be correct if the cable is securely connected and undamaged, but the port's link light is off or erratic, and other devices on the same switch experience similar issues.
Why candidates choose this
Candidates may assume intermittent connectivity is often due to hardware failure at the switch, especially if they overlook the physical inspection finding of a loose cable.
✗Incorrect IP addressWrong answer — click to see why▾
Why this is wrong here
The user reports intermittent connectivity with a loose cable connection observed; an incorrect IP address typically causes persistent connectivity failure, not intermittent loss, and would not be resolved by reseating the cable.
★ When this WOULD be the correct answer
A user reports that a wired desktop cannot connect to the network at all, but other devices on the same switch work fine. The technician checks the IP configuration and finds a static IP set to a different subnet. In this scenario, incorrect IP address is the cause.
Why candidates choose this
Candidates may confuse symptoms of IP misconfiguration (e.g., no connectivity) with intermittent issues, or they may assume that any network problem is IP-related without considering physical layer causes.
✗DHCP server issueWrong answer — click to see why▾
Why this is wrong here
The technician already observed that the cable is not securely clicked into the NIC port, which directly explains the intermittent connectivity. A DHCP server issue would typically cause complete loss of IP configuration, not intermittent connectivity tied to a physical cable problem.
★ When this WOULD be the correct answer
A user reports that their computer cannot connect to the network after a power outage. Other devices on the same subnet are working. The technician checks the cable and finds it securely connected. In this scenario, a DHCP server issue (e.g., server not responding after reboot) would be the most likely cause.
Why candidates choose this
Candidates may associate intermittent connectivity with DHCP lease renewal failures or server unavailability, overlooking the physical evidence provided in the question.
Analysis generated from the official 220-1101blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
Learn chapter
Troubleshoot: Wireless Connectivity Issues
Key term
Registered Jack Function 45
An RJ45 connector is the clear plastic plug at the end of an Ethernet cable that connects computers, routers, and switches to form a wired network.
Key term
Local Connector
A local connector is a cable or port used to link a device like a computer to a nearby peripheral or network within the same immediate area.
About these practice questions
This 220-1101 question is part of Courseiva's 896-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.