Courseiva
Network ImplementationhardMultiple ChoiceObjective-mapped

N10-009 Network Implementation Practice Question

A network engineer has successfully established an IPsec site-to-site VPN tunnel between a branch office (10.0.1.0/24) and the main office (192.168.1.0/24). The tunnel status shows as active, and both sides can ping each other's tunnel interface IP addresses. However, users at the branch office cannot ping the main office server at 192.168.1.10, and the main office cannot ping the branch office server at 10.0.1.10. The firewall rules on both sides permit IPsec traffic and all internal traffic. What should the engineer check NEXT?

⚠ Common exam trap

The N10-009 exam often tests the distinction between tunnel reachability (pinging the tunnel interface IP) and subnet reachability (pinging hosts behind the tunnel), trapping candidates who assume a working tunnel automatically means all traffic flows correctly, when in fact routing for the remote LANs must be explicitly configured.

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

Verify routing entries on both routers to ensure the remote internal subnets are reachable via the tunnel.

The tunnel is active and both sides can ping each other's tunnel interface IPs, confirming that IPsec phase 1 and phase 2 are established and the tunnel itself is functional. However, users cannot reach the remote internal subnets (10.0.1.0/24 and 192.168.1.0/24), which indicates a routing problem: the routers likely lack routes for those remote subnets pointing to the tunnel interface. Without proper routing entries, traffic destined for the remote LAN is sent out the wrong interface or dropped, even though the tunnel is up.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Verify routing entries on both routers to ensure the remote internal subnets are reachable via the tunnel.

    Why this is correct

    Both routers need to have routes pointing to the remote internal subnets (e.g., 192.168.1.0/24 and 10.0.1.0/24) with the tunnel interface as the next hop. Without these routes, traffic from internal hosts will not be directed into the tunnel.

  • Check the IPsec security associations for encryption algorithm mismatch.

    Why it's wrong here

    An encryption algorithm mismatch, or any other mismatch in IPsec Security Association (SA) parameters (like hashing algorithms or Diffie-Hellman groups), would prevent the IPSec tunnel from successfully establishing in the first place. Since the question states the tunnel has been "successfully established," it confirms that all IKE Phase 1 and Phase 2 parameters, including encryption algorithms, have been correctly negotiated and agreed upon by both VPN peers. Therefore, checking for such a mismatch is irrelevant to a problem where the tunnel is up but traffic isn't flowing.

    When this WOULD be correct

    In a scenario where the IPsec tunnel status shows as active but pings between tunnel interfaces fail, or the tunnel fails to establish, checking for encryption algorithm mismatch would be the next step.

  • Disable the firewall on the internal interfaces temporarily.

    Why it's wrong here

    Disabling firewalls on internal interfaces is a significant security risk and an inappropriate troubleshooting step when the VPN tunnel itself is established. If the tunnel is up, it implies that necessary firewall rules for IPSec (e.g., UDP 500, UDP 4500, ESP protocol 50, AH protocol 51) are already permitting the control plane traffic. The issue described, where the tunnel is up but traffic isn't flowing, points to a routing problem, not a firewall blocking *internal* traffic that should be encapsulated by the VPN.

    When this WOULD be correct

    In a scenario where the IPsec tunnel is up, pings to tunnel interfaces succeed, but internal traffic fails, and the firewall logs show dropped packets for internal traffic. The engineer has verified routing and IPsec SAs, and suspects a firewall rule blocking internal traffic between the subnets. Temporarily disabling the firewall would isolate the issue.

  • Regenerate the pre-shared key on both sides.

    Why it's wrong here

    If the IPSec site-to-site VPN tunnel has been successfully established, it means the pre-shared key (PSK) was correctly configured and used during the Internet Key Exchange (IKE) Phase 1 for mutual authentication. Regenerating the PSK would disrupt the active tunnel and require re-authentication, which is counterproductive when the problem lies elsewhere, specifically with traffic not traversing the *established* tunnel. The PSK's role is solely for initial peer authentication, not for ongoing data plane issues after tunnel establishment.

    When this WOULD be correct

    If the tunnel status showed as down or the ping to the tunnel interface IPs failed, and logs indicated authentication failures, then regenerating the pre-shared key on both sides would be the next step to resolve a key mismatch.

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.

