The VLANs may be named.
VLAN information is saved in the startup configuration.
Non-default VLANs created manually must use the extended range VLAN numbers.
The network administrator may create the VLANs in either global configuration mode or VLAN database mode.
Both VLANs may be named BUILDING_A to distinguish them from other VLANs in different geographical locations.
Dynamic desirable mode
On or dynamic desirable mode
On, auto, or dynamic desirable mode
On, auto, dynamic desirable, or nonegotiate mode
DTP cannot negotiate the trunk since the native VLAN is not the default VLAN.
The remote connected interface cannot negotiate a trunk unless it is also configured as dynamic desirable.
The connected devices dynamically determine when data for multiple VLANs must be transmitted across the link and bring the trunk up as needed.
A trunk link is formed if the remote connected device is configured with the switchport mode dynamic auto or switchport mode trunk commands.
Configuring interswitch connections as trunks will cause all hosts on any VLAN to receive broadcasts from the other VLANs.
A trunk connection is affected by broadcast storms on any particular VLAN that is carried by that trunk.
Restricting trunk connections between switches to a single VLAN will improve efficiency of port usage.
Carrying all required VLANs on a single access port will ensure proper traffic separation.
The network administrator configured VLANs 1002-1005.
The VLANs are in the active state and are in the process of negotiating configuration parameters.
A FDDI trunk has been configured on this switch.
The command switchport access vlan 20 was entered in interface configuration mode for Fast Ethernet interface 0/1.
Devices attached to ports fa0/5 through fa0/8 cannot communicate with devices attached to ports fa0/9 through fa0/12 without the use of a Layer 3 device.
Enter the no vlan 2 and the vlan 3 commands in global configuration mode.
Enter the switchport access vlan 3 command in interface configuration mode.
Enter the switchport trunk native vlan 3 command in interface configuration mode.
Enter the no shutdown in interface configuration mode to return it to the default configuration and then configure the port for VLAN 3.
Hosts on different VLANs use VTP to negotiate a trunk.
Hosts on different VLANs communicate through routers.
Hosts on different VLANs should be in the same IP network.
Hosts on different VLANs examine VLAN ID in the frame tagging to determine if the frame for their network.
None of the computers will receive the broadcast frame
Computer A, computer B, computer C
Computer A, computer D, computer G
Computer D, computer G
Computer A, computer B, computer C, computer D, computer E, computer F, computer G, computer H, computer I
VLAN 1 can never be deleted.
VLAN 1 can only be deleted by deleting the vlan.dat file.
VLAN 1 can not be deleted until all ports have been removed from it.
VLAN 1 can not be deleted until another VLAN has been assigned its responsibilities.
Interface Fa0/2 on switch SW2 will negotiate to become a trunk link if it supports DTP.
Interface Fa0/2 on switch SW2 can only become a trunk link if statically configured as a trunk.
Interface Fa0/1 converts the neighboring link on the adjacent switch into a trunk link if the neighboring interface is configured in nonegotiate mode.
Interface Fa0/1 converts the neighboring link on the adjacent switch into a trunk link automatically with no consideration of the configuration on the neighboring interface.
The link between the switches is up but not trunked.
VLAN 3 is not an allowed VLAN to enter the trunk between the switches.
The router is not properly configured to route traffic between the VLANs.
Computer D does not have a proper address for the VLAN 3 address space.
802.1q is Cisco proprietary.
802.1q frames are mapped to VLANs by MAC address.
802.1q does NOT require the FCS of the original frame to be recalculated.
802.1q will not perform operations on frames that are forwarded out access ports.
The ports cannot communicate with other ports.
The ports default back to the management VLAN.
The ports automatically become a part of VLAN1.
The ports remain a part of that VLAN until the switch is rebooted. They then become members of the management VLAN.
Delete any VLANs currently being trunked through port Fa0/1.
Administratively shut down and re-enable the interface to return it to default.
Enter the switchport mode access command in interface configuration mode.
The switch to switch connection must be configured as an access port to permit access to VLAN 10 on S3.
The new PC is on a different subnet so Fa0/2 on S3 must be configured as a trunk port.
PC4 must use the same subnet as the other HR VLAN PCs.
A single VLAN cannot span multiple switches.
There is a native VLAN mismatch.
The link between Switch1 and Switch2 is up but not trunked.
The router is not properly configured for inter-VLAN routing.
VLAN 50 is not allowed to entering the trunk between Switch1 and Switch2.
VLAN1 should renamed.
VLAN 1 is the management VLAN.
All switch ports are members of VLAN1.
Only switch port 0/1 is assigned to VLAN1.
Links between switches must be members of VLAN1.
VLANs improve network performance by regulating flow control and window size.
VLANs enable switches to route packets to remote networks via VLAN ID filtering.
VLANs reduce network cost by reducing the number of physical ports required on switches.
VLANs improve network security by isolating users that have access to sensitive data and applications.
VLANs divide a network into smaller logical networks, resulting in lower susceptibility to broadcast storms.
Cisco switches only support the ISL trunking protocol.
The trunk cannot be negotiated with both ends set to auto.
By default, Switch1 will only allow VLAN 5 across the link.
A common native VLAN should have been configured on the switches.
The default native VLAN is being used.
The trunking mode is set to auto.
Trunking can occur with non-Cisco switches.
VLAN information about the interface encapsulates the Ethernet frames.