Cisco 300-410 Online Practice Questions and Exam Preparation

Cisco 300-410 Online Questions & Answers

• Question 781:

  Refer to the exhibit.

  

  R2 can reach Loopback222, but R1, SW1, and PC1 cannot communicate with 172.16.222.254. R1 and R2 configurations are shown here:

  

  Which EIGRP configuration command resolves the issue?

  A. R1(config-router)# redistribute static
  B. R2(config-router)# redistribute static
  C. R1(config-router)# network 172.16.222.254 0.0.0.0
  D. R1(config-router)# network 172.16.222.254 255.255.255.255
  B. R2(config-router)# redistribute static

• Question 782:

  Refer to the exhibit.

  

  A network administrator is discovering a Cisco Catalyst 9300 and a Cisco WLC 3504 in Cisco DNA Center. The Catalyst 9300 is added successfully. However, the WLC is showing error "uncontactable" when the administrator tries to add if in Cisco DNA Center. Which action discovers WLC in Cisco DNA Center successfully?

  A. Delete the WLC 3504 from Cisco DNA Center and add it to Cisco DNA Center again.
  B. Add the WLC 3504 under the hierarchy of the Catalyst 9300 connected devices.
  C. Copy the .cert file from the Cisco DNA Center on the USB and upload it to the WLC 3504.
  D. Copy the .pem file from the Cisco DNA Center on the USB and upload it to the WLC 3504.
  D. Copy the .pem file from the Cisco DNA Center on the USB and upload it to the WLC 3504.

  ---

  https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109597-csr-chained-certificates-wlc-00.html#anc12

• Question 783:

  Your company has a policy of creating all configurations in text files, checking the files, and then applying the configurations to the devices. Your assistant has presented you with the following partial configuration that she plans to execute on a router:

  interface S0/0/1 ipv6 address 2001:610:FFFF:1::1/64 ipv6 ospf 100 area 0

  ipv6 router ospf 100 router-id 10.1.1.6 The configuration is supposed to accomplish the following: Enable IPv6 routing Assign a router ID Assign an IPv6 address to the interface Place the interface in OSPF area 0

  Which step does this configuration NOT complete?

  A. Enable IPv6 routing
  B. Assign a router ID
  C. Assign an IPv6 address to the interface
  D. Place the interface in OSPF area 0
  A. Enable IPv6 routing

  ---

  The configuration indicates all steps are complete except for globally enabling IPv6 routing. If that had been done, the configuration output would have reflected it under the interface as follows:

  interface S0/0/1

  ipv6 address 2001:610:FFFF:1::1/64

  ipv6 ospf 100 area 0

  ipv6 enable

  ipv6 router ospf 100

  router-id 10.1.1.6

  Prior to configuring OSPFv3 on an interface, it must be enabled globally. OSPFv3 is an OSPF version specific to IPv6. The following commands will globally enable OSPF v3. It will then be reflected by the ipv6 enable statement under the interface when viewing the configuration as shown in the fourth line of the output above.

  Router5(config)# ipv6 unicast-routing

  Router5(config)# ipv6 ospf 100

  Router5(config-rtr)# router-id 10.1.1.6

  The problem is not the router ID. The configuration in the scenario does assign a router ID, as indicated by these lines:

  ipv6 router ospf 100

  router-id 10.1.1.6

  The problem is not the IPv6 address. The configuration does assign an IPv6 address to the interface, as indicated by these lines:

  interface S0/0/1

  ipv6 address2001:610:FFFF:1::1/64

  OSPF area 0 is not the problem. The configuration does place the interface in OSPF area 0, as indicated by these lines:

  interface S0/0/1

  ipv6 ospf 100 area 0

  Objective:

  Layer 3 Technologies

  Sub-Objective:

  Configure and verify OSPF for IPv6

  References:

  Cisco > Implementing OSPF for IPv6 > How to Implement OSPF for IPv6

• Question 784:

  Which of the following does the show ip eigrp topology all-links command display?

  A. Only feasible successors
  B. Only non-feasible successors
  C. Both feasible successors and non-feasible successors
  D. Both successors and feasible successors
  C. Both feasible successors and non-feasible successors

  ---

  The show ip eigrp topology all-links command displays both the feasible successors and the non-feasible successors. Feasible successors refer to backup routes to a particular destination network.

  Routers compute the metric/distance of every route they learn from their EIGRP neighbors. There can be multiple routes to the same destination network. The route with the least metric value to a specific destination network is selected as the best path, or successor, to that network. However, if the successor goes down, the router computes the next best loop-free path to the same destination network, which is called the feasible successor.

  Feasible successors must have a reported (or advertised) distance that is less than the feasible distance, or current best metric. The routes that are neither successors nor feasible successors are called non-feasible successors. The feasible successors and the non-feasible successors can be viewed by running the show ip eigrp topology all-links command. Sample output is shown below:

  

  The router at 172.17.3.1 is directly connected to three networks: 172.25.1.0/24, 172.20.2.0/24, and 172.18.2.0/24. The second network, 172.20.2.0/24, is listed as the source of the successor routes to those networks. The connection to the last network, 172.18.2.0/4, can deduced by the fact that the local router uses the Serial1 interface to connect to the two networks that the router at 172.17.3.1 is a successor for. Therefore, that router must be directly connected to the network on the Serial1 interface of the

  local router.

  Objective:

  Layer 3 Technologies

  Sub-Objective:

  Configure and verify policy-based routing

  References:

  Cisco IOS IP Routing: EIGRP Command Reference > show ip eigrp topology

