300-425 Question 30
Single answerA network engineer is deploying a Cisco FlexConnect-enabled wireless environment at a remote branch. The branch has VLAN-based central switching enabled for guest traffic while using Flex ACLs for local data traffic. During testing, the engineer notices that guest traffic is not following the configured VLAN mapping. What could be a possible reason for this issue?
- A
The WLAN is not configured for VLAN-based central switching on the WLC.
- B
FlexConnect is not supported with VLAN-based central switching.
- C
Flex ACLs are misconfigured and are overriding VLAN-based central switching.
- D
The branch APs are in connected mode instead of standalone mode.
Show answer and explanation
Correct answer: A
Explanation
In a FlexConnect deployment, VLAN-based central switching needs to be explicitly configured on the WLC for the corresponding WLAN. If this configuration is missing, the APs will not correctly forward guest traffic to the intended VLAN, regardless of other settings like Flex ACLs. This scenario highlights the importance of properly configuring the WLAN on the WLC to ensure the expected traffic flow.
- A. Correct.
Correct. If the WLAN is not configured for VLAN-based central switching on the WLC, the APs will not forward traffic to the correct VLAN, causing the issue described.
- B. Incorrect.
Incorrect. FlexConnect supports VLAN-based central switching, especially for use cases like guest or specific traffic management.
- C. Incorrect.
Incorrect. Flex ACLs apply to locally switched traffic, not centrally switched traffic. Therefore, they do not interfere with VLAN-based central switching.
- D. Incorrect.
Incorrect. VLAN-based central switching is supported in connected mode, which is the typical mode for APs in FlexConnect deployments when they have connectivity to the WLC.