Cisco 300-410 Practice Test 53
Question 520
Following a production change at the Aurora remote operations location, spoke-to-spoke traffic continues hairpinning through the hub despite DMVPN phase 3 configuration. The incident is affecting management access; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Disable the shortcut change if dynamic mappings direct traffic to an untrusted or unreachable NBMA address.
- Restore the former NHS mapping if the hub migration was incomplete.
- Roll back the IPsec proposal atomically on both sides if secure tunnel establishment fails.
- Restore the original network ID if the change merges previously separated DMVPN clouds.
Explanation
Correct Answer
A:Disable the shortcut change if dynamic mappings direct traffic to an untrusted or unreachable NBMA address. DMVPN phase 3 uses hub redirects and spoke shortcuts to facilitate direct spoke-to-spoke forwarding.
Incorrect Answers
B:Restore the former NHS mapping if the hub migration was incomplete. This is a rollback for a different component (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 phase 3 shortcut: DMVPN phase 3 uses hub redirects and spoke shortcuts to facilitate direct spoke-to-spoke forwarding.
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 phase 3 shortcut: DMVPN phase 3 uses hub redirects and spoke shortcuts to facilitate direct spoke-to-spoke forwarding.
D:Restore the original network ID if the change merges previously separated DMVPN clouds. This is a rollback for a different component (DMVPN NHRP network ID), where NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design. Here the evidence instead concerns dmvpn phase 3 shortcut: DMVPN phase 3 uses hub redirects and spoke shortcuts to facilitate direct spoke-to-spoke forwarding.
Question 521
Following a production change at the Boise manufacturing plant, the hub and spokes use the same GRE underlay, but one spoke never appears in NHRP registration cache. The incident is affecting a voice service path; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Compare GRE tunnel keys and tunnel modes between the affected DMVPN endpoints.
- Inspect NHRP redirect generation on the hub and shortcut handling on spokes.
- Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces.
- Inspect the IKE peer identity, key selection, and authentication failure logs for the changed NBMA address.
Explanation
Correct Answer
C:Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Incorrect Answers
A:Compare GRE tunnel keys and tunnel modes between the affected DMVPN endpoints. This is an investigation for a different failure condition (DMVPN tunnel key consistency), where A GRE tunnel key mismatch can prevent compatible overlay traffic from being accepted. Here the evidence instead concerns dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
B:Inspect NHRP redirect generation on the hub and shortcut handling on spokes. This is an investigation for a different failure condition (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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
D: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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Question 522
Following a production change at the Boise manufacturing plant, the hub and spokes use the same GRE underlay, but one spoke never appears in NHRP registration cache. The incident is affecting a voice service path; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Repair the NHRP multicast map or dynamic mapping appropriate to hub/spoke roles.
- Align the tunnel key and compatible mGRE mode for all peers in the same DMVPN cloud.
- Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior.
- Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud.
Explanation
Correct Answer
D:Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Incorrect Answers
A:Repair the NHRP multicast map or dynamic mapping appropriate to hub/spoke roles. This is a configuration change for a different root cause (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 nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
B:Align the tunnel key and compatible mGRE mode for all peers in the same DMVPN cloud. This is a configuration change for a different root cause (DMVPN tunnel key consistency), where A GRE tunnel key mismatch can prevent compatible overlay traffic from being accepted. Here the evidence instead concerns dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
C: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 nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Question 523
Following a production change at the Boise manufacturing plant, the hub and spokes use the same GRE underlay, but one spoke never appears in NHRP registration cache. The incident is affecting a voice service path; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify remote routes and NHRP mappings support the planned direct path without looping.
- Verify IPsec SAs form and protected DMVPN traffic increments encapsulation/decapsulation counters.
- Check show ip nhrp and tunnel state for successful registration after the correction.
- Observe multicast routing hello exchange and stable protocol neighbors across the overlay.
Explanation
Correct Answer
C:Check show ip nhrp and tunnel state for successful registration after the correction. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Incorrect Answers
A:Verify remote routes and NHRP mappings support the planned direct path without looping. This is a validation for another mechanism (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 nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
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 nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Question 524
Following a production change at the Boise manufacturing plant, the hub and spokes use the same GRE underlay, but one spoke never appears in NHRP registration cache. The incident is affecting a voice service path; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Align supported IPsec proposals and tunnel protection profiles on both endpoints without downgrading policy.
- Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces.
- Compare NHRP authentication strings and registration failure causes at the hub and spoke.
- Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud.
Explanation
Correct Answers
B:Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
D:Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Incorrect Answers
A: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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Question 525
Following a production change at the Springfield hospital campus, client IPv6 hosts start selecting a malicious default gateway after a user plugs in a small rogue router. The incident is affecting a monitored campus segment; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Inspect AAA command-authorization method lists, server response attributes, and privilege level for the operator.
- Identify the ingress port carrying unauthorized Router Advertisements and inspect RA Guard trust role.
- Inspect uRPF drop counters and the reverse lookup's selected egress interface for the source address.
- Inspect the endpoint's learned IPv6 binding and whether source guard is applied to the untrusted port.
Explanation
Correct Answer
B:Identify the ingress port carrying unauthorized Router Advertisements and inspect RA Guard trust role. RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
Incorrect Answers
A:Inspect AAA command-authorization method lists, server response attributes, and privilege level for the operator. This is an investigation for a different failure condition (TACACS+ command authorization), where TACACS+ can authorize individual CLI commands separately from successful login authentication. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
C:Inspect uRPF drop counters and the reverse lookup's selected egress interface for the source address. This is an investigation for a different failure condition (Strict uRPF asymmetric routing), where Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
D:Inspect the endpoint's learned IPv6 binding and whether source guard is applied to the untrusted port. This is an investigation for a different failure condition (IPv6 source guard), where IPv6 source guard can filter source addresses against approved binding information. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
Question 526
Following a production change at the Springfield hospital campus, client IPv6 hosts start selecting a malicious default gateway after a user plugs in a small rogue router. The incident is affecting a monitored campus segment; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Rate-limit management traffic in a dedicated class sized for approved operations rather than the default drop class.
- Enable supported ND inspection and guard policies on the affected access segment with proper trust boundaries.
- Block RAs on untrusted access ports while allowing approved router-facing ports to send them.
- Use a policy or feasible uRPF mode appropriate for intentional asymmetry, or correct source routing where possible.
Explanation
Correct Answer
C:Block RAs on untrusted access ports while allowing approved router-facing ports to send them. RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
Incorrect Answers
A:Rate-limit management traffic in a dedicated class sized for approved operations rather than the default drop class. This is a configuration change for a different root cause (CoPP management access), where Management packets destined to the router's CPU are subject to control-plane policing. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
B:Enable supported ND inspection and guard policies on the affected access segment with proper trust boundaries. This is a configuration change for a different root cause (IPv6 Neighbor Discovery inspection), where IPv6 ND inspection uses neighbor state and filtering to mitigate neighbor-discovery spoofing. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
D:Use a policy or feasible uRPF mode appropriate for intentional asymmetry, or correct source routing where possible. This is a configuration change for a different root cause (Strict uRPF asymmetric routing), where Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
Question 527
Following a production change at the Springfield hospital campus, client IPv6 hosts start selecting a malicious default gateway after a user plugs in a small rogue router. The incident is affecting a monitored campus segment; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Validate known legitimate asymmetric flows pass while spoofed invalid-source packets remain denied.
- Validate forged neighbor advertisements are blocked and legitimate NS/NA traffic continues normally.
- Perform a tagged test session and confirm complete accounting records reach the collector.
- Send test RAs from both authorized and unauthorized ports and verify only the authorized default gateway is learned.
Explanation
Correct Answer
D:Send test RAs from both authorized and unauthorized ports and verify only the authorized default gateway is learned. RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
Incorrect Answers
A:Validate known legitimate asymmetric flows pass while spoofed invalid-source packets remain denied. This is a validation for another mechanism (Strict uRPF asymmetric routing), where Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
B:Validate forged neighbor advertisements are blocked and legitimate NS/NA traffic continues normally. This is a validation for another mechanism (IPv6 Neighbor Discovery inspection), where IPv6 ND inspection uses neighbor state and filtering to mitigate neighbor-discovery spoofing. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
C:Perform a tagged test session and confirm complete accounting records reach the collector. This is a validation for another mechanism (AAA accounting records), where AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
Question 528
Following a production change at the Springfield hospital campus, client IPv6 hosts start selecting a malicious default gateway after a user plugs in a small rogue router. The incident is affecting a monitored campus segment; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Identify the ingress port carrying unauthorized Router Advertisements and inspect RA Guard trust role.
- Block RAs on untrusted access ports while allowing approved router-facing ports to send them.
- Correct the scoped TACACS+ command set or method-list binding without granting unrestricted administrative privilege.
- Check whether the IPv6 binding table reflects the host's current VLAN, port and address.
Explanation
Correct Answers
A:Identify the ingress port carrying unauthorized Router Advertisements and inspect RA Guard trust role. RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
B:Block RAs on untrusted access ports while allowing approved router-facing ports to send them. RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
Incorrect Answers
C:Correct the scoped TACACS+ command set or method-list binding without granting unrestricted administrative privilege. This is a configuration change for a different root cause (TACACS+ command authorization), where TACACS+ can authorize individual CLI commands separately from successful login authentication. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
D:Check whether the IPv6 binding table reflects the host's current VLAN, port and address. This is an investigation for a different failure condition (IPv6 address binding table), where Several IPv6 first-hop security features rely on accurate host address and port bindings. Here the evidence instead concerns ipv6 router advertisement guard: RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments.
Question 529
During a scheduled validation at the Lansing hospital campus, link failures are visible in periodic NMS polling but no immediate event notifications arrive when an interface flaps. Engineers must restore a monitored campus segment without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect the authoritative engine ID and how user keys are localized to it.
- Check community string, configured NMS source ACL, UDP 161 reachability, and SNMP service counters.
- Inspect the VTY access-class, source subnet permit entries, and applied inbound direction.
- Inspect configured trap destination, trap enablement, notification type, and UDP transport.
Explanation
Correct Answer
D:Inspect configured trap destination, trap enablement, notification type, and UDP transport. SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
Incorrect Answers
A:Inspect the authoritative engine ID and how user keys are localized to it. This is an investigation for a different failure condition (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 snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
B:Check community string, configured NMS source ACL, UDP 161 reachability, and SNMP service counters. This is an investigation for a different failure condition (SNMPv2c read access), where SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption. Here the evidence instead concerns snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
C: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 snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
Question 530
During a scheduled validation at the Lansing hospital campus, link failures are visible in periodic NMS polling but no immediate event notifications arrive when an interface flaps. Engineers must restore a monitored campus segment without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Recreate or align SNMPv3 credentials for the new authoritative engine instead of reusing incompatible localized keys.
- Align the authorized read-only community and NMS source list without adding public write access.
- Enable the intended interface-event SNMP notifications to the approved NMS recipient.
- Repair synchronization to approved NTP sources and use consistent timestamp settings.
Explanation
Correct Answer
C:Enable the intended interface-event SNMP notifications to the approved NMS recipient. SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
Incorrect Answers
A:Recreate or align SNMPv3 credentials for the new authoritative engine instead of reusing incompatible localized keys. This is a configuration change for a different root cause (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 snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
B:Align the authorized read-only community and NMS source list without adding public write access. This is a configuration change for a different root cause (SNMPv2c read access), where SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption. Here the evidence instead concerns snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
D:Repair synchronization to approved NTP sources and use consistent timestamp settings. This is a configuration change for a different root cause (Time synchronization for logs), where Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps. Here the evidence instead concerns snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.