220-1201 Practice Question: A technician is deploying a wireless network in a…

Answer analysis

Option-by-option breakdown

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

• ✗

  Enable WPA2-PSK with AES encryption.

  Why it's wrong here

  WPA2-PSK with AES encryption provides robust security for wireless networks by encrypting data and requiring a pre-shared key for authentication. However, when a client roams between access points secured with WPA2-PSK, it typically needs to perform a full re-authentication with each new AP. This re-authentication overhead introduces noticeable delays during the handoff process, directly impacting roaming speed and making it an unsuitable solution for seamless transitions.

• ✗

  Set all access points to the same SSID and password.

  Why it's wrong here

  While configuring all access points with the same Service Set Identifier (SSID) and password is a fundamental prerequisite for client devices to even attempt roaming within a wireless network, it does not inherently guarantee fast or seamless handoffs. Without additional protocols like 802.11r, the client still undergoes a full re-authentication process when moving between APs, which introduces latency and can disrupt real-time applications. This setup merely enables the possibility of roaming; it does not optimize its speed or efficiency.

• ✓

  Implement 802.11r Fast Roaming.

  Why this is correct

  Implementing 802.11r, also known as Fast Basic Service Set (BSS) Transition, directly addresses the issue of slow roaming by significantly reducing the authentication time required when a client moves between access points within the same network. It achieves this by allowing clients to pre-authenticate or "fast re-associate" with target APs, thereby minimizing the handoff delay and ensuring a much smoother, more seamless connection for mobile devices. This standard is specifically designed to optimize roaming performance for latency-sensitive applications.

• ✗

  Use a wireless controller with load balancing.

  Why it's wrong here

  A wireless controller with load balancing is designed to distribute client devices evenly across available access points to prevent any single AP from becoming overloaded, thereby optimizing overall network capacity and performance. However, load balancing primarily manages initial client connections and ongoing client distribution, not the speed or efficiency of the handoff process itself when a client decides to roam. It does not accelerate the re-authentication or re-association steps critical for fast roaming, which is a distinct function.

Go deeper

Related to this question