Cisco 300-410 Practice Test 67
Question 660
Following a production change at the Denver warehouse network, sNMPv3 authentication stops after a router replacement despite reusing the old usernames, and monitoring tools report localized-key mismatch. The incident is affecting a monitored campus segment; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Restore the previous scoped community policy if polling from legitimate collectors breaks.
- Restore the earlier engine/credential state if monitoring on the replacement fails.
- Restore earlier remote logging limits if the new level floods the collector.
- Disable excessive trap categories if the notifications overwhelm the event collector.
Explanation
Correct Answer
B:Restore the earlier engine/credential state if monitoring on the replacement fails. SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration.
Incorrect Answers
A:Restore the previous scoped community policy if polling from legitimate collectors breaks. This is a rollback for a different component (SNMPv2c read access), where SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption. Here the evidence instead concerns snmpv3 engine identity: SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration.
C:Restore earlier remote logging limits if the new level floods the collector. This is a rollback for a different component (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns snmpv3 engine identity: SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration.
D: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 snmpv3 engine identity: SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration.
Question 661
During a scheduled validation at the Boise service-provider handoff, syslog messages from a router stop arriving after a management VRF change although the collector remains reachable from the correct source. Engineers must restore a voice service path without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect line-specific login method lists, transport settings, and source filters separately for console and VTY.
- Compare local logging buffer settings with remote trap severity and collector-side filtering.
- Inspect configured logging source-interface, VRF-aware transport, and collector allowlists.
- Check SCP server enablement, privilege, AAA authorization, and management path reachability.
Explanation
Correct Answer
C:Inspect configured logging source-interface, VRF-aware transport, and collector allowlists. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Incorrect Answers
A:Inspect line-specific login method lists, transport settings, and source filters separately for console and VTY. This is an investigation for a different failure condition (Console versus VTY authentication), where Console and VTY lines can use different authentication and authorization methods. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
B:Compare local logging buffer settings with remote trap severity and collector-side filtering. This is an investigation for a different failure condition (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
D:Check SCP server enablement, privilege, AAA authorization, and management path reachability. This is an investigation for a different failure condition (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Question 662
During a scheduled validation at the Boise service-provider handoff, syslog messages from a router stop arriving after a management VRF change although the collector remains reachable from the correct source. Engineers must restore a voice service path without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Correct the VTY AAA binding for remote access while preserving console emergency management.
- Set the intended reachable source-interface and VRF context for remote syslog traffic.
- Set the appropriate remote logging level and destination for the intended operational events.
- Enable the appropriate SCP service and narrowly scoped permissions for the backup account.
Explanation
Correct Answer
B:Set the intended reachable source-interface and VRF context for remote syslog traffic. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Incorrect Answers
A:Correct the VTY AAA binding for remote access while preserving console emergency management. This is a configuration change for a different root cause (Console versus VTY authentication), where Console and VTY lines can use different authentication and authorization methods. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
C:Set the appropriate remote logging level and destination for the intended operational events. This is a configuration change for a different root cause (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
D:Enable the appropriate SCP service and narrowly scoped permissions for the backup account. This is a configuration change for a different root cause (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Question 663
During a scheduled validation at the Boise service-provider handoff, syslog messages from a router stop arriving after a management VRF change although the collector remains reachable from the correct source. Engineers must restore a voice service path without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Confirm client health improves for the affected population rather than relying only on global device uptime.
- Trigger a known test event and verify the message arrives with expected severity and facility.
- Simulate upstream failure and confirm the tracked route withdraws while backup routing activates.
- Verify a test message reaches the collector from the approved router identity.
Explanation
Correct Answer
D:Verify a test message reaches the collector from the approved router identity. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Incorrect Answers
A:Confirm client health improves for the affected population rather than relying only on global device uptime. This is a validation for another mechanism (Catalyst Center client assurance), where Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
B:Trigger a known test event and verify the message arrives with expected severity and facility. This is a validation for another mechanism (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
C:Simulate upstream failure and confirm the tracked route withdraws while backup routing activates. This is a validation for another mechanism (IP SLA object tracking failover), where IP SLA probes detect beyond-interface reachability, and object tracking can control static route installation. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Question 664
During a scheduled validation at the Boise service-provider handoff, syslog messages from a router stop arriving after a management VRF change although the collector remains reachable from the correct source. Engineers must restore a voice service path without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Compare local logging buffer settings with remote trap severity and collector-side filtering.
- Inspect configured logging source-interface, VRF-aware transport, and collector allowlists.
- Set the intended reachable source-interface and VRF context for remote syslog traffic.
- Install a trusted certificate matching the intended management DNS name and enforce HTTPS.
Explanation
Correct Answers
B:Inspect configured logging source-interface, VRF-aware transport, and collector allowlists. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
C:Set the intended reachable source-interface and VRF context for remote syslog traffic. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Incorrect Answers
A:Compare local logging buffer settings with remote trap severity and collector-side filtering. This is an investigation for a different failure condition (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
D: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 syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Question 665
During a scheduled validation at the Lincoln hospital campus, dMVPN spokes learn remote routes through a hub but cannot use direct spoke-to-spoke forwarding because the advertised next hop always points to the hub. Engineers must restore an operations uplink without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect the routing protocol's next-hop handling, EIGRP split-horizon, and DMVPN phase architecture.
- Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub.
- Inspect the IKE peer identity, key selection, and authentication failure logs for the changed NBMA address.
- Compare IKE/IPsec negotiation output, transform proposals, key lifetimes, and peer reachability.
Explanation
Correct Answer
A:Inspect the routing protocol's next-hop handling, EIGRP split-horizon, and DMVPN phase architecture. DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
Incorrect Answers
B:Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub. This is an investigation for a different failure condition (DMVPN tunnel source), where DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association. Here the evidence instead concerns eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
C:Inspect the IKE peer identity, key selection, and authentication failure logs for the changed NBMA address. This is an investigation for a different failure condition (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 eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
D:Compare IKE/IPsec negotiation output, transform proposals, key lifetimes, and peer reachability. This is an investigation for a different failure condition (DMVPN IPsec protection mismatch), where DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay. Here the evidence instead concerns eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
Question 666
During a scheduled validation at the Lincoln hospital campus, dMVPN spokes learn remote routes through a hub but cannot use direct spoke-to-spoke forwarding because the advertised next hop always points to the hub. Engineers must restore an operations uplink without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Align the intended NHRP authentication values without disabling authentication globally.
- Align supported IPsec proposals and tunnel protection profiles on both endpoints without downgrading policy.
- Bind the tunnel to the correct reachable underlay source and update dependent NBMA mapping as needed.
- Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior.
Explanation
Correct Answer
D:Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior. DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
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 eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
B:Align supported IPsec proposals and tunnel protection profiles on both endpoints without downgrading policy. This is a configuration change for a different root cause (DMVPN IPsec protection mismatch), where DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay. Here the evidence instead concerns eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
C:Bind the tunnel to the correct reachable underlay source and update dependent NBMA mapping as needed. This is a configuration change for a different root cause (DMVPN tunnel source), where DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association. Here the evidence instead concerns eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
Question 667
During a scheduled validation at the Lincoln hospital campus, dMVPN spokes learn remote routes through a hub but cannot use direct spoke-to-spoke forwarding because the advertised next hop always points to the hub. Engineers must restore an operations uplink without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify a spoke obtains a shortcut mapping and subsequent traffic uses a direct spoke-to-spoke tunnel.
- Verify remote routes and NHRP mappings support the planned direct path without looping.
- Check tunnel counters and NHRP registration after restoring matched encapsulation settings.
- Observe multicast routing hello exchange and stable protocol neighbors across the overlay.
Explanation
Correct Answer
B:Verify remote routes and NHRP mappings support the planned direct path without looping. DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
Incorrect Answers
A:Verify a spoke obtains a shortcut mapping and subsequent traffic uses a direct spoke-to-spoke tunnel. This is a validation for another mechanism (DMVPN phase 3 shortcut), where DMVPN phase 3 uses hub redirects and spoke shortcuts to facilitate direct spoke-to-spoke forwarding. Here the evidence instead concerns eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
C:Check tunnel counters and NHRP registration after restoring matched encapsulation settings. This is a validation for another mechanism (DMVPN tunnel key consistency), where A GRE tunnel key mismatch can prevent compatible overlay traffic from being accepted. Here the evidence instead concerns eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
D:Observe multicast routing hello exchange and stable protocol neighbors across the overlay. This is a validation for another mechanism (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 eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
Question 668
During a scheduled validation at the Lincoln hospital campus, dMVPN spokes learn remote routes through a hub but cannot use direct spoke-to-spoke forwarding because the advertised next hop always points to the hub. Engineers must restore an operations uplink without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud.
- Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior.
- Compare NHRP authentication strings and registration failure causes at the hub and spoke.
- Inspect the routing protocol's next-hop handling, EIGRP split-horizon, and DMVPN phase architecture.
Explanation
Correct Answers
B:Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior. DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
D:Inspect the routing protocol's next-hop handling, EIGRP split-horizon, and DMVPN phase architecture. DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
Incorrect Answers
A:Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud. This is a configuration change for a different root cause (DMVPN NHRP network ID), where NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design. Here the evidence instead concerns eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
C:Compare NHRP authentication strings and registration failure causes at the hub and spoke. This is an investigation for a different failure condition (DMVPN NHRP authentication), where NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists. Here the evidence instead concerns eigrp on dmvpn hub: DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together.
Question 669
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 investigation should be prioritized before the engineer modifies configuration?
- Check feasibility, variance multiplier, traffic-share policy, and the actual metric ratio.
- Compare the configured EIGRP autonomous-system numbers and active interface participation.
- Inspect outstanding EIGRP queries, stub boundaries, and slow or unreachable neighbors.
- Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub.
Explanation
Correct Answer
C:Inspect outstanding EIGRP queries, stub boundaries, and slow or unreachable neighbors. EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
Incorrect Answers
A:Check feasibility, variance multiplier, traffic-share policy, and the actual metric ratio. This is an investigation for a different failure condition (EIGRP unequal-cost load balancing), where EIGRP variance enables unequal-cost traffic sharing only for qualifying loop-free candidates. 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: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 eigrp stuck-in-active: EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries.
D:Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub. This is an investigation for a different failure condition (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 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.