200-301 Practice Questions

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

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

!

To configure static routing on R1 to ensure that it prefers the path through R2 to reach only PC1 on R4’s LAN, you need to create a static route for the host 10.0.0.100/8 with a next-hop address of 20.0.0.2, which is the IP address of R2’s interface connected to R1. You also need to assign a lower administrative distance (AD) to this route than the default AD of 1 for static routes, so that it has a higher preference over other possible routes. For example, you can use an AD of 10 for this route. To create this static route, you need to enter the following commands on R1’s console:

R1#configure terminal R1(config)#ip route 10.0.0.100 255.0.0.0 20.0.0.2 10 R1(config)#end

To configure static routing on R1 that ensures that traffic sourced from R1 will take an alternate path through R3 to PC1 in the event of an outage along the primary path, you need to create another static route for the host 10.0.0.100/8 with a next-hop address of 40.0.0.2, which is the IP address of R3’s interface connected to R1. You also need to assign a higher AD to this route than the AD of the primary route, so that it has a lower preference and acts as a backup route. For example, you can use an AD of 20 for this route. This type of static route is also known as a floating static route. To create this static route, you need to enter the following commands on R1’s console:

R1#configure terminal R1(config)#ip route 10.0.0.100 255.0.0.0 40.0.0.2 20 R1(config)#end

To configure default routes on R1 and R3 to the Internet using the least number of hops, you need to create a static route for the network 0.0.0.0/0 with a next-hop address of the ISP’s interface connected to each router respectively. A default route is a special type of static route that matches any destination address and is used when no other specific route is available. The ISP’s interface connected to R1 has an IP address of 10.0.0.4, and the ISP’s interface connected to R3 has an IP address of 50.0.0.4. To create these default routes, you need to enter the following commands on each router’s console:

On R1: R1#configure terminal R1(config)#ip route 0.0.0.0 0.0.0.0 10.0.0.4 R1(config)#end

On R3: R3#configure terminal R3(config)#ip route 0.0.0.0 0.0.0.0 50.0.0.4 R3(config)#end

DNS lets applications use names instead of forcing users and software to work directly with IP addresses. A client can ask for the address associated with a hostname, and DNS returns the resource records needed to reach that service. DNS can also map one name to multiple IP addresses, which supports simple distribution, redundancy, or service design depending on the record type and client behavior. It does not encrypt WAN traffic by default, and it does not secure IP addresses merely by hiding them behind fully qualified domain names. DNS is hierarchical, not flat, which is why the root, top-level domains, authoritative zones, and host records can scale globally. Cisco CCNA 200-301 v1.1 covers DNS under IP Services because name resolution is required for many network operations, including management access, web services, and application connectivity. The two valid roles here are enabling applications to identify resources by name and allowing a hostname to be associated with more than one IP address.

Answer A and B is the technically correct selection. The distribution layer aggregates access-layer switches and often forms the Layer 2 to Layer 3 boundary. It is where routing, summarization, policy, and aggregation commonly occur before traffic moves toward the core. 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. Continuous backbone forwarding is a core-layer focus, and LAN printers attach at the access layer. 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.

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.

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).

A server provides services to clients. In practical network terms, it runs applications or services that workstations request, and it can handle requests from multiple clients at the same time. Examples include web servers, file servers, DNS servers, DHCP servers, authentication servers, and application servers. A server does not have to run the same operating system as other servers to communicate; network protocols provide interoperability. It also does not achieve redundancy only through virtual clustering, and it does not have to be housed solely in a data center dedicated to one client. Cisco CCNA 200-301 v1.1 Network Fundamentals includes endpoint and server roles because engineers must understand what traffic sources and destinations exist on the network. The two correct functions are application/data service delivery and handling simultaneous client requests. That makes B and C correct.

Unused switch ports should not remain active in the default VLAN. The proper hardening approach is to administratively shut them down and move them into an unused access VLAN, often called a parking, black-hole, or unused VLAN. Shutting the port stops an attacker from plugging in and immediately gaining Layer 2 connectivity. Moving the port out of VLAN 1 reduces the impact if someone later enables the port accidentally. EtherChannel is irrelevant because it aggregates links; it does not protect idle user-facing ports. Trunking unused ports is actively dangerous because it could expose multiple VLANs. CDP can disclose device information and is not a protection method for unused ports. Cisco CCNA v1.1 Network Access and Security Fundamentals overlap here: secure access-layer design includes disabling unused interfaces, avoiding the default VLAN for user access, and limiting unintended Layer 2 exposure. Therefore, B and C are the correct operational steps.