Home Vendors New Files TQB Simulator Upload Files
Cisco Microsoft VMware Oracle Checkpoint IBM Exin RedHat ECCouncil PMI

Download Cisco.300-420.Pass4Sure.2020-01-09.25q.tqb

Vendor: Cisco
Exam Code: 300-420
Exam Name: Designing Cisco Enterprise Networks (300-420 ENSLD)
Date: Jan 09, 2020
File Size: 3 MB
Download Exam
Taurus Exam Simulator Taurus Exam Simulator Taurus Exam Simulator Taurus Exam Simulator Taurus Exam Simulator

Demo Questions

Question 1
Instructions
The main screen consists of two parts; the Main scenario and the Topology tabs. The main scenario describes TSHOOT.com test bed. The Topology tabs allow you to display the appropriate and select the trouble ticket.
To complete the item, you will first need to familiarize yourself with the TSHOOT.com test bed by clicking on the master scenario first and then the topologies tabs. Once you are familiar with the test bed and the topologies, you should start evaluating the trouble ticket. You will be presented with a Trouble Ticket scenario that will describe the fault condition. You will need to determine on which device the fault condition is located, to which technology the fault condition is related, and the solution to each trouble ticket. This will be done by answering three questions.
Ticket Selection
To begin, click on the Ticket on the Topology tabs.
Please note. Some of the questions will require you to use the scroll bar to see all options.
Fault Isolation
Read the ticket scenario to understand the fault condition.
Open the appropriate topology, based upon the ticket scenario.
Open the console of the desired device by clicking on that device in the topology, based upon your troubleshooting methodology.
Use the supported show, ping and trace commands to begin your fault isolation process.
Move to other devices as need by clicking on those devices within the topology.
Fault Identification
The trouble ticket will include three questions that you will need to answer:
  1. Which device contains the fault
  2. Which technology the fault condition is related to
  3. What is the solution to the issue
