287
24. C. VLANs 1 and 1002 through 1005 are protected by the IOS and cannot be changed,
renamed, or deleted. VLAN 1 cannot be deleted, regardless of whether it is still configured
on a port. The VLAN that serves as the switch’s main management IP can be changed to
any other VLAN; it only defaults to VLAN 1 from the factory. VLAN 1 cannot be deleted
regardless of whether it is configured as a native VLAN on a trunk.
25. D. For security concerns, it should not be used in production. It is the default VLAN
configured on all switches. Potentially, a computer can be plugged into an interface
defaulted to VLAN 1 and expose resources such as the switch management network.
VLAN 1 can be used as a production VLAN, and by default, all switches are configured
to use VLAN 1 right out of the box. VLAN 1 can also be routed the same as any other
VLAN via an SVI. VLAN 1 can also participate in VTP transfers, although its name
cannot be modified.
26. B. VLAN 1 is the default VLAN and it is not permitted by the IOS to change the VLAN
in any way. This includes name changes. VLAN 1 cannot be renamed regardless of
whether it is used on another interface currently. All VLANs are configured numerically
in Cisco IOS; a friendly name can be attached after it is configured. VLAN 1 cannot be
renamed regardless of which configuration prompt you are in.
27. C. The port needs to be changed from trunk mode to access mode via the command
switchport mode access. Although switchport native vlan 12 would remedy the
problem, it would be an improper configuration since you are expecting tagged traffic
and directing untagged traffic to VLAN 12. Removing switch port nonegotiate mode
would only allow the computer to negotiate a trunking protocol via DTP. Configuring the
command
no spanning-tree portfast would prevent the port from forwarding traffic
right away.
28. B. The command to verify that a VLAN is created and the port(s) it is associated with
is
show vlan. The command show vlans is incorrect as it should be singular.
The command
show access vlan is incorrect because it is not a valid command. The
command
show vlan database is incorrect because it is not a valid command.
29. B. When the command is invoked inside of the interface, it will create the VLAN
automatically. The command will not error, but if you are consoled into the device or you
are monitoring the terminal, you can see the VLAN get automatically created. When the
VLAN is auto-created, traffic will forward without the need of any other configuration.
The original command of
switch access vlan 12 will be accepted, and the VLAN will
be auto-created.
30. A. Creating the new VLAN will logically segment this work group. Creating a Switched
Virtual Interface (SVI) will allow routing on the layer 3 switch. The ACLs should only be
applied to VLAN interfaces. Although the other solutions achieve a similar goal, they do
not provide flexibility. Extended ACLs cannot be applied to the R&D switch ports since
they are layer 2 ports and extended ACLs are layer 3 entries. Creating a new VLAN for
R&D and placing the R&D server in the VLAN will not accomplish the goal of restricting
the server. Creating a new VLAN and using a trunk to connect the production and R&D
network will not accomplish the task.
Do'stlaringiz bilan baham: |