Verify routing entries on both routers to ensure the remote internal subnets are reachable via the tunnel.Correct answer

Why this is correct

Both routers need to have routes pointing to the remote internal subnets (e.g., 192.168.1.0/24 and 10.0.1.0/24) with the tunnel interface as the next hop. Without these routes, traffic from internal hosts will not be directed into the tunnel.

Check the IPsec security associations for encryption algorithm mismatch.Wrong answer — click to see why

Why this is wrong here

The tunnel is active and both sides can ping each other's tunnel interface IPs, indicating IPsec SAs are correctly established and encryption algorithms match. The issue is that internal subnets are not reachable, pointing to a routing problem, not an SA mismatch.

★ When this WOULD be the correct answer

In a scenario where the IPsec tunnel status shows as active but pings between tunnel interfaces fail, or the tunnel fails to establish, checking for encryption algorithm mismatch would be the next step.

Why candidates choose this

Candidates often default to checking encryption settings when IPsec issues arise, overlooking that a working tunnel with pingable interfaces already confirms correct SA parameters.

Disable the firewall on the internal interfaces temporarily.Wrong answer — click to see why

Why this is wrong here

The firewall rules already permit all internal traffic and IPsec traffic, so disabling the firewall is unnecessary and would not resolve a routing issue. The problem is that the remote subnets are not reachable via the tunnel, which is a routing problem, not a firewall problem.

★ When this WOULD be the correct answer

In a scenario where the IPsec tunnel is up, pings to tunnel interfaces succeed, but internal traffic fails, and the firewall logs show dropped packets for internal traffic. The engineer has verified routing and IPsec SAs, and suspects a firewall rule blocking internal traffic between the subnets. Temporarily disabling the firewall would isolate the issue.

Why candidates choose this

Candidates may think that since the tunnel is up but traffic fails, a firewall might be blocking internal traffic despite the rules, and disabling it is a quick test. They overlook that routing is the more likely cause when tunnel interfaces are reachable but internal subnets are not.

Regenerate the pre-shared key on both sides.Wrong answer — click to see why

Why this is wrong here

The tunnel is active and both sides can ping each other's tunnel interface IPs, indicating IPsec SAs are correctly established. Regenerating the pre-shared key would disrupt the established tunnel without addressing the routing issue that prevents internal subnet reachability.

★ When this WOULD be the correct answer

If the tunnel status showed as down or the ping to the tunnel interface IPs failed, and logs indicated authentication failures, then regenerating the pre-shared key on both sides would be the next step to resolve a key mismatch.

Why candidates choose this

Candidates may think that a pre-shared key issue could cause connectivity problems, but since the tunnel is active and tunnel interfaces are reachable, the key is already correct.

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

192.168.1.0 /24 256 addresses (254 usable) 192.168.1.0 /25 Subnet A 128 addr (126 usable) 192.168.1.128 /25 Subnet B 128 addr (126 usable) Borrowing 1 bit from host portion creates 2 subnets (/25)

Quick reference

VPN Protocol Comparison

ProtocolPortEncryptionAuthenticationUse Case
IKEv2 / IPsecUDP 500 / 4500AES-256Certificates / PSKSite-to-site & remote access
SSL / TLS VPNTCP 443TLS 1.3Certificates / MFAClientless remote access
L2TP / IPsecUDP 1701AES (IPsec)PSK / CertificatesLegacy remote access
WireGuardUDP 51820ChaCha20Public keysModern high-performance VPN
PPTPTCP 1723MPPE (weak)MS-CHAPv2Legacy — avoid in production

PPTP is considered insecure. IKEv2/IPsec and SSL VPN are the current recommended options.

About these practice questions

This N10-009 question is part of Courseiva's 464-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 →

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.