• Question 785:

  An engineer notices that R1 does not hold enough log messages to Identity the root cause during troubleshooting Which command resolves this issue?

  A. #loggin buffered 4096 critical
  B. (config)#logging buffered 16000 informational
  C. #loggin buffered 16000 critical
  D. (config)#logging buffered 4096 informational
  B. (config)#logging buffered 16000 informational

• Question 786:

  Refer to the following exhibit that shows four Cisco routers named rtr1, rtr2, rtr3, and rtr4:

  

  The routers rtr2, rtr3, and rtr4 are eBGP peers of rtr1. In addition, rtr3 and rtr4 are also eBGP peers.

  You want to implement the following requirements on rtr1:

  The first attribute to select the best path is used.

  Advertisements about 10.77.22.0/24 sent by rtr4 will be chosen over the advertisements sent by rtr3.

  Which of the following commands should be included in the implementation plan for rtr1 to achieve the desired results? (Each option is a part of the solution. Choose all that apply.)

  A. neighbor 135.90.66.1 route-map set_weight out
  B. neighbor 135.90.66.6 route-map set_weight in
  C. route-map set_weight deny 10
  D. match ip-address 1
  E. set metric 100
  F. set weight 100
  B. neighbor 135.90.66.6 route-map set_weight in
  D. match ip-address 1
  F. set weight 100

  ---

  The following commands should be included in the implementation plan:

  neighbor 135.90.66.6 route-map set_weight in match ip-address 1 set weight 100 The neighbor 135.90.66.6 route-map set_weight in command specifies a route-map named set_weight for the incoming routing updates from 135.90.66.6 peer. The match ip-address 1 command specifies a criterion to match the IP address as specified in an access list. When the match criterion is met, the action specified in the set weight command is performed.

  The set weight 100 command sets the weight attribute, which is a Cisco-defined attribute, to 100. The weight attribute is the first to be checked when BGP selects the best path between eBGP routers. This attribute is local to the router on which it is set and cannot be advertised to other routers. The complete set of commands to achieve the desired results is as follows:

  access-list 1 permit 10.77.22.0 0.0.0.255

  router bgp 444

  neighbor 135.90.66.3 remote-as 111

  neighbor 135.90.66.1 remote-as 222

  neighbor 135.90.66.6 remote-as 333

  neighbor 135.90.66.6 route-map set_weight in

  route-map set_weight permit 10

  match ip-address 1

  set weight 100

  The set metric 100 command should not be included in the implementation plan to achieve the desired results. This command sets the metric to 100; however, the requirement is to use the first attribute to be checked, which is the weight attribute.

  The neighbor 135.90.66.1 route-map set_weight out command should not be included in the implementation plan. This command forms an eBGP neighbor relationship with rtr3. The command also uses a route map named set_weight to set the weight attribute for the routes sent by rtr1. However, the weight attribute is local to rtr1 and cannot be set for outbound routes.

  The route-map set_weight deny 10 command should not be specified in the implementation plan to achieve the desired results. This command creates a route map named set_weight. The deny keyword in this command indicates that if the match criterion is satisfied, then the set action is not performed. The permit keyword should be specified instead of the deny keyword to perform the set action when a match occurs.

  Objective:

  Layer 3 Technologies

  Sub-Objective:

  Identify suboptimal routing

  References:

  Cisco > Support > Technology Support > IP > IP Routing > Design > Design Technotes > BGP Case Studies > BGP Case Studies 1 > Route Maps Cisco > Support > Technology Support > IP > IP Routing > Design > Design Technotes > BGP Best Path Selection Algorithm

  Cisco > Support > Technology Support > IP > IP Routing > Design > Design Technotes > BGP Case Studies > BGP Case Studies 2 > Weight Attribute

