Cisco 300-410 Practice Test 68
Question 670
During a scheduled validation at the Dayton distribution campus, a remote EIGRP prefix goes active and remains unresolved until routers reset neighbor relationships. Engineers must restore management access without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship.
- Apply an explicit allowlist prefix policy outbound to the external BGP peer.
- Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes.
- Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link.
Explanation
Correct Answer
D:Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link. EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
Incorrect Answers
A:Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship. This is a configuration change for a different root cause (BGP peer remote AS), where BGP neighbors must agree on configured peer AS identity and establish a TCP session. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
B:Apply an explicit allowlist prefix policy outbound to the external BGP peer. This is a configuration change for a different root cause (BGP prefix leak prevention), where BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
C:Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes. This is a configuration change for a different root cause (EIGRP stub branch), where EIGRP stub limits query scope and is appropriate only where the device is not needed as transit. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
Question 671
During a scheduled validation at the Dayton distribution campus, a remote EIGRP prefix goes active and remains unresolved until routers reset neighbor relationships. Engineers must restore management access without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs.
- Check active routes settle and query traffic is confined during a controlled failure.
- Verify the external EIGRP route and plausible composite metric appear in neighbor tables.
- Confirm internal BGP speakers consistently choose the preferred exit while backup remains available.
Explanation
Correct Answer
B:Check active routes settle and query traffic is confined during a controlled failure. EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
Incorrect Answers
A:Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs. This is a validation for another mechanism (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
C:Verify the external EIGRP route and plausible composite metric appear in neighbor tables. This is a validation for another mechanism (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
D:Confirm internal BGP speakers consistently choose the preferred exit while backup remains available. This is a validation for another mechanism (BGP outbound path local preference), where Within an AS, higher BGP local preference normally wins before AS-path length and MED. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
Question 672
During a scheduled validation at the Dayton distribution campus, a remote EIGRP prefix goes active and remains unresolved until routers reset neighbor relationships. Engineers must restore management access without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the previous ordered route-map clauses if the permitted set becomes too broad.
- Undo new stub restrictions if required transit routes vanish.
- Restore the last verified neighbor export policy if broad filtering withdraws legitimate service routes.
- Reapply the former metric and route-map configuration if new routes displace stable paths.
Explanation
Correct Answer
B:Undo new stub restrictions if required transit routes vanish. EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
Incorrect Answers
A:Restore the previous ordered route-map clauses if the permitted set becomes too broad. This is a rollback for a different component (Route-map permit sequence), where Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
C:Restore the last verified neighbor export policy if broad filtering withdraws legitimate service routes. This is a rollback for a different component (BGP prefix leak prevention), where BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
D:Reapply the former metric and route-map configuration if new routes displace stable paths. This is a rollback for a different component (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
Question 673
During a scheduled validation at the Spokane branch site, two devices added from the same template display identical OSPF router IDs, and routing behavior is unstable. Engineers must restore a customer routing segment without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Compare OSPF stub flags and area type on every router participating in the area.
- Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior.
- Compare interface MTUs and DBD packet handling rather than changing OSPF cost.
- Inspect the OSPF process router IDs and compare them across the affected area.
Explanation
Correct Answer
D:Inspect the OSPF process router IDs and compare them across the affected area. OSPF uses router IDs as unique LSA originator identities within the routing domain.
Incorrect Answers
A:Compare OSPF stub flags and area type on every router participating in the area. This is an investigation for a different failure condition (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
B:Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior. This is an investigation for a different failure condition (OSPF NSSA external route translation), where An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
C:Compare interface MTUs and DBD packet handling rather than changing OSPF cost. This is an investigation for a different failure condition (OSPF database exchange MTU), where An MTU mismatch can prevent OSPF database description exchange from completing. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
Question 674
During a scheduled validation at the Spokane branch site, two devices added from the same template display identical OSPF router IDs, and routing behavior is unstable. Engineers must restore a customer routing segment without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Align the OSPF timer pair and compatible network type for the shared segment.
- Assign a unique stable router ID to the conflicting router and restart the process in a controlled window if necessary.
- Align the effective IP MTU values on both interfaces before considering platform-specific workarounds.
- Select the appropriate external metric type and cost policy to reflect the enterprise exit preference.
Explanation
Correct Answer
B:Assign a unique stable router ID to the conflicting router and restart the process in a controlled window if necessary. OSPF uses router IDs as unique LSA originator identities within the routing domain.
Incorrect Answers
A:Align the OSPF timer pair and compatible network type for the shared segment. This is a configuration change for a different root cause (OSPF hello and dead timers), where OSPF timer compatibility is necessary for adjacency formation on a common segment. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
C:Align the effective IP MTU values on both interfaces before considering platform-specific workarounds. This is a configuration change for a different root cause (OSPF database exchange MTU), where An MTU mismatch can prevent OSPF database description exchange from completing. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
D:Select the appropriate external metric type and cost policy to reflect the enterprise exit preference. This is a configuration change for a different root cause (OSPF external route type), where OSPF E1 considers internal path cost with external cost, while E2 primarily compares the external metric. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
Question 675
During a scheduled validation at the Spokane branch site, two devices added from the same template display identical OSPF router IDs, and routing behavior is unstable. Engineers must restore a customer routing segment without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation.
- Observe the neighbor reach Full state with stable hellos after correction.
- Check routing-table next hops across sites to verify preferred external exit selection.
- Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs.
Explanation
Correct Answer
A:Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation. OSPF uses router IDs as unique LSA originator identities within the routing domain.
Incorrect Answers
B:Observe the neighbor reach Full state with stable hellos after correction. This is a validation for another mechanism (OSPF hello and dead timers), where OSPF timer compatibility is necessary for adjacency formation on a common segment. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
C:Check routing-table next hops across sites to verify preferred external exit selection. This is a validation for another mechanism (OSPF external route type), where OSPF E1 considers internal path cost with external cost, while E2 primarily compares the external metric. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
D:Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs. This is a validation for another mechanism (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
Question 676
During a scheduled validation at the Spokane branch site, two devices added from the same template display identical OSPF router IDs, and routing behavior is unstable. Engineers must restore a customer routing segment without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Remove the new area range if it hides required specificity or changes failover.
- Reinstate the former configuration only after selecting a nonconflicting replacement ID.
- Restore the last valid area configuration if routes leak across unintended boundaries.
- Restore earlier external metric policy if traffic shifts to a constrained circuit.
Explanation
Correct Answer
B:Reinstate the former configuration only after selecting a nonconflicting replacement ID. OSPF uses router IDs as unique LSA originator identities within the routing domain.
Incorrect Answers
A:Remove the new area range if it hides required specificity or changes failover. This is a rollback for a different component (OSPF interarea summarization), where OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
C:Restore the last valid area configuration if routes leak across unintended boundaries. This is a rollback for a different component (OSPF area mismatch), where OSPF neighbors must agree on the local link's area ID. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
D:Restore earlier external metric policy if traffic shifts to a constrained circuit. This is a rollback for a different component (OSPF external route type), where OSPF E1 considers internal path cost with external cost, while E2 primarily compares the external metric. Here the evidence instead concerns ospf duplicate router id: OSPF uses router IDs as unique LSA originator identities within the routing domain.
Question 677
Following a production change at the Huntsville branch site, user traffic matches an ingress PBR policy, but router-originated diagnostic packets do not use the same alternate next hop. The incident is affecting a customer routing segment; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Check key IDs, configured authentication mode, key validity, and key strings at both ends.
- Determine whether failing traffic originates on the router and inspect local policy routing configuration.
- Trace route tags and redistribution points to identify reintroduction of the same route.
- Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior.
Explanation
Correct Answer
B:Determine whether failing traffic originates on the router and inspect local policy routing configuration. Transit PBR on an interface does not automatically change forwarding of locally originated packets.
Incorrect Answers
A:Check key IDs, configured authentication mode, key validity, and key strings at both ends. This is an investigation for a different failure condition (EIGRP neighbor authentication), where Routing authentication mismatches prevent EIGRP neighbors from exchanging trusted updates. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
C:Trace route tags and redistribution points to identify reintroduction of the same route. This is an investigation for a different failure condition (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
D:Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior. This is an investigation for a different failure condition (OSPF NSSA external route translation), where An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
Question 678
Following a production change at the Huntsville branch site, user traffic matches an ingress PBR policy, but router-originated diagnostic packets do not use the same alternate next hop. The incident is affecting a customer routing segment; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Apply a scoped local policy route map for router-generated packets if that behavior is required.
- Enable compatible BFD detection for the routing adjacency with realistic interval and multiplier settings.
- Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate.
- Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link.
Explanation
Correct Answer
A:Apply a scoped local policy route map for router-generated packets if that behavior is required. Transit PBR on an interface does not automatically change forwarding of locally originated packets.
Incorrect Answers
B:Enable compatible BFD detection for the routing adjacency with realistic interval and multiplier settings. This is a configuration change for a different root cause (BFD fast-failure detection), where Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
C:Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate. This is a configuration change for a different root cause (EIGRP feasible successor), where The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
D:Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link. This is a configuration change for a different root cause (EIGRP stuck-in-active), where EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
Question 679
Following a production change at the Huntsville branch site, user traffic matches an ingress PBR policy, but router-originated diagnostic packets do not use the same alternate next hop. The incident is affecting a customer routing segment; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Test router-originated packets separately from transit packets and compare next-hop selection.
- Confirm the BGP next hop resolves and received routes become installable in the RIB.
- Check routing-table next hops across sites to verify preferred external exit selection.
- Verify the BGP session establishes and receives only authorized prefixes.
Explanation
Correct Answer
A:Test router-originated packets separately from transit packets and compare next-hop selection. Transit PBR on an interface does not automatically change forwarding of locally originated packets.
Incorrect Answers
B:Confirm the BGP next hop resolves and received routes become installable in the RIB. This is a validation for another mechanism (BGP iBGP next-hop reachability), where An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
C:Check routing-table next hops across sites to verify preferred external exit selection. This is a validation for another mechanism (OSPF external route type), where OSPF E1 considers internal path cost with external cost, while E2 primarily compares the external metric. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
D:Verify the BGP session establishes and receives only authorized prefixes. This is a validation for another mechanism (BGP peer remote AS), where BGP neighbors must agree on configured peer AS identity and establish a TCP session. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
Question 680
Following a production change at the Huntsville branch site, user traffic matches an ingress PBR policy, but router-originated diagnostic packets do not use the same alternate next hop. The incident is affecting a customer routing segment; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Reinstate the former configuration only after selecting a nonconflicting replacement ID.
- Revert the next-hop rewrite if it diverts traffic from the intended external edge.
- Restore the original neighbor statement if the AS migration must be backed out.
- Remove the local policy if control or management plane traffic is misdirected.
Explanation
Correct Answer
D:Remove the local policy if control or management plane traffic is misdirected. Transit PBR on an interface does not automatically change forwarding of locally originated packets.
Incorrect Answers
A:Reinstate the former configuration only after selecting a nonconflicting replacement ID. This is a rollback for a different component (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
B:Revert the next-hop rewrite if it diverts traffic from the intended external edge. This is a rollback for a different component (BGP iBGP next-hop reachability), where An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.
C:Restore the original neighbor statement if the AS migration must be backed out. This is a rollback for a different component (BGP peer remote AS), where BGP neighbors must agree on configured peer AS identity and establish a TCP session. Here the evidence instead concerns locally generated pbr: Transit PBR on an interface does not automatically change forwarding of locally originated packets.