Free Cisco 200-301 Practice Exam with Questions & Answers | Set: 4

Answer as below configuration:

on R1

config terminal

ipv6 unicast-routing

inter eth0/1

ip addre 192.168.1.1 255.255.255.240

ipv6 addre 2001:db8:aaaa::1/64

not shut

end

copy running start

on R2

config terminal

ipv6 unicast-routing

inter eth0/1

ip address 192.168.1.14 255.255.255.240

ipv6 address 2001:db8:aaaa::2/64

not shut

end

copy running start

---------------------

for test from R1

ping ipv6 2001:db8:aaaa::1

for test from R2

ping ipv6 2001:db8:aaaa::2

Answer as below configuration:

on R1

conf terminal

interface Loopback0

ip address 10.10.1.1 255.255.255.255

!

interface Loopback1

ip address 192.168.1.1 255.255.255.0

!

interface Ethernet0/0

no shut

ip address 10.10.12.1 255.255.255.0

ip ospf 1 area 0

duplex auto

!

interface Ethernet0/1

no shut

ip address 10.10.13.1 255.255.255.0

ip ospf 1 area 0

duplex auto

!

router ospf 1

router-id 10.10.12.1

network 10.10.1.1 0.0.0.0 area 0

network 192.168.1.0 0.0.0.255 area 0

!

copy run star

---------------------------------------

On R2

conf terminal

interface Loopback0

ip address 10.10.2.2 255.255.255.255

!

interface Loopback1

ip address 192.168.2.2 255.255.255.0

!

interface Ethernet0/0

no shut

ip address 10.10.12.2 255.255.255.0

ip ospf priority 255

ip ospf 1 area 0

duplex auto

!

interface Ethernet0/2

no shut

ip address 10.10.23.2 255.255.255.0

ip ospf priority 255

ip ospf 1 area 0

duplex auto

!

router ospf 1

network 10.10.2.2 0.0.0.0 area 0

network 192.168.2.0 0.0.0.255 area 0

!

copy runs start

-----------------------

On R3

conf ter

interface Loopback0

ip address 10.10.3.3 255.255.255.255

!

interface Loopback1

ip address 192.168.3.3 255.255.255.0

!

interface Ethernet0/1

no shut

ip address 10.10.13.3 255.255.255.0

ip ospf 1 area 0

duplex auto

!

interface Ethernet0/2

no shut

ip address 10.10.23.3 255.255.255.0

ip ospf 1 area 0

duplex auto

!

router ospf 1

network 10.10.3.3 0.0.0.0 area 0

network 192.168.3.0 0.0.0.255 area 0

!

copy run start

!

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

Answer as below configuration:

conf t

R1(config)#ntp master 1

R2(config)#ntp server 10.1.2.1

Exit

Router#clock set 00:00:00 jan 1 2019

ip dhcp pool TEST

network 10.1.3.0 255.255.255.0

ip dhcp exluded-address 10.1.3.1 10.1.3.10

R3(config)#int e0/3

R3(config)#int e0/2

ip address dhcp

no shut

crypto key generate RSA

1024

Copy run start

To subnet 172.25.0.0/16 to meet the subnet requirements and maximize the number of hosts, you need to determine how many bits you need to borrow from the host portion of the address to create enough subnets for 32 sites. Since 32 is 2^5, you need to borrow 5 bits, which means your new subnet mask will be /21 or 255.255.248.0. To find the second subnet, you need to add the value of the fifth bit (32) to the third octet of the network address (0), which gives you 172.25.32.0/21 as the second subnet. The first usable IP address in this subnet is 172.25.32.1, and the last usable IP address is 172.25.39.254.

To assign the first usable IP address to e0/0 on Sw101, you need to enter the following commands on the device console:

Sw101#configure terminal Sw101(config)#interface e0/0 Sw101(config-if)#ip address 172.25.32.1 255.255.248.0 Sw101(config-if)#no shutdown Sw101(config-if)#end

To assign the last usable IP address to e0/0 on Sw102, you need to enter the following commands on the device console:

Sw102#configure terminal Sw102(config)#interface e0/0 Sw102(config-if)#ip address 172.25.39.254 255.255.248.0 Sw102(config-if)#no shutdown Sw102(config-if)#end

