Cisco 300-410 Practice Test 73
Question 720
Following a production change at the Lubbock service-provider handoff, a legacy NMS polls routers by SNMPv2c but receives no response after community and source restrictions were tightened. 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?
- Restore the earlier engine/credential state if monitoring on the replacement fails.
- Restore the VTY method list if remote access becomes unusable after the change.
- Disable excessive trap categories if the notifications overwhelm the event collector.
- Restore the previous scoped community policy if polling from legitimate collectors breaks.
Explanation
Correct Answer
D:Restore the previous scoped community policy if polling from legitimate collectors breaks. SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption.
Incorrect Answers
A:Restore the earlier engine/credential state if monitoring on the replacement fails. This is a rollback for a different component (SNMPv3 engine identity), where SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration. Here the evidence instead concerns snmpv2c read access: SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption.
B:Restore the VTY method list if remote access becomes unusable after the change. This is a rollback for a different component (Console versus VTY authentication), where Console and VTY lines can use different authentication and authorization methods. Here the evidence instead concerns snmpv2c read access: SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption.
C:Disable excessive trap categories if the notifications overwhelm the event collector. This is a rollback for a different component (SNMP traps versus polling), where SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events. Here the evidence instead concerns snmpv2c read access: SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption.
Question 721
Following a production change at the Chandler remote operations location, an internal BGP neighbor receives prefixes from an edge router but marks the best paths inaccessible. The incident is affecting an operations uplink; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Check the client's reflector-client configuration, session state, and cluster metadata.
- Inspect local preference distributed in iBGP along with route selection results.
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
- Inspect the received BGP next-hop address and its reachability in the IGP or VRF.
Explanation
Correct Answer
D:Inspect the received BGP next-hop address and its reachability in the IGP or VRF. An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
Incorrect Answers
A:Check the client's reflector-client configuration, session state, and cluster metadata. This is an investigation for a different failure condition (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
B:Inspect local preference distributed in iBGP along with route selection results. This is an investigation for a different failure condition (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 bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
C:Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology. This is an investigation for a different failure condition (Loopback-sourced eBGP session), where Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
Question 722
Following a production change at the Chandler remote operations location, an internal BGP neighbor receives prefixes from an edge router but marks the best paths inaccessible. The incident is affecting an operations uplink; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Install narrowly scoped inter-VRF routes through an approved leaking method without joining the routing tables wholesale.
- Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability.
- Make stub-area settings consistent across the area, including its ABRs.
- Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything.
Explanation
Correct Answer
B:Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability. An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
Incorrect Answers
A:Install narrowly scoped inter-VRF routes through an approved leaking method without joining the routing tables wholesale. This is a configuration change for a different root cause (VRF-Lite controlled route leaking), where VRF separation is intentional; route exchange between VRFs must be explicit and constrained. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
C:Make stub-area settings consistent across the area, including its ABRs. This is a configuration change for a different root cause (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
D:Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything. This is a configuration change for a different root cause (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
Question 723
Following a production change at the Chandler remote operations location, an internal BGP neighbor receives prefixes from an edge router but marks the best paths inaccessible. The incident is affecting an operations uplink; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify TCP 179 establishment using the loopback source and an Established BGP session.
- Verify externally observed paths show the intended extra AS hops without losing prefix reachability.
- Verify client-learned routes are reflected to other clients with correct originator and cluster attributes.
- Confirm the BGP next hop resolves and received routes become installable in the RIB.
Explanation
Correct Answer
D:Confirm the BGP next hop resolves and received routes become installable in the RIB. An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
Incorrect Answers
A:Verify TCP 179 establishment using the loopback source and an Established BGP session. This is a validation for another mechanism (Loopback-sourced eBGP session), where Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
B:Verify externally observed paths show the intended extra AS hops without losing prefix reachability. This is a validation for another mechanism (BGP inbound traffic engineering), where AS-path prepending can make an advertised path less attractive to remote BGP networks, but cannot guarantee inbound routing. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
C:Verify client-learned routes are reflected to other clients with correct originator and cluster attributes. This is a validation for another mechanism (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
Question 724
Following a production change at the Chandler remote operations location, an internal BGP neighbor receives prefixes from an edge router but marks the best paths inaccessible. The incident is affecting an operations uplink; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship.
- Inspect the received BGP next-hop address and its reachability in the IGP or VRF.
- Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability.
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
Explanation
Correct Answers
B:Inspect the received BGP next-hop address and its reachability in the IGP or VRF. An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
C:Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability. An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
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 bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
D:Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology. This is an investigation for a different failure condition (Loopback-sourced eBGP session), where Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings. Here the evidence instead concerns bgp ibgp next-hop reachability: An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters.
Question 725
During a scheduled validation at the Mesa regional hub, a router learns 10.44.0.0/16 from OSPF and from a floating static route, but the static next hop is used even while OSPF is healthy. Engineers must restore a customer routing segment without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Compare interface MTUs and DBD packet handling rather than changing OSPF cost.
- Compare the configured EIGRP autonomous-system numbers and active interface participation.
- Inspect the route's selected source, prefix length, and administrative distance in the routing table.
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
Explanation
Correct Answer
C:Inspect the route's selected source, prefix length, and administrative distance in the routing table. For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Incorrect Answers
A: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 administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
B:Compare the configured EIGRP autonomous-system numbers and active interface participation. This is an investigation for a different failure condition (EIGRP AS mismatch), where EIGRP neighbors for an address family need compatible autonomous-system association and interface settings. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
D:Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology. This is an investigation for a different failure condition (Loopback-sourced eBGP session), where Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Question 726
During a scheduled validation at the Mesa regional hub, a router learns 10.44.0.0/16 from OSPF and from a floating static route, but the static next hop is used even while OSPF is healthy. Engineers must restore a customer routing segment without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance.
- Put the intended permit conditions before the catch-all deny or narrow the deny match.
- Raise the static route's distance above the intended OSPF route or remove the unwanted override.
- Provide the required EIGRP seed metric through redistribution or a route map for the intended source.
Explanation
Correct Answer
C:Raise the static route's distance above the intended OSPF route or remove the unwanted override. For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Incorrect Answers
A:Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance. This is a configuration change for a different root cause (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
B:Put the intended permit conditions before the catch-all deny or narrow the deny match. This is a configuration change for a different root cause (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 administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
D:Provide the required EIGRP seed metric through redistribution or a route map for the intended source. This is a configuration change for a different root cause (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Question 727
During a scheduled validation at the Mesa regional hub, a router learns 10.44.0.0/16 from OSPF and from a floating static route, but the static next hop is used even while OSPF is healthy. 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 client-learned routes are reflected to other clients with correct originator and cluster attributes.
- Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears.
- Confirm the BGP next hop resolves and received routes become installable in the RIB.
- Check both peers appear in the EIGRP neighbor table and routes converge.
Explanation
Correct Answer
B:Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears. For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Incorrect Answers
A:Verify client-learned routes are reflected to other clients with correct originator and cluster attributes. This is a validation for another mechanism (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
C: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 administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
D:Check both peers appear in the EIGRP neighbor table and routes converge. This is a validation for another mechanism (EIGRP AS mismatch), where EIGRP neighbors for an address family need compatible autonomous-system association and interface settings. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Question 728
During a scheduled validation at the Mesa regional hub, a router learns 10.44.0.0/16 from OSPF and from a floating static route, but the static next hop is used even while OSPF is healthy. Engineers must restore a customer routing segment without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage.
- Inspect the route's selected source, prefix length, and administrative distance in the routing table.
- Raise the static route's distance above the intended OSPF route or remove the unwanted override.
- Compare the destination's matching prefixes and their lengths, not merely route-source preference.
Explanation
Correct Answers
B:Inspect the route's selected source, prefix length, and administrative distance in the routing table. For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
C:Raise the static route's distance above the intended OSPF route or remove the unwanted override. For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Incorrect Answers
A:Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage. This is a configuration change for a different root cause (Summary route black hole), where An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
D:Compare the destination's matching prefixes and their lengths, not merely route-source preference. This is an investigation for a different failure condition (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Question 729
During a scheduled validation at the Berkeley manufacturing plant, two border routers learn the same prefix, but most internal routers prefer the wrong upstream exit. Engineers must restore a customer routing segment without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect outbound prefix filters and route-map hit counts for unauthorized advertisements.
- Inspect the received BGP next-hop address and its reachability in the IGP or VRF.
- Inspect local preference distributed in iBGP along with route selection results.
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
Explanation
Correct Answer
C:Inspect local preference distributed in iBGP along with route selection results. Within an AS, higher BGP local preference normally wins before AS-path length and MED.
Incorrect Answers
A:Inspect outbound prefix filters and route-map hit counts for unauthorized advertisements. This is an investigation for a different failure condition (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 bgp outbound path local preference: Within an AS, higher BGP local preference normally wins before AS-path length and MED.
B:Inspect the received BGP next-hop address and its reachability in the IGP or VRF. This is an investigation for a different failure condition (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 bgp outbound path local preference: Within an AS, higher BGP local preference normally wins before AS-path length and MED.
D:Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology. This is an investigation for a different failure condition (Loopback-sourced eBGP session), where Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings. Here the evidence instead concerns bgp outbound path local preference: Within an AS, higher BGP local preference normally wins before AS-path length and MED.
Question 730
During a scheduled validation at the Berkeley manufacturing plant, two border routers learn the same prefix, but most internal routers prefer the wrong upstream exit. Engineers must restore a customer routing segment without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Set a higher local preference for the preferred egress using a scoped inbound policy at the edge.
- Configure a consistent loopback update source and sufficient eBGP multihop hop limit.
- Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability.
- Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship.
Explanation
Correct Answer
A:Set a higher local preference for the preferred egress using a scoped inbound policy at the edge. Within an AS, higher BGP local preference normally wins before AS-path length and MED.
Incorrect Answers
B:Configure a consistent loopback update source and sufficient eBGP multihop hop limit. This is a configuration change for a different root cause (Loopback-sourced eBGP session), where Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings. Here the evidence instead concerns bgp outbound path local preference: Within an AS, higher BGP local preference normally wins before AS-path length and MED.
C:Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability. This is a configuration change for a different root cause (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 bgp outbound path local preference: Within an AS, higher BGP local preference normally wins before AS-path length and MED.
D: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 bgp outbound path local preference: Within an AS, higher BGP local preference normally wins before AS-path length and MED.