# Free 300-410 practice questions

> 10 free 300-410 practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/cisco-300-410/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/cisco-300-410/

### Question 1 of 10

A BGP session to an eBGP peer stays in the Active state. The peer's address is reachable with ping, and the remote AS number is correct. Which issue is MOST consistent with this state?

- A. The session is established but the maximum-prefix limit has been exceeded
- B. The peer has received the session but the routes are rejected by an inbound prefix list
- C. TCP port 179 cannot connect, for example because update-source does not match
- D. The BGP router IDs on both peers are identical, so the UPDATE messages are rejected

**Answer:** C

**Explanation:** Active means the router is still trying to open the TCP connection to port 179, which commonly fails when the source address does not match the neighbor statement on the peer or when an ACL blocks TCP 179. A prefix list rejecting routes would occur on an established session. A maximum-prefix violation tears down an established session and shows Idle (PfxCt), and a duplicate router ID is detected after the OPEN exchange rather than leaving the session in Active.

### Question 2 of 10

In a hub-and-spoke design where the hub uses a single multipoint GRE interface, EIGRP routes learned from spoke A are not advertised from the hub to spoke B. Which change on the hub tunnel interface corrects this?

- A. no ip next-hop-self eigrp 100
- B. no ip split-horizon eigrp 100
- C. ip bandwidth-percent eigrp 100 75
- D. ip summary-address eigrp 100 0.0.0.0 0.0.0.0

**Answer:** B

**Explanation:** EIGRP split horizon prevents the hub from advertising a route out of the same interface on which it was learned, which blocks spoke-to-spoke propagation on a multipoint interface; disabling it fixes this. Advertising a default summary would give the spokes reachability but replaces the specific routes. Disabling next-hop-self changes the advertised next hop but does not allow the routes out, and bandwidth-percent only limits EIGRP control traffic.

### Question 3 of 10

A branch router learns its default route from headquarters as an OSPF external route. A 4G backup router is reachable at 192.0.2.1, and the static default route toward it must be used only when the OSPF default disappears. Which command meets this requirement?

- A. ip route 0.0.0.0 0.0.0.0 192.0.2.1 permanent
- B. ip route 0.0.0.0 0.0.0.0 192.0.2.1 120
- C. ip route 0.0.0.0 0.0.0.0 192.0.2.1 110 tag 5
- D. ip route 0.0.0.0 0.0.0.0 192.0.2.1 100

**Answer:** B

**Explanation:** A floating static route needs an administrative distance higher than the OSPF route it backs up (110), so a distance of 120 keeps it out of the routing table until the OSPF default is withdrawn. A distance of 100 would beat OSPF and take over immediately. The permanent keyword keeps the route installed with the default distance of 1, which also overrides OSPF, and a distance equal to OSPF's 110 does not reliably prefer the OSPF route.

### Question 4 of 10

For prefix 172.16.40.0/24, router R1's successor has a feasible distance of 2816. The topology table shows three other neighbors with these reported distances: R2 = 2560, R3 = 2816, R4 = 3072. Which neighbors qualify as feasible successors?

- A. R2, R3 and R4, because all of them advertise a valid path to the prefix
- B. Only R2, because its reported distance is strictly lower than the current feasible distance
- C. R2 and R3, because their reported distances are not higher than the current feasible distance
- D. Only R4, because the highest reported distance indicates the most diverse backup path

**Answer:** B

**Explanation:** The EIGRP feasibility condition requires a neighbor's reported distance to be strictly less than the feasible distance of the current successor, so only R2 (2560 < 2816) qualifies. R3's reported distance equals the feasible distance, which fails the strict comparison and could hide a loop. R4's reported distance is higher than the feasible distance, and simply advertising a route never makes a neighbor a feasible successor.

### Question 5 of 10

In a DMVPN network, spokes register successfully with the hub, and show ip nhrp on the hub lists every spoke. However, the hub never forms EIGRP adjacencies with the spokes. Which command is missing on the hub tunnel interface?

- A. ip nhrp network-id 1
- B. ip nhrp registration timeout 30
- C. ip nhrp map multicast dynamic
- D. ip nhrp nhs dynamic

**Answer:** C

**Explanation:** EIGRP hellos are multicast, and ip nhrp map multicast dynamic tells the hub to replicate multicast traffic to every spoke that registers, which lets the adjacencies form. The nhs command is configured on spokes to point at the hub. A network ID is required for NHRP to work at all, and registration succeeded here, and the registration timeout is a spoke timer that does not affect multicast forwarding.

### Question 6 of 10 (choose 2)

