Cisco 300-410 Practice Test 18
Question 170
Following a production change at the Roswell regional hub, a DMVPN spoke's tunnel interface remains up/up, but NHRP never registers after its ISP-facing interface was changed. The incident is affecting a tenant service; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Align the intended NHRP authentication values without disabling authentication globally.
- Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior.
- Update the authorized peer authentication mapping or identity policy to match the new underlay endpoint.
- Bind the tunnel to the correct reachable underlay source and update dependent NBMA mapping as needed.
Explanation
Correct Answer
D:Bind the tunnel to the correct reachable underlay source and update dependent NBMA mapping as needed. DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Incorrect Answers
A:Align the intended NHRP authentication values without disabling authentication globally. This is a configuration change for a different root cause (DMVPN NHRP authentication), where NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
B:Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior. This is a configuration change for a different root cause (EIGRP on DMVPN hub), where DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
C:Update the authorized peer authentication mapping or identity policy to match the new underlay endpoint. This is a configuration change for a different root cause (IKE peer authentication), where IKE peer authentication is independent of NHRP and must match the correct endpoint identity and credentials. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Question 171
Following a production change at the Roswell regional hub, a DMVPN spoke's tunnel interface remains up/up, but NHRP never registers after its ISP-facing interface was changed. The incident is affecting a tenant service; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify accepted registrations appear at the hub and authorized spokes can resolve tunnel addresses.
- Verify IPsec SAs form and protected DMVPN traffic increments encapsulation/decapsulation counters.
- Verify the spoke reaches the hub's NBMA endpoint and NHRP registration succeeds.
- Verify the spoke registers with the intended NHS and can resolve hub tunnel reachability.
Explanation
Correct Answer
C:Verify the spoke reaches the hub's NBMA endpoint and NHRP registration succeeds. DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Incorrect Answers
A:Verify accepted registrations appear at the hub and authorized spokes can resolve tunnel addresses. This is a validation for another mechanism (DMVPN NHRP authentication), where NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
B:Verify IPsec SAs form and protected DMVPN traffic increments encapsulation/decapsulation counters. This is a validation for another mechanism (DMVPN IPsec protection mismatch), where DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
D:Verify the spoke registers with the intended NHS and can resolve hub tunnel reachability. This is a validation for another mechanism (DMVPN NHS mapping), where A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Question 172
Following a production change at the Roswell regional hub, a DMVPN spoke's tunnel interface remains up/up, but NHRP never registers after its ISP-facing interface was changed. The incident is affecting a tenant service; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Revert the new peer identity mapping if it unexpectedly permits an unknown spoke.
- Restore the prior tunnel source if the new ISP path cannot support the overlay.
- Roll back the IPsec proposal atomically on both sides if secure tunnel establishment fails.
- Restore the prior multicast map if the change floods routing hellos to unintended endpoints.
Explanation
Correct Answer
B:Restore the prior tunnel source if the new ISP path cannot support the overlay. DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Incorrect Answers
A:Revert the new peer identity mapping if it unexpectedly permits an unknown spoke. This is a rollback for a different component (IKE peer authentication), where IKE peer authentication is independent of NHRP and must match the correct endpoint identity and credentials. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
C:Roll back the IPsec proposal atomically on both sides if secure tunnel establishment fails. This is a rollback for a different component (DMVPN IPsec protection mismatch), where DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
D:Restore the prior multicast map if the change floods routing hellos to unintended endpoints. This is a rollback for a different component (DMVPN multicast neighbor discovery), where Dynamic routing across GRE/mGRE requires the overlay to carry its multicast or broadcast control traffic. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Question 173
During a scheduled validation at the Omaha enterprise edge, routes learned from one iBGP client do not reach another iBGP client connected to the same route reflector. Engineers must restore remote-site route stability without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Check the client's reflector-client configuration, session state, and cluster metadata.
- Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor.
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
- Inspect local preference distributed in iBGP along with route selection results.
Explanation
Correct Answer
A:Check the client's reflector-client configuration, session state, and cluster metadata. Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
Incorrect Answers
B:Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor. This is an investigation for a different failure condition (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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
D: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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
Question 174
During a scheduled validation at the Omaha enterprise edge, routes learned from one iBGP client do not reach another iBGP client connected to the same route reflector. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Configure a consistent loopback update source and sufficient eBGP multihop hop limit.
- Set a higher local preference for the preferred egress using a scoped inbound policy at the edge.
- Mark the intended iBGP neighbors as route-reflector clients under the correct address family.
- Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability.
Explanation
Correct Answer
C:Mark the intended iBGP neighbors as route-reflector clients under the correct address family. Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
Incorrect Answers
A: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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
B:Set a higher local preference for the preferred egress using a scoped inbound policy at the edge. This is a configuration change for a different root cause (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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
D: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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
Question 175
During a scheduled validation at the Omaha enterprise edge, routes learned from one iBGP client do not reach another iBGP client connected to the same route reflector. Engineers must restore remote-site route stability without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify only authorized aggregate prefixes are advertised and the private/internal prefixes are absent.
- Verify TCP 179 establishment using the loopback source and an Established BGP session.
- Verify client-learned routes are reflected to other clients with correct originator and cluster attributes.
- Verify the BGP session establishes and receives only authorized prefixes.
Explanation
Correct Answer
C:Verify client-learned routes are reflected to other clients with correct originator and cluster attributes. Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
Incorrect Answers
A:Verify only authorized aggregate prefixes are advertised and the private/internal prefixes are absent. This is a validation for another mechanism (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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
B: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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
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 bgp route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
Question 176
During a scheduled validation at the Omaha enterprise edge, routes learned from one iBGP client do not reach another iBGP client connected to the same route reflector. Engineers must restore remote-site route stability without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the last verified neighbor export policy if broad filtering withdraws legitimate service routes.
- Revert the local-preference policy if it overloads the selected WAN circuit.
- Undo reflector-client assignment if it creates an unintended reflection topology.
- Remove unsupported multihop changes and restore the original direct-peering source if needed.
Explanation
Correct Answer
C:Undo reflector-client assignment if it creates an unintended reflection topology. Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
Incorrect Answers
A: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 bgp route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
B:Revert the local-preference policy if it overloads the selected WAN circuit. This is a rollback for a different component (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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
D:Remove unsupported multihop changes and restore the original direct-peering source if needed. This is a rollback for a different component (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 route reflector clients: Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes.
Question 177
During a scheduled validation at the Naperville service-provider handoff, a collector reports no new application-flow records after a router refresh although interfaces pass traffic normally. Engineers must restore a customer routing segment without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect flow record, flow monitor, and whether the monitor is attached in the intended interface direction.
- Inspect exporter destination address, UDP port, source-interface, VRF, and export statistics.
- Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding.
- Inspect the VTY access-class, source subnet permit entries, and applied inbound direction.
Explanation
Correct Answer
A:Inspect flow record, flow monitor, and whether the monitor is attached in the intended interface direction. Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Incorrect Answers
B:Inspect exporter destination address, UDP port, source-interface, VRF, and export statistics. This is an investigation for a different failure condition (NetFlow exporter destination), where Flow collection and export are distinct: valid local cache entries do not imply successful export transport. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
C:Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding. This is an investigation for a different failure condition (IPv4 DHCP relay), where IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
D:Inspect the VTY access-class, source subnet permit entries, and applied inbound direction. This is an investigation for a different failure condition (VTY access-class), where A VTY access-class restricts which source addresses can open remote terminal sessions to the router. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Question 178
During a scheduled validation at the Naperville service-provider handoff, a collector reports no new application-flow records after a router refresh although interfaces pass traffic normally. Engineers must restore a customer routing segment without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Install a trusted certificate matching the intended management DNS name and enforce HTTPS.
- Attach the compatible Flexible NetFlow monitor to the correct traffic-facing interface and direction.
- Configure the correct ip helper-address on the client-facing routed interface.
- Correct the exporter's receiver, source, and transport settings without changing the flow record unnecessarily.
Explanation
Correct Answer
B:Attach the compatible Flexible NetFlow monitor to the correct traffic-facing interface and direction. Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Incorrect Answers
A:Install a trusted certificate matching the intended management DNS name and enforce HTTPS. This is a configuration change for a different root cause (HTTPS device management), where HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
C:Configure the correct ip helper-address on the client-facing routed interface. This is a configuration change for a different root cause (IPv4 DHCP relay), where IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
D:Correct the exporter's receiver, source, and transport settings without changing the flow record unnecessarily. This is a configuration change for a different root cause (NetFlow exporter destination), where Flow collection and export are distinct: valid local cache entries do not imply successful export transport. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Question 179
During a scheduled validation at the Naperville service-provider handoff, a collector reports no new application-flow records after a router refresh although interfaces pass traffic normally. 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 the collector receives decoded flows and the router's export success counter increments.
- Generate known flows and verify cache entries and corresponding exported records.
- Validate console and VTY logins with their intended distinct credentials and restrictions.
- Compare event timestamps across devices after a known simultaneous test event.
Explanation
Correct Answer
B:Generate known flows and verify cache entries and corresponding exported records. Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Incorrect Answers
A:Verify the collector receives decoded flows and the router's export success counter increments. This is a validation for another mechanism (NetFlow exporter destination), where Flow collection and export are distinct: valid local cache entries do not imply successful export transport. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
C:Validate console and VTY logins with their intended distinct credentials and restrictions. This is a validation for another mechanism (Console versus VTY authentication), where Console and VTY lines can use different authentication and authorization methods. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
D:Compare event timestamps across devices after a known simultaneous test event. This is a validation for another mechanism (Time synchronization for logs), where Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Question 180
During a scheduled validation at the Naperville service-provider handoff, a collector reports no new application-flow records after a router refresh although interfaces pass traffic normally. 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?
- Disable the newly enabled SCP service if authorization permits unapproved file access.
- Detach the monitor if it consumes excessive resources on an unsupported interface.
- Remove the new relay if replies reach the wrong IPv6 segment.
- Restore the previous exporter path if exports accidentally reach an external untrusted collector.
Explanation
Correct Answer
B:Detach the monitor if it consumes excessive resources on an unsupported interface. Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Incorrect Answers
A:Disable the newly enabled SCP service if authorization permits unapproved file access. This is a rollback for a different component (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
C:Remove the new relay if replies reach the wrong IPv6 segment. This is a rollback for a different component (DHCPv6 relay), where DHCPv6 relaying transports client messages to a remote server; Router Advertisements still convey default-router details. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
D:Restore the previous exporter path if exports accidentally reach an external untrusted collector. This is a rollback for a different component (NetFlow exporter destination), where Flow collection and export are distinct: valid local cache entries do not imply successful export transport. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.