Tactics to objectif 18-135 ou 70-300

Our Cisco 300-135 exam demos include two versions: Pdf(printable version) and Test Serp(software version). They are quite convenient and helpful for you to make entire preparation for the 300-135 genuine exam. Our Pdf or even Testing engine preparation materials regarding Cisco Cisco certification exam contain everything thats precise and logical which you need in the exam. You can freely download the Pdf files and analyze engine on your own PC after purchase. Make entire use of the comprehensive Cisco Cisco practice questions which are tested through our certified experts before publishing and pass your 300-135 exam successfully at 1st attempt.

2021 Dec ccnp tshoot 300-135 topology:

Q21. - (Topic 10)

The implementations group has been using the test bed to do a ‘proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing scheme, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address.

Use the supported commands to isolated the cause of this fault and answer the following questions.

The fault condition is related to which technology?

A. BGP

B. NTP

C. IP NAT

D. IPv4 OSPF Routing

E. IPv4 OSPF Redistribution

F. IPv6 OSPF Routing

G. IPv4 layer 3 security

Answer: C

Explanation:

On R1 we need to add the client IP address for reachability to server to the access list that is used to specify which hosts get NATed.

Topic 11, Ticket 6 : R1 ACL

Topology Overview (Actual Troubleshooting lab design is for below network design)

. Client Should have IP 10.2.1.3

. EIGRP 100 is running between switch DSW1 & DSW2

. OSPF (Process ID 1) is running between R1, R2, R3, R4

. Network of OSPF is redistributed in EIGRP

. BGP 65001 is configured on R1 with Webserver cloud AS 65002

. HSRP is running between DSW1 & DSW2 Switches

The company has created the test bed shown in the layer 2 and layer 3 topology exhibits.

This network consists of four routers, two layer 3 switches and two layer 2 switches.

In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1.

DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary.

R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP's network. Because the company's address space is in the private range.

R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside (209.65.0.0/24) network.

ASW1 and ASW2 are layer 2 switches.

NTP is enabled on all devices with 209.65.200.226 serving as the master clock source.

The client workstations receive their IP address and default gateway via R4's DHCP server.

The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2.

In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6.

DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE.

The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistribution is enabled where necessary.

Recently the implementation group has been using the test bed to do a ‘proof-of-concept' on several implementations. This involved changing the configuration on one or more of the devices. You will be presented with a series of trouble tickets related to issues introduced during these configurations.

Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and solution.

Each ticket has 3 sub questions that need to be answered & topology remains same.

Question-1 Fault is found on which device,

Question-2 Fault condition is related to,

Question-3 What exact problem is seen & what needs to be done for solution

Client is unable to ping IP 209.65.200.241…

Solution

Steps need to follow as below:-

. When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4

. Ipconfig ----- Client will be receiving IP address 10.2.1.3

. IP 10.2.1.3 will be able to ping from R4 , R3, R2, R1

. Look for BGP Neighbourship

. Sh ip bgp summary ----- State of BGP will be in active state. This means connectivity issue between serial

. Check for running config. i.e sh run --- over here check for access-list configured on interface as BGP is down (No need to check for NAT configuration as its configuration should be right as first need to bring BGP up)

. In above snapshot we can see that access-list of edge_security on R1 is not allowing wan IP network

. Change required: On R1, we need to permit IP 209.65.200.222/30 under the access list.

Q22. - (Topic 15)

Use the supported commands to isolated the cause of this fault and answer the following questions.

The fault condition is related to which technology?

A. Under the global configuration mode enter no access-list 10 command.

B. Under the global configuration mode enter no access-map vlan 10 command.

C. Under the global configuration mode enter no vlan access-map test1 10 command.

D. Under the global configuration mode enter no vlan filter test1 vlan-list 10 command.

Answer: C

Explanation:

On DSW1, VALN ACL, Need to delete the VLAN access-map test1 whose action is to drop access-list 10; specifically 10.2.1.3

Q23. - (Topic 1)

Refer to the exhibit.

How would you confirm on R1 that load balancing is actually occurring on the default-network (0.0.0.0)?

A. Use ping and the show ip route command to confirm the timers for each default network resets to 0.

B. Load balancing does not occur over default networks; the second route will only be used for failover.

C. Use an extended ping along with repeated show ip route commands to confirm the gateway of last resort address toggles back and forth.

D. Use the traceroute command to an address that is not explicitly in the routing table.

Answer: D

Q24. - (Topic 18)

The implementations group has been using the test bed to do a ‘proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing schemes, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address.

Use the supported commands to isolate the cause of this fault and answer the following question.

The fault condition is related to which technology?

A. NTP

B. IP DHCP Server

C. Ipv4 OSPF Routing

D. Ipv4 EIGRP Routing.

E. Ipv4 Route Redistribution.

F. Ipv6 RIP Routing

G. Ipv6 OSPF Routing

H. Ipv4 and Ipv6 Interoperability

I. Ipv4 layer 3 security.

Answer: B

Explanation:

On R4 the DHCP IP address is not allowed for network 10.2.1.0/24 which clearly shows the problem lies on R4 & the problem is with DHCP

