350-401 · Question #161
Company policy restricts VLAN 10 to be allowed only on SW1 and SW2. All other VLANs can be on all three switches. An administrator has noticed that VLAN 10 has propagated to SW3. Which configuration c
The correct answer is C. SW2(config)#int gi1/2. To prevent an unauthorized VLAN from propagating to a specific switch, the trunk port connecting the upstream switch to the downstream switch must be configured to prune that VLAN.
Question
Exhibits
Options
- ASW1(config)#int gi1/1
- BSW2(config)#int gi1/2
- CSW2(config)#int gi1/2
- DSW1(config)#int gi1/1
How the community answered
(18 responses)- A11% (2)
- B6% (1)
- C78% (14)
- D6% (1)
Why each option
To prevent an unauthorized VLAN from propagating to a specific switch, the trunk port connecting the upstream switch to the downstream switch must be configured to prune that VLAN.
Applying `switchport trunk allowed vlan remove 10` to `gi1/1` on SW1 (if it connects to SW2) would prevent VLAN 10 from reaching SW2, which contradicts the policy requiring VLAN 10 on SW2.
This choice is a partial command; however, if it implies removing VLAN 10, it must be applied to the correct interface (the one connecting SW2 to SW3) to be effective for the stated problem.
To prevent VLAN 10 from propagating to SW3 while ensuring it remains available on SW1 and SW2, the trunk link originating from SW2 and connecting to SW3 must be configured to exclude VLAN 10. The command `switchport trunk allowed vlan remove 10` applied to interface `gi1/2` on SW2 (assuming `gi1/2` connects to SW3) specifically prunes VLAN 10 from that trunk, correcting the unauthorized propagation.
Applying `switchport trunk allowed vlan remove 10` to `gi1/1` on SW1 (if it connects to SW2) would prune VLAN 10 from the trunk between SW1 and SW2, preventing it from reaching SW2, which is contrary to the company policy.
Concept tested: VLAN pruning on trunk ports
Source: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12_2_55_se/configuration/guide/3560scg/swvlan.html
Topics
Community Discussion
No community discussion yet for this question.