To subnet an IPv6 GUA to meet the subnet requirements and maximize the number of hosts, you need to determine how many bits you need to borrow from the interface identifier portion of the address to create enough subnets for 32 sites. Since 32 is 2^5, you need to borrow 5 bits, which means your new prefix length will be /69 or ffff:ffff:ffff:fff8::/69 (assuming that your IPv6 GUA has a /64 prefix by default). To find the second subnet, you need to add the value of the fifth bit (32) to the fourth hextet of the network address (0000), which gives you xxxx:xxxx:xxxx:0020::/69 as the second subnet (where xxxx:xxxx:xxxx is your IPv6 GUA prefix). The first and last IPv6 addresses in this subnet are xxxx:xxxx:xxxx:0020::1 and xxxx:xxxx:xxxx:0027:ffff:ffff:ffff:fffe respectively.

To assign an IPv6 GUA using a unique 64-bit interface identifier on e0/0 on Sw101, you need to enter the following commands on the device console (assuming that your IPv6 GUA prefix is 2001:db8::/64):

Sw101#configure terminal Sw101(config)#interface e0/0 Sw101(config-if)#ipv6 address 2001:db8::20::1/69 Sw101(config-if)#no shutdown Sw101(config-if)#end

To assign an IPv6 GUA using a unique 64-bit interface identifier on e0/0 on Sw102, you need to enter the following commands on the device console (assuming that your IPv6 GUA prefix is 2001:db8::/64):

Sw102#configure terminal Sw102(config)#interface e0/0 Sw102(config-if)#ipv6 address 2001:db8::27::fffe/69 Sw102(config-if)#no shutdown Sw102(config-if)#end

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

Answer B is the technically correct selection. A router forwards packets between different IP networks. If PC-A and PC-B are in separate subnets, the router receives the frame, checks the destination IP, chooses a route, rewrites Layer 2 addressing, and forwards the packet. This aligns with Cisco CCNA 200-301 v1.1 because the exam blueprint requires engineers to recognize operational behaviour from configuration symptoms and topology requirements. A Layer 2 switch forwards within a VLAN and does not route between IP subnets by itself. Treat the distractors carefully: most are real Cisco terms, but they solve a different problem or operate at a different layer. The selected answer is the one that would be used by an engineer on the device or in the design to produce the outcome stated in the question.

The verified answer is the displayed drag-and-drop mapping. IPv6 address types are identified by prefix and scope. Global unicast is Internet-routable, unique local is private-like, link-local stays on the local link, and multicast reaches a group. Cisco CCNA 200-301 v1.1 places this skill in Network Fundamentals, where the exam expects a working understanding of how the feature behaves on real Cisco networks, not just a memorized command. Correct mapping depends on recognizing prefix ranges such as 2000::/3, FC00::/7, FE80::/10, and FF00::/8. In production, this distinction matters because a misapplied command or design choice usually creates an outage, a security gap, or unnecessary troubleshooting noise. The correct choice matches the control-plane, data-plane, wireless, security, or services behaviour described in the scenario and should be preferred over options that merely sound related.

Answer as below configuration:

On R2:

Enable

Conf t

Ip route 192.168.1.0 255.255.255.0 10.10.31.1

On R1:

Enable

Conf t

Ip route 0.0.0.0 0.0.0.0 10.10.13.3

On R2

Ip route 172.20.20.128 255.255.255.128 e0/2

Ip route 172.20.20.128 255.255.255.128 e0/1

On R1

Ip route 192.168.0.0 255.255.255.0 e0/1

Ip route 192.168.0.0 255.255.255.0 10.10.12.2 3

Save all configurations after every router from anyone of these command

Do wr

Or

Copy run start

Cisco CCNA 200-301 v1.1 expects these items to be matched by function, protocol layer, scope, and operational role rather than by keyword similarity. The reliable method is to identify what each item actually does in a Cisco network: whether it forwards traffic, manages a device, secures access, assigns addressing, identifies a resource, or carries control information. Distractors in this format are usually valid networking terms placed under the wrong category. That is why the retained mapping is important; it keeps protocol behavior, device function, and service purpose aligned. In a real network, mixing these concepts leads to broken routing, failed wireless access, insecure management, or automation calls aimed at the wrong interface. The mapping shown in the document is therefore retained as the Cisco-consistent answer for this item.