A single-hub DMVPN network currently sends all spoke-to-spoke traffic through the hub. The team wants Phase 3 behavior so spokes build direct tunnels on demand while the hub advertises only a summary route. Which two commands are required? (Choose two.)

- A. ip nhrp shortcut on each spoke tunnel interface
- B. tunnel mode gre ip on each spoke tunnel interface
- C. no ip split-horizon eigrp on each spoke tunnel interface
- D. ip nhrp redirect on the hub tunnel interface
- E. ip nhrp map multicast dynamic on every spoke tunnel interface

**Answer:** A, D

**Explanation:** In DMVPN Phase 3 the hub sends NHRP redirect messages when it forwards traffic between spokes, and the spokes use ip nhrp shortcut to install the resolved shortcut path. Dynamic multicast mapping belongs on the hub so it can replicate routing protocol multicasts to registered spokes. Disabling split horizon matters on the hub in Phase 2 designs, and point-to-point GRE mode on spokes would prevent direct spoke-to-spoke tunnels.

### Question 7 of 10

A time-based ACL should allow a contractor subnet access only from 08:00 to 18:00 on weekdays, but the rule is enforced several hours off schedule. The time-range itself is correct. What is the MOST likely cause?

- A. The ACL must be removed and reapplied each day so the router reads the time-range values again
- B. The router's clock or time zone is wrong because NTP is not configured correctly
- C. Time-based ACLs work only on extended named ACLs applied outbound
- D. The time-range must be declared as absolute instead of periodic weekdays

**Answer:** B

**Explanation:** Time-based ACLs evaluate time ranges against the router's local clock, so a wrong clock or time zone shifts enforcement, and synchronizing with NTP with the correct time zone fixes it. Time ranges work with numbered or named extended ACLs in either direction. A periodic range is the right choice for a recurring weekday schedule, and the ACL does not need to be reapplied because the router evaluates the range continuously.

### Question 8 of 10

An engineer must permit SSH to the router's VTY lines only from the management subnet 10.250.0.0/24. Which configuration is the MOST direct way to enforce this?

- A. Configure a CoPP class that drops TCP 22 from any source other than 10.250.0.0/24 on the control plane
- B. Apply a standard ACL permitting 10.250.0.0 0.0.0.255 with access-class in under line vty 0 15
- C. Configure transport input ssh under line vty 0 15 and set the SSH source interface to the management VLAN
- D. Apply an extended ACL permitting TCP 22 from 10.250.0.0/24 with ip access-group in on every interface

**Answer:** B

**Explanation:** An access-class on the VTY lines filters remote management sessions regardless of which interface they arrive on, which directly restricts SSH to the management subnet. Interface ACLs could achieve this but require edits on every interface and affect transit traffic. transport input ssh limits the protocol, not the source, and a CoPP class would work but is a more complex way to meet a simple VTY restriction.

### Question 9 of 10

An engineer must run debug ip packet on a busy core router to troubleshoot traffic from a single host on GigabitEthernet0/3 without overwhelming the console. Which approach is MOST appropriate?

- A. Reference an extended ACL matching the host, as in debug ip packet 101 detail
- B. Configure debug condition interface GigabitEthernet0/3 so only that interface is debugged
- C. Enable logging buffered debugging and disable logging console before starting the debug
- D. Run the debug and then filter the output with show logging | include and the host IP

**Answer:** A

**Explanation:** Binding an ACL that matches only the host's traffic to debug ip packet limits the debug to those packets, which protects CPU and keeps output readable. Redirecting output to the buffer still debugs every packet and only hides it from the console. An interface condition would include every host on that interface, and filtering show logging afterwards does nothing to reduce the debugging load.

### Question 10 of 10

A UDP jitter IP SLA operation from a branch router to a headquarters router reports no statistics, while an ICMP echo operation to the same target succeeds. What is the MOST likely cause?

- A. UDP jitter operations require NTP to be configured on the source router only
- B. The target router has not been configured with ip sla responder
- C. UDP jitter operations work only toward a Cisco Catalyst Center appliance
- D. The operation must be scheduled with the ageout forever keyword to start

**Answer:** B

**Explanation:** UDP jitter relies on a Cisco IP SLA responder on the target to timestamp and return probe packets, so it fails without ip sla responder. Clock synchronization improves one-way delay accuracy but is not what prevents the operation from running. Any IOS device with a responder can be the target, and the ageout keyword only controls how long an inactive operation is kept.

Ready for a timed run? Take the free 15-question 300-410 mini exam: https://devopscodelab.com/app/exams/cisco-300-410/mini/

DevOpsCode Lab is not affiliated with Cisco. 300-410 and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