To advance to the next question within the ticket click on “Next Question”.
When you click “DONE”, the trouble ticket will turn RED and will no longer be accessible.
You may also use the “Previous Question” button to review questions within that specific ticket.
To complete a trouble ticket, answer all three questions and click “DONE”. This will store your response to the questions. Do not click on “DONE” unless you have answered all questions within the ticket.
Item Completion
Click the NEXT button on the bottom of the screen once a ticket is RED. This action moves you to the next item.
Scenario
The company has created the test bed network 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 the outside (209.65.200.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.
  
The implementation 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, and FHRP services, 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 questions. 
On which device is the fault condition located?
  1. R1
  2. R2
  3. R3
  4. R4
  5. DSW1
  6. DSW2
  7. ASW1
  8. ASW2
Correct answer: G
Explanation:
Steps need to follow as below:-1.When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4Ipconfig ----- Client will be getting 169.X.X.X2.On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IPaddress 10.2.1.0/24Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2====================================================interface FastEthernet1/0/1switchport mode accessswitchport access vlan 10interface FastEthernet1/0/2switchport mode accessswitchport access vlan 10====================================================3.We need to check on ASW 1 trunk port the trunk Po13 & Po23 were receiving VLAN 20 &200 but not VLAN 10 so that switch could not get DHCP IP address and was failing to reach IPaddress of Internet4. Change required:On ASW1 below change is required for switch-to-switch connectivity..int range portchannel13,portchannel23switchport trunk allowed vlan noneswitchport trunk allowed vlan 10,200
Steps need to follow as below:-1.When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4Ipconfig ----- Client will be getting 169.X.X.X2.On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IPaddress 10.2.1.0/24Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2====================================================interface FastEthernet1/0/1switchport mode accessswitchport access vlan 10interface FastEthernet1/0/2switchport mode accessswitchport access vlan 10====================================================
3.We need to check on ASW 1 trunk port the trunk Po13 & Po23 were receiving VLAN 20 &200 but not VLAN 10 so that switch could not get DHCP IP address and was failing to reach IPaddress of Internet4. 
Change required:
On ASW1 below change is required for switch-to-switch connectivity..int range portchannel13,portchannel23switchport trunk allowed vlan noneswitchport trunk allowed vlan 10,200
Question 2
Instructions
The main screen consists of two parts; the Main scenario and the Topology tabs. The main scenario describes TSHOOT.com test bed. The Topology tabs allow you to display the appropriate and select the trouble ticket.
To complete the item, you will first need to familiarize yourself with the TSHOOT.com test bed by clicking on the master scenario first and then the topologies tabs. Once you are familiar with the test bed and the topologies, you should start evaluating the trouble ticket. You will be presented with a Trouble Ticket scenario that will describe the fault condition. You will need to determine on which device the fault condition is located, to which technology the fault condition is related, and the solution to each trouble ticket. This will be done by answering three questions.
Ticket Selection
To begin, click on the Ticket on the Topology tabs.
Please note. Some of the questions will require you to use the scroll bar to see all options.
Fault Isolation
Read the ticket scenario to understand the fault condition.
Open the appropriate topology, based upon the ticket scenario.
Open the console of the desired device by clicking on that device in the topology, based upon your troubleshooting methodology.
Use the supported show, ping and trace commands to begin your fault isolation process.
Move to other devices as need by clicking on those devices within the topology.
Fault Identification
The trouble ticket will include three questions that you will need to answer:
  1. Which device contains the fault
  2. Which technology the fault condition is related to
  3. What is the solution to the issue
To advance to the next question within the ticket click on “Next Question”.
When you click “DONE”, the trouble ticket will turn RED and will no longer be accessible.
You may also use the “Previous Question” button to review questions within that specific ticket.
To complete a trouble ticket, answer all three questions and click “DONE”. This will store your response to the questions. Do not click on “DONE” unless you have answered all questions within the ticket.
Item Completion
Click the NEXT button on the bottom of the screen once a ticket is RED. This action moves you to the next item.
Scenario
The company has created the test bed network 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 the outside (209.65.200.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.
  
The implementation 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, and FHRP services, 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 questions. 
The fault condition is related to which technology?
  1. NTP
  2. Switch-to-Switch Connectivity
  3. Loop Prevention
  4. Access Vlans
  5. Port Security
  6. VLAN ACL / Port ACL
  7. Switch Virtual Interface
Correct answer: B
Explanation:
Steps need to follow as below:-1.When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4Ipconfig ----- Client will be getting 169.X.X.X2.On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IPaddress 10.2.1.0/24Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2====================================================interface FastEthernet1/0/1switchport mode accessswitchport access vlan 10interface FastEthernet1/0/2switchport mode accessswitchport access vlan 10====================================================3.We need to check on ASW 1 trunk port the trunk Po13 & Po23 were receiving VLAN 20 &200 but not VLAN 10 so that switch could not get DHCP IP address and was failing to reach IPaddress of Internet4. Change required:On ASW1 below change is required for switch-to-switch connectivity..int range portchannel13,portchannel23switchport trunk allowed vlan noneswitchport trunk allowed vlan 10,200
Steps need to follow as below:-1.When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4Ipconfig ----- Client will be getting 169.X.X.X2.On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IPaddress 10.2.1.0/24Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2====================================================interface FastEthernet1/0/1switchport mode accessswitchport access vlan 10interface FastEthernet1/0/2switchport mode accessswitchport access vlan 10====================================================
3.We need to check on ASW 1 trunk port the trunk Po13 & Po23 were receiving VLAN 20 &200 but not VLAN 10 so that switch could not get DHCP IP address and was failing to reach IPaddress of Internet4. 
Change required:
On ASW1 below change is required for switch-to-switch connectivity..int range portchannel13,portchannel23switchport trunk allowed vlan noneswitchport trunk allowed vlan 10,200
Question 3
Instructions
The main screen consists of two parts; the Main scenario and the Topology tabs. The main scenario describes TSHOOT.com test bed. The Topology tabs allow you to display the appropriate and select the trouble ticket.
To complete the item, you will first need to familiarize yourself with the TSHOOT.com test bed by clicking on the master scenario first and then the topologies tabs. Once you are familiar with the test bed and the topologies, you should start evaluating the trouble ticket. You will be presented with a Trouble Ticket scenario that will describe the fault condition. You will need to determine on which device the fault condition is located, to which technology the fault condition is related, and the solution to each trouble ticket. This will be done by answering three questions.
Ticket Selection
To begin, click on the Ticket on the Topology tabs.
Please note. Some of the questions will require you to use the scroll bar to see all options.
Fault Isolation
Read the ticket scenario to understand the fault condition.
Open the appropriate topology, based upon the ticket scenario.
Open the console of the desired device by clicking on that device in the topology, based upon your troubleshooting methodology.
Use the supported show, ping and trace commands to begin your fault isolation process.
Move to other devices as need by clicking on those devices within the topology.
Fault Identification
The trouble ticket will include three questions that you will need to answer:
  1. Which device contains the fault
  2. Which technology the fault condition is related to
  3. What is the solution to the issue
To advance to the next question within the ticket click on “Next Question”.
When you click “DONE”, the trouble ticket will turn RED and will no longer be accessible.
You may also use the “Previous Question” button to review questions within that specific ticket.
To complete a trouble ticket, answer all three questions and click “DONE”. This will store your response to the questions. Do not click on “DONE” unless you have answered all questions within the ticket.
Item Completion
Click the NEXT button on the bottom of the screen once a ticket is RED. This action moves you to the next item.
Scenario
The company has created the test bed network 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 the outside (209.65.200.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.
  
The implementation 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, and FHRP services, 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 questions. 
What is the solution to the fault condition?
  1. In configuration mode, using the interface range port-channel 23, port-channel 24, then configure switchport trunk allowed vlan none followed by switchport trunk allowed vlan 10,20,200 commands.
  2. In configuration mode, using the interface range port-channel 13, port-channel 23, then configure switchport trunk allowed vlan none followed by switchport trunk allowed vlan 10,200 commands.
  3. In configuration mode, using the interface range port-channel 23, port-channel 24, then configure switchport trunk allowed vlan none followed by switchport trunk allowed vlan 10,20, commands.
  4. In configuration mode, using the interface range port-channel 13, port-channel 23, then configure switchport trunk allowed vlan 10,200 followed by interface Fastethernet 1/0/1, then no shutdown commands.
Correct answer: B
Explanation:
Solution Steps need to follow as below:-1.When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4Ipconfig ----- Client will be getting 169.X.X.X2.On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IPaddress 10.2.1.0/24Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2====================================================interface FastEthernet1/0/1switchport mode accessswitchport access vlan 10interface FastEthernet1/0/2switchport mode accessswitchport access vlan 10====================================================3.We need to check on ASW 1 trunk port the trunk Po13 & Po23 were receiving VLAN 20 &200 but not VLAN 10 so that switch could not get DHCP IP address and was failing to reach IPaddress of Internet4. Change required:On ASW1 below change is required for switch-to-switch connectivity..int range portchannel13,portchannel23switchport trunk allowed vlan noneswitchport trunk allowed vlan 10,200
Solution 
Steps need to follow as below:-1.When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4Ipconfig ----- Client will be getting 169.X.X.X2.On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IPaddress 10.2.1.0/24Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2====================================================interface FastEthernet1/0/1switchport mode accessswitchport access vlan 10interface FastEthernet1/0/2switchport mode accessswitchport access vlan 10====================================================
3.We need to check on ASW 1 trunk port the trunk Po13 & Po23 were receiving VLAN 20 &200 but not VLAN 10 so that switch could not get DHCP IP address and was failing to reach IPaddress of Internet4. 
Change required:
On ASW1 below change is required for switch-to-switch connectivity..int range portchannel13,portchannel23switchport trunk allowed vlan noneswitchport trunk allowed vlan 10,200
CONNECT US
EXAM SIMULATOR

How to Open TQB Files?

Use Taurus Exam Simulator to open TQB files

Taurus Exam Simulator


Taurus Exam Simulator for Windows/macOS/Linus

Download

We does not sell or support this software
Taurus Exam Studio
Enjoy a 20% discount on Taurus Exam Studio!

You now have the chance to acquire Exam Studio at a discounted rate of 20%.

Get Now!
-->