Courseiva
Question 367 of 464
Network TroubleshootinghardMultiple ChoiceObjective-mapped

N10-009 Network Troubleshooting Practice Question

A network technician is troubleshooting connectivity between two branch offices connected by a site-to-site VPN. The VPN tunnel shows as active and up. Users at Branch A can ping the VPN gateway IP at Branch B successfully, but they cannot access any servers behind the firewall at Branch B. The firewall at Branch B is stateful and its logs show that traffic from Branch A is being dropped. What is the most likely cause?

⚠ Common exam trap

The N10-009 exam often tests the misconception that a 'green' tunnel status guarantees end-to-end application connectivity, but the trap here is that stateful firewalls require symmetric traffic flows, and candidates may incorrectly blame encryption mismatches or DNS when the tunnel itself is operational.

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

Asymmetric routing causing the stateful firewall to drop return traffic

The VPN tunnel is active and Branch A can ping the VPN gateway IP at Branch B, confirming that the tunnel itself and Layer 3 connectivity are functional. However, a stateful firewall tracks connection states based on source/destination IP and port; if traffic from Branch A enters the firewall on one interface but return traffic exits via a different path (asymmetric routing), the firewall sees the return packets as not belonging to any established session and drops them. This matches the log showing traffic being dropped despite the tunnel being 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.

  • Mismatched encryption algorithms

    Why it's wrong here

    Mismatched encryption algorithms prevent the successful establishment of a VPN tunnel during the Internet Key Exchange (IKE) phases. If the two VPN endpoints cannot agree on a common set of cryptographic parameters, such as the encryption algorithm (e.g., AES-256 vs. 3DES) or hashing function (e.g., SHA-256 vs. MD5), the security association (SA) negotiation will fail. Since the problem implies that traffic is attempting to flow and being dropped by a firewall, the VPN tunnel must have already been established, making mismatched encryption algorithms an unlikely cause.

    When this WOULD be correct

    In a scenario where the VPN tunnel fails to establish or shows as down, mismatched encryption algorithms (e.g., AES vs. 3DES) are a common cause, especially when both sides have different security association proposals.

  • Asymmetric routing causing the stateful firewall to drop return traffic

    Why this is correct

    The stateful firewall expects to see both directions of a connection. If traffic from Branch A enters one firewall interface but the return traffic leaves via a different path, the firewall sees the return packet as unsolicited and drops it.

  • Incorrect DNS configuration

    Why it's wrong here

    Incorrect DNS configuration primarily affects name resolution, preventing devices from translating human-readable domain names into numerical IP addresses. If DNS were the issue, users would be unable to reach resources by hostname, but direct IP address communication would still function. Since the problem describes traffic being dropped by a firewall and implies that IP-based connectivity might be working (e.g., ping by IP to the gateway works), DNS is not the root cause of the firewall actively dropping packets that have a valid destination IP address.

    When this WOULD be correct

    A network technician is troubleshooting why users at a remote site cannot access internal servers by hostname, but can access them by IP address. The VPN tunnel is up and ping to the servers' IPs works. In this scenario, incorrect DNS configuration would be the likely cause.

  • MTU mismatch causing fragmentation issues

    Why it's wrong here

    An MTU (Maximum Transmission Unit) mismatch occurs when the largest packet size allowed on a network path varies, leading to fragmentation or dropping of larger packets if the 'Don't Fragment' bit is set. While MTU issues can cause packet loss, slow performance, or timeouts for specific applications, a stateful firewall typically drops traffic due to policy violations or a mismatch in its connection state table. The firewall would log a drop based on stateful inspection rules, not directly because of an MTU-related fragmentation problem, making this an indirect or unlikely cause for a firewall-specific drop.

    When this WOULD be correct

    In a scenario where users can establish a VPN connection but experience slow or intermittent access to applications, and large packets fail while small ones succeed, MTU mismatch would be the correct answer.

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.

Asymmetric routing causing the stateful firewall to drop return trafficCorrect answer

Why this is correct

The stateful firewall expects to see both directions of a connection. If traffic from Branch A enters one firewall interface but the return traffic leaves via a different path, the firewall sees the return packet as unsolicited and drops it.

Mismatched encryption algorithmsWrong answer — click to see why

Why this is wrong here

Mismatched encryption algorithms would prevent the VPN tunnel from establishing or cause it to fail, but the question states the tunnel is active and up, and pings to the VPN gateway succeed, indicating encryption is working correctly.

★ When this WOULD be the correct answer

In a scenario where the VPN tunnel fails to establish or shows as down, mismatched encryption algorithms (e.g., AES vs. 3DES) are a common cause, especially when both sides have different security association proposals.

Why candidates choose this

Candidates often associate VPN issues with encryption mismatches, overlooking that the tunnel is up and basic connectivity exists, leading them to incorrectly choose this option.

Incorrect DNS configurationWrong answer — click to see why

Why this is wrong here

Incorrect DNS configuration would prevent name resolution, but the issue is that traffic is being dropped by the stateful firewall, not that servers cannot be reached by name. Users can ping the VPN gateway IP successfully, indicating basic connectivity and routing are intact.

★ When this WOULD be the correct answer

A network technician is troubleshooting why users at a remote site cannot access internal servers by hostname, but can access them by IP address. The VPN tunnel is up and ping to the servers' IPs works. In this scenario, incorrect DNS configuration would be the likely cause.

Why candidates choose this

Candidates may confuse symptoms of connectivity issues with DNS problems, assuming that if servers cannot be accessed, it must be a name resolution failure, especially when ping to IP works but application access fails.

MTU mismatch causing fragmentation issuesWrong answer — click to see why

Why this is wrong here

The VPN tunnel is active and pings to the gateway succeed, indicating the link is functional. MTU mismatch typically causes packet fragmentation or loss, not a stateful firewall dropping traffic due to asymmetric routing.

★ When this WOULD be the correct answer

In a scenario where users can establish a VPN connection but experience slow or intermittent access to applications, and large packets fail while small ones succeed, MTU mismatch would be the correct answer.

Why candidates choose this

Candidates may confuse general connectivity issues with MTU problems, especially when symptoms involve packet loss or performance degradation, but here the specific symptom is firewall drops due to asymmetric routing.

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?”

Quick reference

Asymmetric Encryption Algorithm Comparison

AlgorithmKey ExchangeSignaturesEquivalent Security KeyNotes
RSA-3072YesYes128-bitWidely deployed; slow for bulk data
ECDSA P-256NoYes128-bitFast signatures; standard TLS certs
ECDH / ECDHEYesNo128-bitPerfect forward secrecy in TLS 1.3
DH / DHEYesNo128-bit (3072-bit key)Replaced by ECDHE in modern TLS
Ed25519NoYes~128-bitSSH keys, modern PKI

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.