• Question 787:

  With respect to modifying an OSPF router ID to a loopback address, which of the following statements are true?

  A. OSPF is not as reliable if a loopback interface is configured.
  B. Using a loopback address avoids wasting an additional IP address.
  C. A loopback interface is not always active, and it can go "down" like a real interface.
  D. The loopback address does not automatically appear in the routing table of neighboring OSPF routers, so it cannot be pinged from other routers unless you include it with a network statement on the router local to the loopback interface.
  D. The loopback address does not automatically appear in the routing table of neighboring OSPF routers, so it cannot be pinged from other routers unless you include it with a network statement on the router local to the loopback interface.

  ---

  A loopback address does not automatically appear in neighboring routers' routing tables, so it cannot be pinged for network troubleshooting.

  A work-around for this problem is to add a network statement under OSPF that advertises the loopback address network so that other routers will know how to reach your loopback.

  A loopback address is an IP address assigned to a loopback interface, which is a logical interface on a router that behaves like a physical interface. Their advantage is that, unlike physical interfaces, logical interfaces do not go down.

  For example:

  Router(config)# interface loopback 0

  Router(config-if)# ip address 172.17.1.1 255.255.255.0

  In the example, a loopback IP address is used by OSPF to provide its router ID. This type of address is preferred because it is assumed to be more stable than a router ID tied to a physical interface. The traditional problem with a router ID tied to a physical interface is that if the physical interface were to go down, the router would have to change its router ID to some other value. That would cause the OSPF neighbor relationships to reset and change values in the link-state advertisements (LSAs), causing a

  disruption to the OSPF area.

  With this consideration in mind, OSPF is more reliable when using a loopback interface than using a physical interface.

  Using a loopback address does not avoid wasting an additional IP address. The address must still be unique.

  A loopback interface is always active, and it cannot go "down" as a physical interface can.

  Objective:

  Layer 3 Technologies

  Sub-Objective:

  Configure and verify OSPF operations

  References:

  Cisco > IP Routing: OSPF Configuration Guide > Configuring OSPF > Forcing the Router ID Choice with a Loopback Interface

• Question 788:

  If you executed the show ip ospf database command, which keyword would you add to the command to produce the following output?

  

  A. router
  B. summary
  C. network
  D. external
  B. summary

  ---

  The output was produced with the summary keyword. When the show ip ospf database command is executed, any of several keywords can be used to specify the type of link-state advertisements (LSAs) to display. The output LS Type:

  Summary Links(Network) indicates that these are summary links. Summary LSAs are generated by an area border router (ABR) and will be displayed when you execute the summary keyword.

  These are Type 3 LSAs.

  The router keyword was not used. If this keyword had been used, the LS Type line would have included Router Links instead of Summary Links. Router LSAs are Type 1 LSAs.

  The network keyword was not used. If this keyword had been used the LS Type line would have included Network Links instead of Summary Links. Network LSAs are Type 2 LSAs. The external keyword was not used. If this keyword had been used the LS Type line would have included AS External Links instead of Summary Links. External LSAs are Type 5 LSAs.

  Objective:

  Layer 3 Technologies

  Sub-Objective:

  Describe OSPF packet types

  References:

  Cisco > Cisco IOS IP Routing: OSPF Command Reference > show ip ospf database

• Question 789:

  You can use a variety of commands to verify and troubleshoot the operation of route redistribution on your network.

  Which command should you NOT use on routers that are overloaded?

  A. trace
  B. debug
  C. show ip route
  D. show ipx route
  B. debug

  ---

  The debug command uses a good deal of router CPU time, so you should not initiate this command on an already overloaded router. It often requires the router to do extensive examination of the packets, requiring heavy use of resources at times.

  You could also possibly overload the router just with the debug command. If the router is overloaded to the point that it is no longer responding to your EXEC session, you may need to reload the router to stop the debug output.

  These additional steps can help to verify proper route redistribution:

  On the router not performing the redistribution, use the show ip route command to see if the redistributed routes are displayed. On the router performing the redistribution, use the show ip protocol command to verify the redistribution configuration, and use the show ip route command that to verify the proper routes are there from each routing protocol.

  The trace command is used to discover the route that packets take to their destination.

  The show ip route command displays the routing table.

  The show ip protocols command displays information about each routing protocol running on the router.

  Objective:

  Layer 3 Technologies

  Sub-Objective:

  Configure and verify manual and autosummarization with any routing protocol

  References:

  Cisco > Home > Support > Technology Support > Dial and Access > ISDN, CAS > Design > Design Technotes > Important Information on Debug Commands > Document ID: 10374 Cisco > Cisco IOS Debug Command Reference > Using Debug Commands

• Question 790:

  Refer to the exhibit.

  Jun 24 08:54:51.530: IF-EvO(GigabitEthemet0/0): IP Routing reports state transition from DOWN to DOWN Jun 24 08:54:52.525: %1INEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthemet0/0, changed state to down Jun 24 08:54:52.528: IF-EvD(GigabitEthernet0/0): IP Routing reports state transition from DOWN to DOWN Jun 24 08:54:53 215: IF-EvD(GigabitEthernet0/0): IP Routing reports state transition from DOWN to DOWN Jun 24 08:54:54.998: %LINK-3-UPDOWN: Interface GigabitEthemet0/0, changed state to up Jun 24 08:54:55.006: IF-EvO(GigabitEthernet0/0): IP Routing reports state transition from DOWN to UP Jun 24 08:54:55.998: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up

  R1 is connected with R2 via GigabitEthernet0/0, and R2 cannot ping R1. What action will fix the issue?

  A. Fix route dampening configured on the router
  B. Replace the SFP module because it is not supported.
  C. Fix IP Event Dampening configured on the interface.
  D. Correct the IP SLA probe that failed.
  C. Fix IP Event Dampening configured on the interface.

  ---

  The IP Event Dampening feature introduces a configurable exponential decay mechanism to suppress the effects of excessive interface flapping events on routing protocols and routing tables in the network. This feature allows the network operator to configure a router to automatically identify and selectively dampen a local interface that is flapping.