Topic 19, Ticket 14: IPv6 Routing Issue 1

Topology Overview (Actual Troubleshooting lab design is for below network design)

-Client Should have IP 10.2.1.3

-EIGRP 100 is running between switch DSW1 & DSW2

-OSPF (Process ID 1) is running between R1, R2, R3, R4

-Network of OSPF is redistributed in EIGRP

-BGP 65001 is configured on R1 with Webserver cloud AS 65002

-HSRP is running between DSW1 & DSW2 Switches

The company has created the test bed shown in the layer 2 and layer 3 topology exhibits.

This network consists of four routers, two layer 3 switches and two layer 2 switches.

In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1.

DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary.

R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP's network. Because the company's address space is in the private range.

R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside (209.65.0.0/24) network.

ASW1 and ASW2 are layer 2 switches.

NTP is enabled on all devices with 209.65.200.226 serving as the master clock source.

The client workstations receive their IP address and default gateway via R4's DHCP server.

The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2.

In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6.

DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE.

The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistrution is enabled where necessary.

Recently the implementation group has been using the test bed to do a ‘proof-of-concept' on several implementations. This involved changing the configuration on one or more of the devices.

You will be presented with a series of trouble tickets related to issues introduced during these configurations.

Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and solution.

Each ticket has 3 sub questions that need to be answered & topology remains same.

Question-1 Fault is found on which device,

Question-2 Fault condition is related to,

Question-3 What exact problem is seen & what needs to be done for solution

===============================================================================

Q25. - (Topic 12)

Use the supported commands to isolated the cause of this fault and answer the following questions.

What is the solution to the fault condition?

A. In Configuration mode, using the interface range Fa 1/0/1 – 2, then no switchport port-security interface configuration commands. Then in exec mode clear errdisable interface fa 1/01 – 2 vlan 10 command

B. In Configuration mode, using the interface range Fa 1/0/1 – 2, then no switchport port-security, followed by shutdown, no shutdown interface configuration commands.

C. In Configuration mode, using the interface range Fa 1/0/1 – 2, then no switchport port-security interface configuration commands.

D. In Configuration mode, using the interface range Fa 1/0/1 – 2, then no switchport port-security interface configuration commands. Then in exec mode clear errdisable interface fa 1/0/1, then clear errdisable interface fa 1/0/2 commands.

Answer: B

Explanation:

On ASW1, we need to remove port-security under interface fa1/0/1 & fa1/0/2.

Reference: http://www.cisco.com/en/US/tech/ABC389/ABC621/technologies_tech_note09186a00806c d87b.shtml

Improved bes 516-300-s 135-d-pu-10:

Q26. - (Topic 17)

The implementations group has been using the test bed to do a ‘proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing schemes, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened DSW1 will not become the active router for HSRP group 10.

Use the supported commands to isolated the cause of this fault and answer the following questions.

What is the solution to the fault condition?

A. Under the interface vlan 10 configuration enter standby 10 preempt command.

B. Under the track 1 object configuration delete the threshold metric up 1 down 2 command and enter the threshold metric up 61 down 62 command.

C. Under the track 10 object configuration delete the threshold metric up 61 down 62 command and enter the threshold metric up 1 down 2 command.

D. Under the interface vlan 10 configuration delete the standby 10 track1 decrement 60 command and enter the standby 10 track 10 decrement 60 command.

Answer: D

Explanation:

On DSW1, related to HSRP, under VLAN 10 change the given track 1 command to instead use the track 10 command.

Q27. - (Topic 8)

Use the supported commands to isolated the cause of this fault and answer the following questions.

What is the solution to the fault condition?

A. Enable OSPF authentication on the s0/0/0 interface using the ip ospf authentication message-digest command

B. Enable OSPF routing on the s0/0/0 interface using the network 10.1.1.0 0.0.0.255 area 12 command.

C. Enable OSPF routing on the s0/0/0 interface using the network 209.65.200.0 0.0.0.255 area 12 command.

D. Redistribute the BGP route into OSPF using the redistribute BGP 65001 subnet command.

Answer: A

Explanation:

On R1, for IPV4 authentication of OSPF the command is missing and required to configure------ ip ospf authentication message-digest

Topic 9, Ticket 4 : BGP Neighbor

Topology Overview (Actual Troubleshooting lab design is for below network design)

. Client Should have IP 10.2.1.3

. EIGRP 100 is running between switch DSW1 & DSW2

. OSPF (Process ID 1) is running between R1, R2, R3, R4

. Network of OSPF is redistributed in EIGRP

. BGP 65001 is configured on R1 with Webserver cloud AS 65002

. HSRP is running between DSW1 & DSW2 Switches

The company has created the test bed shown in the layer 2 and layer 3 topology exhibits.

This network consists of four routers, two layer 3 switches and two layer 2 switches.

In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1.

DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary.

R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP's network. Because the company's address space is in the private range.

R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside (209.65.0.0/24) network.

ASW1 and ASW2 are layer 2 switches.

NTP is enabled on all devices with 209.65.200.226 serving as the master clock source.