Unlike autonomous access points, lightweight access points require a WLC to implement remote firmware updates.. Cisco wireless design separates RF behavior, client authentication, encryption, AP operating mode, and controller management. A WLC centralizes WLAN configuration and AP control, while lightweight APs use CAPWAP to register and exchange control/data information with the controller. Security choices such as WPA2/AES and WPA3/SAE are not interchangeable with older mechanisms such as WEP, TKIP, or RC4. RF questions also depend on channel planning: adjacent cells should avoid overlapping channels, and 5-GHz preference features reduce congestion in the 2.4-GHz band. The incorrect options generally confuse AP mode, authentication, encryption, or controller responsibilities. Cisco CCNA 200-301 v1.1 includes these items because wireless failures often come from using the right-looking feature in the wrong part of the WLAN design. The selected answer is the Cisco-consistent configuration or behavior for this wireless scenario.

access list 100 deny tcp host 172.16.1.33 any eq 22access list 100 permit ip any anyline vty 0 15access-class 100 in. Cisco wireless design separates RF behavior, client authentication, encryption, AP operating mode, and controller management. A WLC centralizes WLAN configuration and AP control, while lightweight APs use CAPWAP to register and exchange control/data information with the controller. Security choices such as WPA2/AES and WPA3/SAE are not interchangeable with older mechanisms such as WEP, TKIP, or RC4. RF questions also depend on channel planning: adjacent cells should avoid overlapping channels, and 5-GHz preference features reduce congestion in the 2.4-GHz band. The incorrect options generally confuse AP mode, authentication, encryption, or controller responsibilities. Cisco CCNA 200-301 v1.1 includes these items because wireless failures often come from using the right-looking feature in the wrong part of the WLAN design. The selected answer is the Cisco-consistent configuration or behavior for this wireless scenario.

to uniquely identify each client application. Cisco wireless design separates RF behavior, client authentication, encryption, AP operating mode, and controller management. A WLC centralizes WLAN configuration and AP control, while lightweight APs use CAPWAP to register and exchange control/data information with the controller. Security choices such as WPA2/AES and WPA3/SAE are not interchangeable with older mechanisms such as WEP, TKIP, or RC4. RF questions also depend on channel planning: adjacent cells should avoid overlapping channels, and 5-GHz preference features reduce congestion in the 2.4-GHz band. The incorrect options generally confuse AP mode, authentication, encryption, or controller responsibilities. Cisco CCNA 200-301 v1.1 includes these items because wireless failures often come from using the right-looking feature in the wrong part of the WLAN design. The selected answer is the Cisco-consistent configuration or behavior for this wireless scenario.

Configuration templates and testing can be built into implementation, which increases the success rate of a network change.. Cisco wireless design separates RF behavior, client authentication, encryption, AP operating mode, and controller management. A WLC centralizes WLAN configuration and AP control, while lightweight APs use CAPWAP to register and exchange control/data information with the controller. Security choices such as WPA2/AES and WPA3/SAE are not interchangeable with older mechanisms such as WEP, TKIP, or RC4. RF questions also depend on channel planning: adjacent cells should avoid overlapping channels, and 5-GHz preference features reduce congestion in the 2.4-GHz band. The incorrect options generally confuse AP mode, authentication, encryption, or controller responsibilities. Cisco CCNA 200-301 v1.1 includes these items because wireless failures often come from using the right-looking feature in the wrong part of the WLAN design. The selected answer is the Cisco-consistent configuration or behavior for this wireless scenario.

It floods the frame to all ports except the incoming port.. Layer 2 switching behavior is driven by VLAN membership, MAC learning, trunk encapsulation, STP state, and EtherChannel negotiation. Cisco switches learn source MAC addresses on ingress, flood unknown unicasts within the same VLAN, and forward known unicasts only out the port associated with the destination MAC address. Trunk and EtherChannel questions must be solved on the logical interface and with the correct negotiation protocol: LACP uses active/passive, PAgP uses desirable/auto, and static mode uses on. STP and PortFast questions depend on whether the port is intended for an endpoint or part of the switched topology. The wrong choices usually apply the correct feature to the wrong port type or violate the required negotiation behavior. Cisco CCNA 200-301 v1.1 emphasizes these details because a single incorrect Layer 2 setting can create loops, VLAN leaks, or failed host connectivity. The selected answer matches Cisco switching operation.

2001:db8:1a44:41a4:C081:BFFF:FE4A:1. Routing and redundancy questions are solved by applying longest-prefix match, administrative distance, metrics, and gateway-redundancy behavior in the correct order. Cisco CCNA 200-301 v1.1 includes this under Network Fundamentals, where the expected skill is selecting the feature that actually produces the requested network behavior. The wording normally gives the clue: protocol family, address scope, trunk state, route preference, security mode, API method, or controller role. Incorrect choices point to the wrong next hop, choose the wrong route source, or confuse routing with Layer 2 behavior. In production, choosing the wrong option would typically cause failed client access, a broken route, insecure management, or an automation workflow that targets the wrong interface. The selected answer is the Cisco-consistent behavior for this item.

0.0.0.0. Cisco routing logic is deterministic: a router first matches the most specific destination prefix, then uses administrative distance when competing route sources advertise the same prefix, and finally evaluates the protocol metric when multiple paths remain inside the same routing protocol. First-hop redundancy protocols add a separate default-gateway resiliency function for hosts on a LAN. The other choices in this question either point to the wrong route-selection rule, confuse a protocol metric with administrative distance, or apply a Layer 2 concept where a Layer 3 forwarding decision is required. In production, that mistake would create blackholing, asymmetric routing, or a backup path that never activates. Cisco CCNA 200-301 v1.1 tests this because route selection is fundamental to troubleshooting reachability. The selected answer matches the behavior Cisco routers use when forwarding traffic or maintaining gateway redundancy.

offers link bundling to servers. Cisco routing logic is deterministic: a router first matches the most specific destination prefix, then uses administrative distance when competing route sources advertise the same prefix, and finally evaluates the protocol metric when multiple paths remain inside the same routing protocol. First-hop redundancy protocols add a separate default-gateway resiliency function for hosts on a LAN. The other choices in this question either point to the wrong route-selection rule, confuse a protocol metric with administrative distance, or apply a Layer 2 concept where a Layer 3 forwarding decision is required. In production, that mistake would create blackholing, asymmetric routing, or a backup path that never activates. Cisco CCNA 200-301 v1.1 tests this because route selection is fundamental to troubleshooting reachability. The selected answer matches the behavior Cisco routers use when forwarding traffic or maintaining gateway redundancy.

Cisco CCNA 200-301 v1.1 Network Fundamentals drag-and-drop items test whether each protocol, address type, API action, or infrastructure component is matched to its real function. The correct way to solve these is to classify every item by layer, scope, and operational behavior before matching it. Several distractors are legitimate networking terms, but they are wrong when placed under the wrong protocol family or management model. The retained mapping preserves the Cisco distinctions between TCP and UDP behavior, AAA functions, IPv6 address scopes, device-management approaches, and REST operations. In implementation work, these distinctions matter because applying a feature at the wrong layer or associating a control with the wrong service creates broken configurations and wasted troubleshooting effort. The shown mapping is therefore retained as the verified response.

An interface line has changed status. Cisco routing logic is deterministic: a router first matches the most specific destination prefix, then uses administrative distance when competing route sources advertise the same prefix, and finally evaluates the protocol metric when multiple paths remain inside the same routing protocol. First-hop redundancy protocols add a separate default-gateway resiliency function for hosts on a LAN. The other choices in this question either point to the wrong route-selection rule, confuse a protocol metric with administrative distance, or apply a Layer 2 concept where a Layer 3 forwarding decision is required. In production, that mistake would create blackholing, asymmetric routing, or a backup path that never activates. Cisco CCNA 200-301 v1.1 tests this because route selection is fundamental to troubleshooting reachability. The selected answer matches the behavior Cisco routers use when forwarding traffic or maintaining gateway redundancy.