You save $69.98
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.
At an e-commerce platform, the branch support lead has a healthy trunk allowing several production VLANs, but must add new VLAN 151 without deleting any current allowed entries. Which IOS command is appropriate?
Using the add form includes VLAN 151 while retaining the existing allowed VLAN entries. This avoids inadvertently removing the VLANs already traversing the trunk.
Without add, this command replaces the current allowed list with VLAN 151. Previously permitted VLANs could lose reachability.
An access VLAN command does not append to the allowed VLAN list on a trunk. It changes a separate access-port property.
This syntax does not add VLAN 151 to the trunk allowance and can remove/rewrite the list instead.
Two Cisco switches use an 802.1Q trunk. Switch A uses native VLAN 99 and switch B uses native VLAN 1. What is the main risk of this mismatch?
The native VLAN defines classification of untagged frames. Mismatched native VLAN IDs can place the same untagged traffic into different broadcast domains and trigger mismatch warnings.
The native VLAN mismatch does not automatically synchronize VLAN membership or tagging rules.
Host Layer 3 addressing does not fix the different untagged VLAN classifications at the two trunk ends.
Native VLAN selection controls handling of untagged frames, not burned-in interface MAC addresses.
At a manufacturing plant, the branch support lead investigates untagged-frame misclassification on a trunk that also needs VLAN 96; the design reserves VLAN 624 for native traffic. What should be done?
Consistent native VLAN 624 maps untagged frames to the same domain on both peers, and VLAN 96 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.
DTP controls trunk negotiation. Disabling it cannot correct an existing native VLAN ID mismatch between two trunks.
A trunk between SW1 and SW2 permits VLANs 10,20,30. VLAN 30 hosts communicate across the link, but VLAN 40 is active locally on both switches and unreachable remotely. Which investigation best fits?
A trunk can be operational while filtering a particular VLAN. Its allowed/active list should be checked before changing native VLAN or spanning-tree behavior.
A one-ended native-VLAN change can misclassify untagged frames and does not correctly permit tagged VLAN 40.
Access mode transports one untagged access VLAN, not independent tagged VLANs 30 and 40.
Disabling STP introduces loop risk and does not add VLAN 40 to an allowed list.
Trunk A allows VLANs 10 and 30, while switch B’s matching trunk allows VLAN 10 only. Hosts in VLAN 10 communicate but VLAN 30 is isolated across the link. Which action is needed?
Both ends must permit VLAN 30 for tagged frames to cross the inter-switch link in the intended direction. One-sided allowed-list changes can isolate that VLAN.
That would break the known working VLAN without permitting the missing VLAN 30 on B.
Matching STP bridge priority cannot allow tagged VLAN 30 where the trunk is explicitly filtering it.
Mismatched native VLANs can leak or misclassify frames and are not a safe fix for explicit VLAN tagging permission.
At a bank branch, the on-call technician sees a native VLAN mismatch alert on a trunk whose design specifies native VLAN 875 at both ends. What change resolves the mismatch without dropping tagged VLAN 149?
For a conventional 802.1Q trunk, untagged frames are assigned to the configured native VLAN. Both peers must agree on native VLAN 875 to avoid VLAN leakage and mismatch warnings.
Native VLAN 875 versus 493 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.
An access port is not a trunk and cannot carry the distinct required tagged VLANs.
At an airport terminal, an implementation partner has a healthy trunk allowing several production VLANs, but must add new VLAN 31 without deleting any current allowed entries. Which IOS command is appropriate?
Using the add form includes VLAN 31 while retaining the existing allowed VLAN entries. This avoids inadvertently removing the VLANs already traversing the trunk.
Without add, this command replaces the current allowed list with VLAN 31. Previously permitted VLANs could lose reachability.
An access VLAN command does not append to the allowed VLAN list on a trunk. It changes a separate access-port property.
This syntax does not add VLAN 31 to the trunk allowance and can remove/rewrite the list instead.
A provider-facing switch trunk is statically configured and should not send Cisco DTP negotiation frames to the adjacent non-Cisco device. Which additional command is appropriate?
On supported Cisco platforms, nonegotiate suppresses DTP negotiations after a compatible static trunk/access mode is configured. Verify that both sides agree on tagging and allowed VLANs.
Dynamic desirable actively negotiates trunk status through DTP and conflicts with the stated requirement.
Allowing every VLAN changes traffic authorization and does not suppress DTP frames.
PortFast changes STP convergence behavior on edge ports; it does not disable trunk negotiation frames.
At a media studio, a network administrator investigates untagged-frame misclassification on a trunk that also needs VLAN 286; the design reserves VLAN 713 for native traffic. What should be done?
Consistent native VLAN 713 maps untagged frames to the same domain on both peers, and VLAN 286 must remain in the trunk allowance for its tagged traffic.
A host port access VLAN does not determine the 802.1Q native VLAN mapping on the inter-switch trunk.
This explicitly creates different native VLANs between peers, causing the same mismatch and potential misclassification.
An SVI gateway changes routed access and cannot reconcile unequal native VLAN tagging on a Layer 2 trunk.
Two Cisco switch uplinks both use `switchport mode dynamic auto` and remain access links even though VLANs 100 and 200 must traverse an 802.1Q trunk. Which change directly establishes the required trunk?
Two dynamic-auto peers do not actively negotiate trunking. A deliberate trunk configuration or compatible active DTP mode is required, followed by verification of VLANs.
Gateway IPs affect routed connectivity and cannot initiate DTP or make an Ethernet switchport a trunk.
PortFast changes STP edge behavior, not trunk encapsulation or DTP mode negotiation.
A Layer 2 access port belongs to one data VLAN and cannot simultaneously bridge two independent VLANs without trunking.
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.
