There are 500 employees in a certain enterprise building, and they usually start to connect to the company's WLAN network in the lobby when they go to work. As each employee walks to their…

Question

Options

• ADo not configure VLAN Pool, configure a static IP address for each mobile terminal
• BConfigure VLAN Pool and configure Hash algorithm
• CConfigure the VLAN Pool and configure the load balance algorithm
• DConfigure VLAN Pool, any configuration algorithm

• A
  3% (1)
• B
  71% (22)
• C
  10% (3)
• D
  16% (5)

Explanation

Option B is correct because with 500 roaming employees, a VLAN Pool is needed to split broadcast domains and scale IP addressing - and the Hash algorithm maps each client's MAC address deterministically to the same VLAN every time, so as a user roams between APs, they land in the same VLAN, retain their IP address, and sessions stay unbroken.

Why the distractors fail:

• A - Static IPs don't solve the VLAN consistency problem; if a roaming client lands on a different VLAN, it's still on the wrong subnet regardless of its static address, and managing 500 static IPs is operationally impractical.
• C - The load-balance algorithm distributes clients across VLANs to even out traffic, but it doesn't guarantee a client gets the same VLAN on every association, so a roaming user may get a new IP mid-session, breaking connections.
• D - Algorithm choice is not arbitrary; "any algorithm" implicitly includes load-balance, which breaks roaming continuity as explained above.

Memory tip: Think "Hash = Habit" - a hash function is a creature of habit, always producing the same output for the same input (MAC address), so the client always goes home to the same VLAN. Load balance, by contrast, is about fairness, not consistency.

No community discussion yet for this question.