The client workstations receive their IP address and default gateway via R4's DHCP server.

The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2.

In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6.

DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE.

The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistrution is enabled where necessary.

Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and solution.

Each ticket has 3 sub questions that need to be answered & topology remains same.

Question-1 Fault is found on which device,

Question-2 Fault condition is related to,

Question-3 What exact problem is seen & what needs to be done for solution

Client is unable to ping IP 209.65.200.241

Solution

Steps need to follow as below:-

. When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4

ipconfig ----- Client will be receiving IP address 10.2.1.3

. IP 10.2.1.3 will be able to ping from R4 , R3, R2, R1

. Look for BGP Neighbourship

Sh ip bgp summary ----- No O/P will be seen

. Check for interface IP & ping IP 209.65.200.225 ---- Reply will be received from Webserver interface

. Look for peering IP address via sh run on R1 interface serial 0/0/1

. Since we are receiving icmp packets from Webserver interface on R1 so peering IP address under router BGP is configured wrong IP but with correct AS nos.

. Change required: On R1 under router BGP Change neighbor 209.56.200.226 remote-as 65002 statement to neighbor 209.65.200.226 remote-as 65002

Q28. - (Topic 2)

A customer network engineer has made configuration changes that have resulted in some loss of connectivity. You have been called in to evaluate a switch network and suggest resolutions to the problems.

Refer to the topology.

SW1 Switch Management IP address is not pingable from SW4. What could be the issue?

A. Management VLAN not allowed in the trunk links between SW1 and SW4

B. Management VLAN not allowed in the trunk links between SW1 and SW2

C. Management VLAN not allowed in the trunk link between SW2 and SW4

D. Management VLAN ip address on SW4 is configured in wrong subnet

E. Management VLAN interface is shutdown on SW4

Answer: D

Explanation:

In the network, VLAN 300 is called the Management VLAN. Based on the configurations shown below, SW1 has VLAN 300 configured with the IP address of 192.168.10.1/24, while on SW4 VLAN 300 has an IP address of 192.168.100.4/24, which is not in the same subnet.

Q29. - (Topic 1)

Which three features are benefits of using GRE tunnels in conjunction with IPsec for building siteto-site VPNs? (Choose three.)

A. allows dynamic routing over the tunnel

B. supports multi-protocol (non-IP) traffic over the tunnel

C. reduces IPsec headers overhead since tunnel mode is used

D. simplifies the ACL used in the crypto map

E. uses Virtual Tunnel Interface (VTI) to simplify the IPsec VPN configuration

Answer: A,B,D

Q30. - (Topic 20)

The implementation group has been using the test bed to do an IPv6 'proof-of-concept1. After several changes to the network addressing and routing schemes, a trouble ticket has been opened indicating that the loopback address on R1 (2026::111:1) is not able to ping the loopback address on DSW2 (2026::102:1).

Use the supported commands to isolate the cause of this fault and answer the following question.

What is the solution to the fault condition?

A. Under the interface Tunnel34 configuration enter the ipv6 ospf 6 area 34 command.

B. Under the interface Loopback6 configuration enter the ipv6 ospf 6 area 34 command.

C. Under the interface Serial0/0/0.34 configuration enter the ipv6 ospf 6 area 34 command.

D. Under ipv6 router ospf 6 configuration enter the redistribute rip RIP_ZONE include-connected command.

Answer: D

Explanation:

As explained earlier, the problem is with route redistribution on R4 of not redistributing RIP routes into OSPF for IPV6.

Topic 21, Ticket 16: IPv6 Routing Issue 3

Topology Overview (Actual Troubleshooting lab design is for below network design)

-Client Should have IP 10.2.1.3

-EIGRP 100 is running between switch DSW1 & DSW2

-OSPF (Process ID 1) is running between R1, R2, R3, R4

-Network of OSPF is redistributed in EIGRP

-BGP 65001 is configured on R1 with Webserver cloud AS 65002

-HSRP is running between DSW1 & DSW2 Switches

The company has created the test bed shown in the layer 2 and layer 3 topology exhibits.

This network consists of four routers, two layer 3 switches and two layer 2 switches.

In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1.

DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary.

R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP's network. Because the company's address space is in the private range.

R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside (209.65.0.0/24) network.

ASW1 and ASW2 are layer 2 switches.

NTP is enabled on all devices with 209.65.200.226 serving as the master clock source.

The client workstations receive their IP address and default gateway via R4's DHCP server.

The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2.

In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6.

DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE.

The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistrution is enabled where necessary.

Recently the implementation group has been using the test bed to do a ‘proof-of-concept' on several implementations. This involved changing the configuration on one or more of the devices.

You will be presented with a series of trouble tickets related to issues introduced during these configurations.

Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and solution.

Each ticket has 3 sub questions that need to be answered & topology remains same.

Question-1 Fault is found on which device,

Question-2 Fault condition is related to,

Question-3 What exact problem is seen & what needs to be done for solution

===============================================================================

2021 Dec ccnp tshoot 300-135 topology:

Improved bes 516-300-s 135-d-pu-10:

To see all sample questions go to: 300-135 test prep

Related 300-135 posts: