Cisco 200-301 Questions and Answers

Question 001 IP connectivity and OSPF are preconfigured on all devices where necessary. Do not make any changes to the IP addressing or OSPF. The company policy uses connected interfaces and next hops when configuring static routes except for load balancing or redundancy without floating static. Connectivity must be established between subnet 172.20.20.128/25 on the Internet, and the LAN at 192.168.0.0/24 connected to SW1. 1. Configure reachability to the switch SW1 LAN subnet in router R2. 2. Configure default reachability to the Internet subnet in router R1. 3. Configure a single static route in router R2 to reach the Internet subnet considering both redundant links between routers R1 and R2. Ad default route is NOT allowed on router R2. 4. Configure a static route in router R1 towards the switch SW1 LAN subnet where the primary link must be through Gi 0/0/1 and the backup link must be through GI 0/0/2 using a floating route. Use the minimal administrative distance value when required.   Answer 001: 1. Configure reachability to the switch SW1 LAN subnet in router R2. enable configure terminal ! ip route 192.168.0.0 255.255.255.0 10.10.31.1 end copy running-config startup-config R2# ping 192.168.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms 2. Configure default reachability to the Internet subnet in router R1. enable configure terminal ! ip route 0.0.0.0 0.0.0.0 10.10.13.3 end copy running-config startup-config R1#ping 172.20.20.129 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.20.20.129, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms 3. Configure a single static route in router R2 to reach the Internet subnet considering both redundant links between routers R1 and R2. A default route is NOT allowed on router R2. enable configure terminal ! ip route 172.20.20.128 255.255.255.128 Gi 0/0/1 ip route 172.20.20.128 255.255.255.128 Gi 0/0/2 end copy running-config startup-config asymmetrical routing occurs – misses alternate pings   4. Configure a static route in router R1 towards the switch SW1 LAN subnet where the primary link must be through Gi 0/0/1 and the backup link must be through GI 0/0/2 using a floating route. Use the minimal administrative distance value when required. enable configure terminal ! ip route 192.168.0.0 255.255.255.0 Gi 0/0/1 (default AD = 1 ) ip route 192.168.0.0 255.255.255.0 Gi 0/0/1 2 (AD = 2 ) end copy running-config startup-config R1# ping 192.168.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms Note: At R1, here is the routing table with Gi 0/0/1 up: R1# show ip route Gateway of last resort is 10.10.13.3 to network 0.0.0.0 10.0.0.0/8 is variably subnetted, 7 subnets, 3 masks C 10.10.1.1/32 is directly connected, Loopback0 C 10.10.12.0/25 is directly connected, GigabitEthernet0/0/1 L 10.10.12.1/32 is directly connected, GigabitEthernet0/0/1 C 10.10.12.128/25 is directly connected, GigabitEthernet0/0/2 L 10.10.12.129/32 is directly connected, GigabitEthernet0/0/2 C 10.10.13.0/24 is directly connected, GigabitEthernet0/0/0 L 10.10.13.1/32 is directly connected, GigabitEthernet0/0/0 S 192.168.0.0/24 is directly connected, GigabitEthernet0/0/1 S* 0.0.0.0/0 [1/0] via 10.10.13.3 R1# show ip route 192.168.0.1 Routing entry for 192.168.0.0/24 Known via "static", distance 1, metric 0 (connected) Routing Descriptor Blocks: * directly connected, via GigabitEthernet0/0/1 Route metric is 0, traffic share count is 1 - And at R1, here is the routing table with Gi 0/0/1 down: R1# show ip route Gateway of last resort is 10.10.13.3 to network 0.0.0.0 10.0.0.0/8 is variably subnetted, 5 subnets, 3 masks C 10.10.1.1/32 is directly connected, Loopback0 C 10.10.12.128/25 is directly connected, GigabitEthernet0/0/2 L 10.10.12.129/32 is directly connected, GigabitEthernet0/0/2 C 10.10.13.0/24 is directly connected, GigabitEthernet0/0/0 L 10.10.13.1/32 is directly connected, GigabitEthernet0/0/0 S 192.168.0.0/24 is directly connected, GigabitEthernet0/0/2 S* 0.0.0.0/0 [1/0] via 10.10.13.3 R1# show ip route 192.168.0.1 Routing entry for 192.168.0.0/24 Known via "static", distance 2, metric 0 (connected) Routing Descriptor Blocks: * directly connected, via GigabitEthernet0/0/2 Route metric is 0, traffic share count is 1 Question 002 Connectivity between three routers has been established an IP services must be configured in the order presented to complete the implementation Tasks assigned including the configuration of NAT, NTP, DHCP, and SSH services. 1. All traffic sent from R3 to the R1 Loopback address must be configured for NAT on R2. All source addresses must be translated from R3 to the Ip address of Gi 0/0/0 on R2, while using only a standard access list named NAT. To verify, a ping must be successful to the R1 Loopback address sourced from R3. Do Not use NVI NAT configuration. 2. Configure R1 as an NTP server and R2 as a client, not as a peer, using the IP address of the R1 Gi 0/0/1 interface. Set the clock on the NTP server for midnight on January 1, 2019. 3. Configure R1 as a DHCP server for the network 10.1.3.0 /24 in a pool named TEST. Using a single command, exclude addresses 1-10 from the range. Interface Gi 0/0/0 on R3 must be issued the IP address of 10.1.3.11 via DHCP. 4. Configure SSH connectivity from R1 to R3, while excluding access via other remote connection protocols. Access for user root and password Cisco must be set on router R3 using RSA and 1024 bits. Verify connectivity using an SSH session from router R1 using a destination address of 10.1.3.11. Do NOT modify console access or line numbers to accomplish this task.   Answer 002: 1. All traffic sent from R3 to the R1 Loopback address must be configured for NAT on R2. All source addresses must be translated from R3 to the IP address of Gi 0/0/0 on R2, while using only a standard access list named NAT. To verify, a ping must be successful to the R1 Loopback address sourced from R3. Do Not use NVI NAT configuration. - Implement NAT at R2. All traffic from R3 to R1’s Loopback (192.168.1.1) is translated. The outside address is R2’s Gi 0/0/0 (10.1.2.2) R2 enable configure terminal ! ip nat inside source list NAT interface GigabitEthernet 0/0/0 overload ! ip access-list standard NAT remark IP Addresses to be changed by NAT = R3 addresses permit 10.2.3.3 0.0.0.0 permit 192.168.3.1 0.0.0.0 permit 192.168.3.1 0.0.0.0 ! interface GigabitEthernet 0/0/0 ip nat outside ! interface GigabitEthernet 0/0/1 ip nat inside ! end copy running-config startup-config At R3: R3# ping 192.168.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds: !!!!! At R1: R1# debug ip icmp ICMP packet debugging is on R1# ICMP: echo reply sent, src 192.168.1.1, dst 10.1.2.2 ICMP: echo reply sent, src 192.168.1.1, dst 10.1.2.2 ICMP: echo reply sent, src 192.168.1.1, dst 10.1.2.2 ICMP: echo reply sent, src 192.168.1.1, dst 10.1.2.2 ICMP: echo reply sent, src 192.168.1.1, dst 10.1.2.2