300-430 Question 1
Single answerAn organization has deployed a Cisco FlexConnect solution for its branch offices. During a WAN outage, users in one of the branch offices report issues with accessing local resources despite being connected to the wireless network. Upon investigation, it is observed that the SSID in use is not functioning as expected during the WAN downtime. What could be the cause of this issue?
- A
The SSID is not configured for FlexConnect Local Switching.
- B
The AP is not in connected mode with the controller.
- C
The VLAN mappings for the SSID are not defined on the AP in FlexConnect mode.
- D
The FlexConnect AP is not configured for standalone mode.
Show answer and explanation
Correct answer: A
Explanation
In a Cisco FlexConnect deployment, SSIDs that need to continue functioning during WAN outages must be configured for Local Switching. This allows the AP to locally switch the traffic instead of trying to send it to the controller over the WAN. If Local Switching is not enabled, the SSID traffic will fail during WAN downtime, leading to the issue described.
- A. Correct.
If the SSID is not configured for FlexConnect Local Switching, traffic from the SSID will still attempt to traverse the WAN to the controller, causing issues during a WAN outage.
- B. Incorrect.
APs in connected or standalone mode will continue to operate with their configuration; however, this is not directly related to the issue described.
- C. Incorrect.
While VLAN mappings are crucial for FlexConnect Local Switching, their absence would not result in complete SSID failure but may cause incorrect VLAN tagging.
- D. Incorrect.
FlexConnect APs do not need to be explicitly configured for standalone mode; they automatically switch to standalone mode during a WAN outage.