Courseiva
Network TroubleshootingmediumMultiple ChoiceObjective-mapped

N10-009 Network Troubleshooting Practice Question

A technician is troubleshooting a user's computer that cannot access any network resources. The technician runs ipconfig and sees an IP address of 169.254.18.33 with a subnet mask of 255.255.0.0. The computer is connected to a switch port configured for VLAN 10. The DHCP server is located in a different subnet (VLAN 200) and is reachable via a router. The technician confirms that the switch port is in the correct VLAN and that the cabling is good. Which of the following is the MOST likely cause of the issue?

⚠ Common exam trap

The trap here is that candidates see a 169.254.x.x address and immediately blame a faulty NIC or DHCP server issue, overlooking the need for a DHCP relay when the server is on a different subnet.

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 router does not have a DHCP relay (ip helper-address) configured

The 169.254.x.x address is an Automatic Private IP Addressing (APIPA) address, assigned when a DHCP client fails to receive a lease. Since the DHCP server is on VLAN 200 and the client is on VLAN 10, a DHCP relay (ip helper-address) must be configured on the router interface facing VLAN 10 to forward DHCP broadcast requests as unicast to the DHCP server. Without this relay, the DHCP server never receives the client's discover message, causing the client to self-assign an APIPA address.

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 not authorized in Active Directory

    Why it's wrong here

    DHCP server authorization in Active Directory is a security feature in Windows environments designed to prevent unauthorized DHCP servers from issuing IP addresses on a domain network. If a DHCP server is not authorized, it will typically cease to issue leases or be ignored by domain clients, but it would not inherently prevent a client from attempting DHCP and subsequently falling back to APIPA due to a lack of *any* DHCP response. The core problem here is the DHCP server's inability to receive the client's request across subnets, not its authorization status.

    When this WOULD be correct

    This would be correct in a scenario where DHCP clients are on the same subnet as the DHCP server, the server is running Windows, and clients receive 'No DHCP server available' errors despite the server being operational. In that case, unauthorized DHCP server in AD would prevent it from leasing addresses.

  • The router does not have a DHCP relay (ip helper-address) configured

    Why this is correct

    Without a DHCP relay configured on the router, DHCP broadcast requests from clients cannot traverse different IP subnets or VLANs to reach a DHCP server located in another segment. The `ip helper-address` command (or equivalent) is essential for the router to convert these broadcasts into unicast packets and forward them to the specified DHCP server. Consequently, the client's DHCP discovery request never reaches the server, leading to a timeout and the assignment of an Automatic Private IP Addressing (APIPA) address.

  • The computer's NIC is faulty

    Why it's wrong here

    A faulty Network Interface Card (NIC) typically manifests as a complete lack of link connectivity, intermittent network access, or erratic packet loss. The consistent acquisition of an APIPA address, however, indicates that the NIC is functional enough to establish a physical link and attempt DHCP discovery. This behavior suggests the NIC itself is working correctly at Layer 1 and Layer 2, but the DHCP process is failing at a higher layer or due to network configuration issues.

    When this WOULD be correct

    A technician finds a computer with no network connectivity and no IP address (or a 169.254.x.x address) after replacing the NIC. The switch port shows link but the computer cannot obtain an IP address even after static configuration fails. In that scenario, a faulty NIC would be the likely cause.

  • The switch port is in the wrong VLAN

    Why it's wrong here

    If the switch port were in the wrong VLAN, the client's DHCP requests would be broadcast into an incorrect network segment, preventing them from reaching the intended DHCP server. While this would certainly result in no network access and potentially an APIPA address, the problem statement indicates the technician already confirmed the port is in the correct VLAN. Therefore, the issue lies not with the client's initial VLAN assignment, but with the DHCP server's reachability across VLAN boundaries.

    When this WOULD be correct

    A technician sees a computer with an IP address from a different subnet than expected (e.g., 192.168.1.x instead of 10.0.0.x) and the switch port is configured for a different VLAN than the one the computer is physically connected to. In that case, the wrong VLAN assignment would cause the incorrect IP address.

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 N10-009 exam frequently reuses these exact scenarios with slightly different constraints.

The router does not have a DHCP relay (ip helper-address) configuredCorrect answer

Why this is correct

Without a DHCP relay configured on the router, DHCP broadcast requests from clients cannot traverse different IP subnets or VLANs to reach a DHCP server located in another segment. The `ip helper-address` command (or equivalent) is essential for the router to convert these broadcasts into unicast packets and forward them to the specified DHCP server. Consequently, the client's DHCP discovery request never reaches the server, leading to a timeout and the assignment of an Automatic Private IP Addressing (APIPA) address.

The DHCP server is not authorized in Active DirectoryWrong answer — click to see why

Why this is wrong here

The computer received an APIPA address (169.254.x.x), indicating it failed to get a DHCP lease. DHCP server authorization in Active Directory is irrelevant because the issue is that DHCP requests from VLAN 10 are not reaching the DHCP server in VLAN 200 due to missing relay configuration.

★ When this WOULD be the correct answer

This would be correct in a scenario where DHCP clients are on the same subnet as the DHCP server, the server is running Windows, and clients receive 'No DHCP server available' errors despite the server being operational. In that case, unauthorized DHCP server in AD would prevent it from leasing addresses.

Why candidates choose this

Candidates may confuse DHCP server authorization with general DHCP availability issues, especially if they have studied Windows DHCP server deployment and know that unauthorized servers do not respond to requests, but they overlook the cross-subnet relay requirement here.

The computer's NIC is faultyWrong answer — click to see why

Why this is wrong here

A faulty NIC would typically cause no link or intermittent connectivity, but the computer obtained an APIPA address (169.254.x.x), indicating the NIC is functional and can communicate on the local link. The issue is that DHCP requests are not reaching the DHCP server across VLANs.

★ When this WOULD be the correct answer

A technician finds a computer with no network connectivity and no IP address (or a 169.254.x.x address) after replacing the NIC. The switch port shows link but the computer cannot obtain an IP address even after static configuration fails. In that scenario, a faulty NIC would be the likely cause.

Why candidates choose this

Candidates may think that any network issue could be due to hardware failure, especially when connectivity is completely absent. The APIPA address might be misinterpreted as a symptom of a faulty NIC rather than a DHCP relay problem.

The switch port is in the wrong VLANWrong answer — click to see why

Why this is wrong here

The question states the technician confirmed the switch port is in the correct VLAN (VLAN 10), so the port is not in the wrong VLAN. The IP address 169.254.x.x indicates APIPA, which occurs when DHCP fails, not due to VLAN misconfiguration.

★ When this WOULD be the correct answer

A technician sees a computer with an IP address from a different subnet than expected (e.g., 192.168.1.x instead of 10.0.0.x) and the switch port is configured for a different VLAN than the one the computer is physically connected to. In that case, the wrong VLAN assignment would cause the incorrect IP address.

Why candidates choose this

Candidates may assume that any network connectivity issue with a VLAN configuration is due to the port being in the wrong VLAN, especially when the problem involves DHCP and subnet mismatches.

Analysis generated from the official N10-009blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Visual reference

Client DHCP Server 1 Discover (broadcast) 2 Offer (IP: 192.168.1.10) 3 Request (I accept) 4 Acknowledge (lease confirmed) DORA — the four-step DHCP lease process

Go deeper

Related to this question

About these practice questions

One of 464 original N10-009 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This N10-009 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 N10-009 exam.