What happens when VLAN filtering is enabled on a bridge?

What happens when VLAN filtering is enabled on a bridge?

• A. The bridge becomes VLAN-aware but requires per-port configuration
• B. VLANs are ignored by the bridge
• C. The bridge becomes aware of VLANs, allowing VLAN interfaces to be used for traffic segmentation
• D. The bridge converts all VLAN traffic to untagged

Answer: (C)

Enabling VLAN filtering makes the bridge operate as VLAN-aware. The bridge starts to recognize 802.1Q tags and uses per-port VLAN membership and PVID settings to decide where traffic belongs. This setup lets you create VLAN interfaces directly on the bridge (traffic can be segmented by creating VLANs on the bridge itself, like br0.10, br0.20, etc.), so different VLANs carry different traffic paths through the same bridge. Frames are tagged or mapped to a specific VLAN as they pass, rather than all traffic being treated as a single, unsegmented stream. In short, the bridge becomes aware of VLANs and supports using VLAN interfaces for traffic segmentation.

Enabling VLAN filtering makes the bridge operate as VLAN-aware. The bridge starts to recognize 802.1Q tags and uses per-port VLAN membership and PVID settings to decide where traffic belongs. This setup lets you create VLAN interfaces directly on the bridge (traffic can be segmented by creating VLANs on the bridge itself, like br0.10, br0.20, etc.), so different VLANs carry different traffic paths through the same bridge. Frames are tagged or mapped to a specific VLAN as they pass, rather than all traffic being treated as a single, unsegmented stream. In short, the bridge becomes aware of VLANs and supports using VLAN interfaces for traffic segmentation.