You save $69.98
At a hotel, the site engineer is asked to verify an inter-switch 802.1Q trunk carrying VLAN 100. Which observation most directly proves the traffic is allowed at Layer 2?
show interfaces trunk reports trunk state, encapsulation/native settings and which VLANs are actually permitted and active. That directly tests whether VLAN 100 is carried.
Local VLAN presence does not prove that the switch link negotiated 802.1Q tagging or carries VLAN 100 end-to-end.
A default route is a Layer 3 property and cannot prove the Layer 2 trunk carries VLAN 100.
Interface descriptions are administratively assigned text and do not guarantee operational 802.1Q trunking for VLAN 100.
At a bank branch, the site engineer investigates untagged-frame misclassification on a trunk that also needs VLAN 246; the design reserves VLAN 711 for native traffic. What should be done?
Consistent native VLAN 711 maps untagged frames to the same domain on both peers, and VLAN 246 must remain in the trunk allowance for its tagged traffic.
An SVI gateway changes routed access and cannot reconcile unequal native VLAN tagging on a Layer 2 trunk.
This explicitly creates different native VLANs between peers, causing the same mismatch and potential misclassification.
Auto-negotiating a physical link does not reconcile the differing native VLAN ID used to classify untagged 802.1Q frames.
At a university, a network administrator needs to preserve multiple VLAN broadcast domains across an Ethernet switch uplink. A review notes VLAN 185 must be tagged while native VLAN 671 handles untagged frames. Which description matches?
802.1Q trunks mark non-native VLAN frames with tags, allowing multiple VLANs on one link; consistent native VLAN 671 handles untagged frames. The allowed list must include 185.
Access mode generally carries one untagged data VLAN, so it cannot substitute for a multi-VLAN tagged trunk.
Both DTP auto peers may stay access; the requirement needs confirmed 802.1Q trunk operation for tagged VLANs.
The one-ended native mapping can misclassify untagged frames and does not correctly implement consistent native VLAN 671.
Switches SW-A and SW-B have an operational 802.1Q trunk. Hosts in VLAN 30 communicate across it, but VLAN 40 hosts cannot. On SW-A, `show interfaces trunk` lists VLANs 10,30 as allowed; VLAN 40 exists on both switches. What is the first corrective change?
The allowed-VLAN list filters which tagged VLANs the trunk carries. Adding VLAN 40 on the required trunk ports addresses the observed exclusion without merging VLANs or changing native VLAN roles.
Native VLAN controls classification of untagged frames; it does not replace an omitted VLAN in the allowed list. Making user VLAN 40 native is an unrelated change.
Access mode cannot transport several separate 802.1Q VLANs between switches. It would also disrupt the functioning VLAN 30 path.
Discovery protocols report neighbors and capabilities; they do not silently reconfigure a switch's trunk allowed-VLAN list.
At a satellite office, an implementation partner sees a native VLAN mismatch alert on a trunk whose design specifies native VLAN 779 at both ends. What change resolves the mismatch without dropping tagged VLAN 241?
For a conventional 802.1Q trunk, untagged frames are assigned to the configured native VLAN. Both peers must agree on native VLAN 779 to avoid VLAN leakage and mismatch warnings.
An access port is not a trunk and cannot carry the distinct required tagged VLANs.
Native VLAN 779 versus 329 classifies untagged frames differently at each endpoint. That is a mismatch, not a fix.
Changing a single end does not enforce consistent native handling; the peer may classify untagged frames into a different VLAN.
A campus trunk must stop transporting decommissioned VLAN 60 but retain VLANs 10,20,30,40, and all other currently authorized entries. Which configuration avoids replacing the full list?
The remove keyword subtracts only VLAN 60 from the trunk allowed list. Validate the operational list at both ends before the old VLAN is deleted.
Without add/remove this replaces the allowed list with only VLAN 60, the opposite of the requirement.
An access VLAN setting does not remove one VLAN from an operational trunk allowance.
Adding VLAN 60 retains the decommissioned VLAN rather than removing its transport permission.
An inter-switch 802.1Q trunk currently permits VLANs 60,40,80. The Gi1/0/3 uplink must also carry newly authorized VLAN 133 without removing existing production VLANs. Which IOS configuration preserves all four VLANs?
The add form appends VLAN 133 to the current allowed list 60,40,80; these already permitted VLANs remain carried by the trunk. Verify 60,40,80,133 in show interfaces trunk.
Without the add keyword, the trunk allowance is replaced by only VLAN 133, potentially disconnecting 60,40,80.
An access VLAN setting assigns untagged endpoint traffic; it does not extend this tagged inter-switch allowed-VLAN list.
Native VLAN changes untagged-frame classification and does not append tagged VLAN 133 to the allowed list.
At an enterprise data center, the infrastructure lead investigates untagged-frame misclassification on a trunk that also needs VLAN 171; the design reserves VLAN 751 for native traffic. What should be done?
Consistent native VLAN 751 maps untagged frames to the same domain on both peers, and VLAN 171 must remain in the trunk allowance for its tagged traffic.
An SVI gateway changes routed access and cannot reconcile unequal native VLAN tagging on a Layer 2 trunk.
This explicitly creates different native VLANs between peers, causing the same mismatch and potential misclassification.
An allowed-VLAN list controls tagged traffic carriage; it does not fix different classifications of untagged native frames.
Two switches have a working 802.1Q trunk with VLANs 20 and 30 allowed. SW1 uses native VLAN 20, but SW2 uses native VLAN 30. CDP reports a native-VLAN mismatch. What action addresses the actual forwarding risk?
An untagged 802.1Q frame is classified into the local native VLAN. Matching native VLAN configurations prevent SW1's untagged traffic from being interpreted as a different VLAN at SW2.
PortFast changes spanning-tree edge behavior; it does not reconcile differing native VLAN identifiers and is inappropriate as a general trunk fix.
Allowing more tagged VLANs does not change how untagged frames are classified. A native mismatch persists.
Suppressing a discovery warning hides evidence but does not change the differing VLAN mappings on the trunk.
At a bank branch, the branch support lead must carry VLANs 170 and 496 across one 802.1Q inter-switch connection. Which interface configuration meets this requirement?
A trunk carries tagged VLAN 170 and 496 over one interface. The allowed list names both required broadcast domains.
The allowed list omits required VLAN 170. A trunk can be operational yet filter frames of a missing VLAN.
Administratively shutting down the interface prevents both VLANs from traversing even with a correct allowed list.
Access mode carries one regular untagged data VLAN rather than both required tagged VLANs. VLAN 496 would not traverse it.
At a stadium, a network administrator sees a native VLAN mismatch alert on a trunk whose design specifies native VLAN 727 at both ends. What change resolves the mismatch without dropping tagged VLAN 61?
For a conventional 802.1Q trunk, untagged frames are assigned to the configured native VLAN. Both peers must agree on native VLAN 727 to avoid VLAN leakage and mismatch warnings.
Changing a single end does not enforce consistent native handling; the peer may classify untagged frames into a different VLAN.
Native VLAN 727 versus 414 classifies untagged frames differently at each endpoint. That is a mismatch, not a fix.
An access port is not a trunk and cannot carry the distinct required tagged VLANs.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (760 Questions, Last Updated on Nov 4, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
