VLAN Configuration

A

Sure, I'd be happy to explain each of the answer choices in detail:

A. The statement that the switch must be in VTP server or transparent mode before you can configure a VLAN is false. You can configure a VLAN on a switch regardless of whether it is in VTP server or transparent mode. VTP (VLAN Trunking Protocol) is a protocol that enables switches to exchange VLAN information with each other, but it is not necessary for creating VLANs on a switch.

B. The statement that the switch must be in config-vlan mode before you configure an extended VLAN is false. In fact, there is no "config-vlan" mode in Cisco switches. To configure a VLAN, you enter VLAN configuration mode by using the command "vlan <vlan-id>" followed by any additional configuration commands for that VLAN. Extended VLANs (VLAN IDs 1006-4094) require the use of the "vlan dot1q tag native" command to enable their use, but this does not require a special configuration mode.

C. The statement that dynamic inter-VLAN routing is supported on VLAN2 through VLAN 4064 is false. Dynamic inter-VLAN routing (e.g. using a routing protocol like OSPF or EIGRP) can be used on any VLAN on a switch, regardless of its VLAN ID. The VLAN ID simply serves as a way to logically group devices and traffic together. However, some switches may have limits on the number of VLANs that can be routed simultaneously, so it's possible that some VLANs may not be able to be routed on certain switches.

D. The statement that a switch in VTP transparent mode saves the VLAN databases to the running configuration only is true. When a switch is in VTP transparent mode, it does not participate in VTP updates and does not store a copy of the VTP database. Instead, any VLANs that are created or deleted on a switch in transparent mode are saved to the running configuration only. This means that if the switch is rebooted or the running configuration is erased, the VLAN configuration will need to be manually re-entered.