To implement the system from misjudging roaming with the same VLAN ID but in different subnets as Layer 2 roaming, you need to use the roaming domain to determine whether the devices are in the same…

Question

Options

• ATRUE
• BFALSE
• C
• D

• A
  70% (28)
• B
  5% (2)
• C
  8% (3)
• D
  18% (7)

Explanation

A is correct because in wireless network deployments, two access points can share the same VLAN ID while belonging to different IP subnets - a situation that would cause a naive system to incorrectly classify an inter-subnet handoff as Layer 2 roaming. Using a roaming domain as the deciding factor resolves this ambiguity: if the client's old and new APs share the same subnet (regardless of VLAN ID), it is Layer 2 roaming; if the subnets differ, it is Layer 3 roaming, which requires IP address reassignment and additional handling.

B (FALSE) is wrong because the statement accurately describes the correct implementation approach - skipping the roaming domain check and relying solely on VLAN ID would cause miscategorization and broken connectivity for clients crossing subnet boundaries.

Memory tip: Think of VLAN ID as a "label" and subnet as the "neighborhood." Two buildings (APs) can wear the same label but be in different neighborhoods. Only checking which neighborhood (subnet/roaming domain) tells you whether the client truly stayed local (L2) or moved far enough to need a new address (L3).

No community discussion yet for this question.