Courseiva
Network SecurityhardMultiple ChoiceObjective-mapped

N10-009 Network Security Practice Question

A company's public web server is experiencing a flood of TCP SYN packets from multiple external IP addresses. The server's connection table is full, causing new legitimate connections to be dropped. Which of the following mitigation techniques should be implemented to protect the server while still allowing legitimate traffic?

⚠ Common exam trap

The N10-009 exam often tests the misconception that increasing the TCP backlog (Option B) is a viable defense against SYN floods, but candidates must recognize that backlog tuning only delays exhaustion, whereas SYN cookies provide a stateless, scalable solution.

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

Implement SYN cookies on the server.

SYN cookies allow the server to avoid storing connection state in the TCP backlog until the three-way handshake completes. When the SYN flood fills the connection table, the server encodes the initial sequence number (ISN) with cryptographic information about the connection, enabling it to verify the ACK from a legitimate client without consuming table entries. This technique preserves resources for legitimate traffic while dropping spoofed or incomplete handshakes.

Answer analysis

Option-by-option breakdown

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

  • Implement SYN cookies on the server.

    Why this is correct

    SYN cookies are a highly effective defense against SYN floods because they allow the server to defer allocating memory for a new connection until the three-way handshake is fully completed. Instead of storing connection state, the server encodes all necessary information, such as client IP, port, and sequence numbers, into the initial SYN-ACK packet's sequence number. Only upon receiving a valid final ACK, which includes the correct cookie, does the server reconstruct the connection state and allocate resources, effectively preventing its connection table from being exhausted by spoofed or incomplete SYN requests.

  • Increase the server's TCP connection backlog.

    Why it's wrong here

    Increasing the server's TCP connection backlog merely expands the queue for half-open connections awaiting the final ACK. While this might slightly delay the point of exhaustion, it does not fundamentally alter the server's vulnerability to a sustained SYN flood. The server still dedicates finite memory and processing resources to each entry in that backlog, meaning a sufficiently large or prolonged attack will inevitably fill even an expanded queue, leading to service degradation.

    When this WOULD be correct

    This option would be correct in a scenario where the server is dropping legitimate connections due to a legitimate traffic spike (e.g., flash crowd) and the backlog is set too low, causing new connections to be rejected even though the server has capacity to handle them.

  • Enable bogon filtering on the perimeter firewall.

    Why it's wrong here

    Bogon filtering on a perimeter firewall blocks traffic originating from IP addresses that are reserved for private networks or are currently unallocated on the internet. While some SYN flood attacks utilize spoofed source IP addresses, many of these spoofed addresses are not bogons, rendering this defense largely ineffective against a sophisticated SYN flood. This technique primarily aims to prevent traffic from clearly invalid sources, not to mitigate resource exhaustion from a high volume of seemingly valid, yet malicious, connection attempts.

    When this WOULD be correct

    A company is receiving traffic from IP addresses that are known to be unallocated or reserved (e.g., private IPs on the internet). Enabling bogon filtering on the perimeter firewall would block this invalid traffic and protect the network.

  • Deploy an intrusion prevention system (IPS) with signature detection.

    Why it's wrong here

    Deploying an Intrusion Prevention System (IPS) with signature detection can identify and potentially block known SYN flood patterns. However, an IPS typically operates at a higher layer and requires more computational resources per packet than simpler network devices or server-side mitigations. In the face of a high-volume SYN flood, the IPS itself can become a bottleneck, struggling to process the immense traffic volume, leading to performance issues or even becoming overwhelmed before the attack traffic reaches the server.

    When this WOULD be correct

    An IPS with signature detection would be correct for blocking application-layer attacks, such as SQL injection or cross-site scripting, where the attack payload is in the data stream and can be matched against signatures.

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.

Implement SYN cookies on the server.Correct answer

Why this is correct

SYN cookies are a highly effective defense against SYN floods because they allow the server to defer allocating memory for a new connection until the three-way handshake is fully completed. Instead of storing connection state, the server encodes all necessary information, such as client IP, port, and sequence numbers, into the initial SYN-ACK packet's sequence number. Only upon receiving a valid final ACK, which includes the correct cookie, does the server reconstruct the connection state and allocate resources, effectively preventing its connection table from being exhausted by spoofed or incomplete SYN requests.

Increase the server's TCP connection backlog.Wrong answer — click to see why

Why this is wrong here

Increasing the TCP connection backlog only raises the limit of pending connections in the queue, but a SYN flood fills the connection table regardless of backlog size, so the server still exhausts resources and drops legitimate connections.

★ When this WOULD be the correct answer

This option would be correct in a scenario where the server is dropping legitimate connections due to a legitimate traffic spike (e.g., flash crowd) and the backlog is set too low, causing new connections to be rejected even though the server has capacity to handle them.

Why candidates choose this

Candidates may think that a larger backlog can absorb more SYN packets, misunderstanding that SYN floods exhaust the connection table via half-open connections, not by exceeding the backlog limit.

Enable bogon filtering on the perimeter firewall.Wrong answer — click to see why

Why this is wrong here

Bogon filtering blocks traffic from invalid or unallocated IP addresses, but the SYN flood is coming from multiple external IPs that may be legitimate (spoofed or real). It does not prevent the connection table from filling up due to half-open connections.

★ When this WOULD be the correct answer

A company is receiving traffic from IP addresses that are known to be unallocated or reserved (e.g., private IPs on the internet). Enabling bogon filtering on the perimeter firewall would block this invalid traffic and protect the network.

Why candidates choose this

Candidates may think that blocking 'bad' IPs (bogons) is a general defense against any flood, but SYN floods often use spoofed or real distributed IPs that are not necessarily bogons.

Deploy an intrusion prevention system (IPS) with signature detection.Wrong answer — click to see why

Why this is wrong here

An IPS with signature detection can block known attack patterns, but it cannot prevent the connection table from filling up during a SYN flood because the attack traffic still reaches the server and consumes resources before the IPS can act.

★ When this WOULD be the correct answer

An IPS with signature detection would be correct for blocking application-layer attacks, such as SQL injection or cross-site scripting, where the attack payload is in the data stream and can be matched against signatures.

Why candidates choose this

Candidates may think an IPS can stop any type of attack, including SYN floods, because it is a general-purpose security device, but they overlook that SYN floods exploit TCP handshake mechanics that require endpoint-level mitigation.

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 Server SYN (seq=100) SYN-ACK (seq=200, ack=101) ACK (ack=201) Connection established — data transfer begins

About these practice questions

Courseiva writes every N10-009 question from scratch — 464 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 →

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.