Helping Hand Questions for 200-301

Answer as below configuration:

On SW1:

conf terminal

vlan 15

exit

interface range eth0/0 - 1

channel-group 1 mode active

exit

interface port-channel 1

switchport trunk encapsulation dot1q

switchport mode trunk

switchport trunk native vlan 15

end

copy run start

on SW2:

conf terminal

vlan 15

exit

interface range eth0/0 - 1

channel-group 1 mode active

exit

interface port-channel 1

switchport trunk encapsulation dot1q

switchport mode trunk

switchport trunk native vlan 15

end

copy run start

To configure an LACP EtherChannel and number it as 44, configure it between switches SW1 and SW2 using interfaces Ethernet0/0 and Ethernet0/1 on both sides, configure the EtherChannel as a trunk link, configure the trunk link with 802.1q tags, and configure VLAN ‘MONITORING’ as the untagged VLAN of the EtherChannel, you need to follow these steps:

On both SW1 and SW2, enter the global configuration mode by using the configure terminal command.

On both SW1 and SW2, select the two interfaces that will form the EtherChannel by using the interface range ethernet 0/0 - 1 command. This will enter the interface range configuration mode.

On both SW1 and SW2, set the protocol to LACP by using the channel-protocol lacp command.

On both SW1 and SW2, assign the interfaces to an EtherChannel group number 44 by using the channel-group 44 mode active command. This will create a logical interface named Port-channel44 and set the LACP mode to active on both ends. The LACP mode must match on both ends for the EtherChannel to form.

On both SW1 and SW2, exit the interface range configuration mode by using the exit command.

On both SW1 and SW2, enter the Port-channel interface configuration mode by using the interface port-channel 44 command.

On both SW1 and SW2, configure the Port-channel interface as a trunk link by using the switchport mode trunk command.

On both SW1 and SW2, configure the Port-channel interface to use 802.1q tags for VLAN identification by using the switchport trunk encapsulation dot1q command.

On both SW1 and SW2, configure VLAN ‘MONITORING’ as the untagged VLAN of the Port-channel interface by using the switchport trunk native vlan MONITORING command.

On both SW1 and SW2, exit the Port-channel interface configuration mode by using the exit command.

On both SW1 and SW2, save the configuration to NVRAM by using the copy running-config startup-config command.

Answer as below configuration:

Sw1

enbale

config t

Vlan 210

Name FINANCE

Inter e0/1

Switchport access vlan 210

do wr

Sw2

Enable

config t

Vlan 110

Name MARKITING

Int e0/1

Switchport acees vlan 110

do wr

Sw3

Enable

config t

Vlan 110

Name MARKITING

Vlan 210

Name FINANCE

Int e0/0

Switchport access vlan 110

Int e0/1

Switchport access vlan 210

Sw1

Int e0/1

Switchport allowed vlan 210

Sw2

Int e0/2

Switchport trunk allowed vlan 210

Sw3

Int e0/3

Switchport trunk allowed vlan 210

Switchport trunk allowed vlan 210,110

The matching is based on identifying the attack layer and then choosing the control that blocks that behavior. Dynamic ARP Inspection validates ARP messages against trusted bindings and is used against ARP spoofing or poisoning, a common man-in-the-middle technique on Layer 2 segments. DHCP snooping builds the trusted binding table and blocks unauthorized DHCP server behavior. Port security limits which MAC addresses can use a switchport, reducing exposure to MAC flooding or unauthorized endpoint attachment. Changing the native VLAN or using proper trunk controls helps mitigate VLAN hopping and double-tagging attacks, because the attacker relies on trunk/native VLAN behavior to cross VLAN boundaries. Cisco CCNA v1.1 Network Access includes switch security features such as DHCP snooping, DAI, and port security. The practical approach is not to memorize coordinates in a drag-and-drop map. Identify the malicious mechanism first, then map it to the feature that checks or constrains that exact mechanism.

In this attack, the attacking computer generates frames with two 802.1Q tags. The first tag matches the native VLAN of the trunk port (VLAN 10 in this case), and the second matches the VLAN of a host it wants to attack (VLAN 20).