300-425 Question 17
Single answerA company has deployed multiple branch offices using FlexConnect APs grouped into FlexConnect groups. The network administrator notices that when users roam between APs within the same branch office, there are occasional disruptions in connectivity. What could be the reason for this issue?
- A
The FlexConnect groups are not configured to share VLAN information across APs.
- B
The WLAN is configured to use local switching instead of central switching.
- C
The APs within the FlexConnect group are incorrectly configured with different Mobility Group names.
- D
The branch office APs are not connected to the same WLC for seamless roaming.
Show answer and explanation
Correct answer: C
Explanation
In FlexConnect deployments, the Mobility Group name is a critical configuration for seamless roaming. All APs within the same FlexConnect group should have the same Mobility Group name. When this is not configured correctly, roaming disruptions can occur because the APs cannot coordinate the session handoff properly. This is particularly relevant in branch office scenarios where consistency in configuration is crucial for reliable performance.
- A. Incorrect.
FlexConnect groups are used to facilitate VLAN pooling and configuration consistency, but VLAN information sharing is not typically related to roaming disruptions.
- B. Incorrect.
Local switching is commonly used in FlexConnect deployments to reduce latency, but it is not the primary cause of roaming disruptions if configured correctly.
- C. Correct.
Mobility Group names must be consistent across APs within a FlexConnect group to enable seamless roaming. If APs in the same group have different Mobility Group names, roaming disruptions can occur.
- D. Incorrect.
In a FlexConnect deployment, APs do not need to be connected to the same WLC for roaming within the same branch office, as roaming is handled locally.