New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Eccouncil 312-50 Exam - Topic 9 Question 99 Discussion

Actual exam question for Eccouncil's 312-50 exam
Question #: 99
Topic #: 9
[All 312-50 Questions]

A new wireless client is configured to join a 802.11 network. This client uses the same hardware and software as many of the other clients on the network. The client can see the network, but cannot connect. A wireless packet sniffer shows that the Wireless Access Point (WAP) is not responding to the association requests being sent by the wireless client. What is a possible source of this problem?

Show Suggested Answer Hide Answer
Suggested Answer: B

A Slow HTTP POST attack is a type of denial-of-service (DoS) attack that exploits the way web servers handle HTTP requests. The attacker sends a legitimate HTTP POST header to the web server, specifying a large amount of data to be sent in the request body. However, the attacker then sends the data very slowly, keeping the connection open and occupying the server's resources. The attacker can launch multiple such connections, exceeding the server's capacity to handle concurrent requests and preventing legitimate users from accessing the web server.

The attack duration D is given by the formula D = a * b, where a is the number of connections and b is the hold-up time per connection. The attacker intends to maximize D by manipulating a and b. The server can manage m connections per second, but any connections exceeding m will overwhelm the system. Therefore, the scenario that is most likely to result in the longest duration of server unavailability is the one where a > m and b is the largest. Among the four options, this is the case for option B, where a = 100, m = 90, and b = 15. In this scenario, D = 100 * 15 = 1500 seconds, which is the longest among the four options. Option A has a larger b, but a < m, so the server can handle the connections without being overwhelmed. Option C has a > m, but a smaller b, so the attack duration is shorter. Option D has a > m, but a smaller b and a smaller difference between a and m, so the attack duration is also shorter. Reference:

What is a Slow POST Attack & How to Prevent One? (Guide)

Mitigate Slow HTTP GET/POST Vulnerabilities in the Apache HTTP Server - Acunetix

What is a Slow Post DDoS Attack? | NETSCOUT


Contribute your Thoughts:

0/2000 characters
Sharika
3 months ago
Not sure about the MAC address thing, seems a bit off.
upvoted 0 times
...
Trina
3 months ago
Wait, the client can see the network but can't connect? That's weird.
upvoted 0 times
...
Ming
4 months ago
I think it's more likely a channel mismatch.
upvoted 0 times
...
Alyce
4 months ago
Definitely sounds like a DHCP problem to me.
upvoted 0 times
...
Tula
4 months ago
Could be the MAC address issue, WAP might be filtering.
upvoted 0 times
...
Elke
4 months ago
I feel like DHCP issues are usually more about getting an IP address after connecting, so I'm hesitant about option D being the cause.
upvoted 0 times
...
Annmarie
4 months ago
I practiced a question like this where the channel configuration was the issue, so option C could be worth considering.
upvoted 0 times
...
Gianna
5 months ago
I'm not entirely sure, but I think if the client can see the network, then option B might not be the right answer.
upvoted 0 times
...
Sherita
5 months ago
I remember something about MAC address filtering being a common issue, so maybe option A could be the problem here.
upvoted 0 times
...
Lavonda
5 months ago
I'm a bit confused by this one. If the client can see the network, then the SSID and channel seem to be correct. And if the hardware and software are the same as other working clients, that makes me doubt it's a configuration issue on the client side. I'll need to really think this through carefully.
upvoted 0 times
...
Paz
5 months ago
Okay, let's see here. The client hardware and software are the same as other working clients, so that rules out a compatibility issue. The WAP not responding to the association requests is the key clue. I'm going to go with option A - the WAP doesn't recognize the client's MAC address.
upvoted 0 times
...
Tabetha
5 months ago
Hmm, this is a tricky one. The fact that the client can see the network but can't connect makes me think it's not a simple issue like the SSID or channel. I'll need to really think through the possible causes and try to eliminate the less likely ones.
upvoted 0 times
...
Alease
5 months ago
This one seems pretty straightforward. I'm going to focus on the key details - the client can see the network but can't connect, and the packet sniffer shows the WAP isn't responding to the association requests. That points to a configuration issue on the WAP side, so I'll carefully consider the options.
upvoted 0 times
...
Carol
10 months ago
Hmm, maybe the client needs to try a channel-hopping dance routine to get the WAP's attention. Or perhaps they just need to switch to a wireless network that speaks their language. 'Cause you know, gotta keep that SSID on point, am I right?
upvoted 0 times
...
Mattie
10 months ago
This one's tricky, but I'm leaning towards the SSID being the culprit. If the client can't see the network's SSID, how's it gonna connect? Gotta make sure that's dialed in.
upvoted 0 times
Micaela
8 months ago
D) The wireless client is not configured to use DHCP
upvoted 0 times
...
Ardella
8 months ago
C) Client is configured for the wrong channel
upvoted 0 times
...
Jill
9 months ago
B) The client cannot see the SSID of the wireless network
upvoted 0 times
...
Meghan
9 months ago
A) The WAP does not recognize the client's MAC address
upvoted 0 times
...
...
Vincenza
10 months ago
Oof, no DHCP configuration? That's a rookie mistake. How's the client supposed to get an IP address without that? Better double-check that setting.
upvoted 0 times
...
Tamesha
10 months ago
Wait, the client can see the network but can't connect? That's a head-scratcher. Could it be a MAC address issue? The WAP might not be recognizing this client's MAC.
upvoted 0 times
Geraldine
9 months ago
C) Client is configured for the wrong channel
upvoted 0 times
...
Theron
9 months ago
B) The client cannot see the SSID of the wireless network
upvoted 0 times
...
Carmen
9 months ago
C) Client is configured for the wrong channel
upvoted 0 times
...
Tamala
9 months ago
B) The client cannot see the SSID of the wireless network
upvoted 0 times
...
Clemencia
9 months ago
A) The WAP does not recognize the client's MAC address
upvoted 0 times
...
Sean
10 months ago
A) The WAP does not recognize the client's MAC address
upvoted 0 times
...
...
Viola
10 months ago
Hmm, the WAP not responding to the association requests seems like a connectivity issue. I'm going to guess that the client is configured for the wrong channel. Gotta make sure that's in sync with the WAP!
upvoted 0 times
...
Rodolfo
11 months ago
But what if the client is configured for the wrong channel? That could also be causing the issue, right?
upvoted 0 times
...
Ty
11 months ago
I agree with Melda. If the WAP doesn't recognize the MAC address, it won't respond to the association requests.
upvoted 0 times
...
Melda
11 months ago
I think the possible source of the problem could be that the WAP does not recognize the client's MAC address.
upvoted 0 times
...

Save Cancel