Cisco 300-410 Practice Test 33
Question 320
During a scheduled validation at the Bismarck warehouse network, a newly deployed spoke sends NHRP resolution queries but never learns the hub's tunnel-to-NBMA mapping. Engineers must restore management access without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the original network ID if the change merges previously separated DMVPN clouds.
- Restore the prior multicast map if the change floods routing hellos to unintended endpoints.
- Restore the former NHS mapping if the hub migration was incomplete.
- Revert the new peer identity mapping if it unexpectedly permits an unknown spoke.
Explanation
Correct Answer
C:Restore the former NHS mapping if the hub migration was incomplete. A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration.
Incorrect Answers
A: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 nhs mapping: A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration.
B: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 nhs mapping: A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration.
D: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 nhs mapping: A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration.
Question 321
Following a production change at the Boulder data center, link failures are visible in periodic NMS polling but no immediate event notifications arrive when an interface flaps. The incident is affecting a business-critical application; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Inspect IP SLA probe status, tracked object, and whether the static route references that object.
- Inspect the authoritative engine ID and how user keys are localized to it.
- Inspect configured trap destination, trap enablement, notification type, and UDP transport.
- Check community string, configured NMS source ACL, UDP 161 reachability, and SNMP service counters.
Explanation
Correct Answer
C: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 IP SLA probe status, tracked object, and whether the static route references that object. This is an investigation for a different failure condition (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 snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
B: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.
D: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.
Question 322
Following a production change at the Boulder data center, link failures are visible in periodic NMS polling but no immediate event notifications arrive when an interface flaps. The incident is affecting a business-critical application; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- 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.
- Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route.
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:Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route. This is a configuration change for a different root cause (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 snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
Question 323
Following a production change at the Boulder data center, link failures are visible in periodic NMS polling but no immediate event notifications arrive when an interface flaps. The incident is affecting a business-critical application; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Confirm successful SNMPv3 authentication to the new engine ID after credential repair.
- Compare event timestamps across devices after a known simultaneous test event.
- Verify authorized SNMP polling works and an unauthorized source remains blocked.
- Flap a test interface and confirm an event notification reaches the NMS promptly.
Explanation
Correct Answer
D:Flap a test interface and confirm an event notification reaches the NMS promptly. SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
Incorrect Answers
A:Confirm successful SNMPv3 authentication to the new engine ID after credential repair. This is a validation for another mechanism (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: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 snmp traps versus polling: SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events.
C:Verify authorized SNMP polling works and an unauthorized source remains blocked. This is a validation for another mechanism (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.
Question 324
Following a production change at the Boulder data center, link failures are visible in periodic NMS polling but no immediate event notifications arrive when an interface flaps. The incident is affecting a business-critical application; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Align the authorized read-only community and NMS source list without adding public write access.
- Inspect the authoritative engine ID and how user keys are localized to it.
- Inspect configured trap destination, trap enablement, notification type, and UDP transport.
- Enable the intended interface-event SNMP notifications to the approved NMS recipient.
Explanation
Correct Answers
C: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.
D: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: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.
B: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.
Question 325
During a scheduled validation at the Columbus enterprise edge, two OSPF routers remain in ExStart or Exchange after an interface MTU increase on only one side. Engineers must restore an operations uplink without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Compare external LSA metric types E1/E2 and internal cost to each ASBR.
- Compare interface MTUs and DBD packet handling rather than changing OSPF cost.
- Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior.
- Inspect the OSPF process router IDs and compare them across the affected area.
Explanation
Correct Answer
B:Compare interface MTUs and DBD packet handling rather than changing OSPF cost. An MTU mismatch can prevent OSPF database description exchange from completing.
Incorrect Answers
A:Compare external LSA metric types E1/E2 and internal cost to each ASBR. This is an investigation for a different failure condition (OSPF external route type), where OSPF E1 considers internal path cost with external cost, while E2 primarily compares the external metric. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
C:Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior. This is an investigation for a different failure condition (OSPF NSSA external route translation), where An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
D:Inspect the OSPF process router IDs and compare them across the affected area. This is an investigation for a different failure condition (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
Question 326
During a scheduled validation at the Columbus enterprise edge, two OSPF routers remain in ExStart or Exchange after an interface MTU increase on only one side. Engineers must restore an operations uplink without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Place both ends of the adjacency into the intended same area, leaving other area boundaries untouched.
- Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes.
- Select the appropriate external metric type and cost policy to reflect the enterprise exit preference.
- Align the effective IP MTU values on both interfaces before considering platform-specific workarounds.
Explanation
Correct Answer
D:Align the effective IP MTU values on both interfaces before considering platform-specific workarounds. An MTU mismatch can prevent OSPF database description exchange from completing.
Incorrect Answers
A:Place both ends of the adjacency into the intended same area, leaving other area boundaries untouched. This is a configuration change for a different root cause (OSPF area mismatch), where OSPF neighbors must agree on the local link's area ID. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
B:Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes. This is a configuration change for a different root cause (OSPF NSSA external route translation), where An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
C:Select the appropriate external metric type and cost policy to reflect the enterprise exit preference. This is a configuration change for a different root cause (OSPF external route type), where OSPF E1 considers internal path cost with external cost, while E2 primarily compares the external metric. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
Question 327
During a scheduled validation at the Columbus enterprise edge, two OSPF routers remain in ExStart or Exchange after an interface MTU increase on only one side. Engineers must restore an operations uplink without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation.
- Observe the neighbor reach Full state with stable hellos after correction.
- Confirm database exchange completes and the neighbor progresses to Full without dropped DBD packets.
- Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs.
Explanation
Correct Answer
C:Confirm database exchange completes and the neighbor progresses to Full without dropped DBD packets. An MTU mismatch can prevent OSPF database description exchange from completing.
Incorrect Answers
A:Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation. This is a validation for another mechanism (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
B:Observe the neighbor reach Full state with stable hellos after correction. This is a validation for another mechanism (OSPF hello and dead timers), where OSPF timer compatibility is necessary for adjacency formation on a common segment. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
D:Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs. This is a validation for another mechanism (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
Question 328
During a scheduled validation at the Columbus enterprise edge, two OSPF routers remain in ExStart or Exchange after an interface MTU increase on only one side. 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.
- Apply the correct OSPF area-range summary at the ABR instead of an ASBR-only summary command.
- Align the effective IP MTU values on both interfaces before considering platform-specific workarounds.
- Compare interface MTUs and DBD packet handling rather than changing OSPF cost.
- Compare external LSA metric types E1/E2 and internal cost to each ASBR.
Explanation
Correct Answers
B:Align the effective IP MTU values on both interfaces before considering platform-specific workarounds. An MTU mismatch can prevent OSPF database description exchange from completing.
C:Compare interface MTUs and DBD packet handling rather than changing OSPF cost. An MTU mismatch can prevent OSPF database description exchange from completing.
Incorrect Answers
A:Apply the correct OSPF area-range summary at the ABR instead of an ASBR-only summary command. This is a configuration change for a different root cause (OSPF interarea summarization), where OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
D:Compare external LSA metric types E1/E2 and internal cost to each ASBR. This is an investigation for a different failure condition (OSPF external route type), where OSPF E1 considers internal path cost with external cost, while E2 primarily compares the external metric. Here the evidence instead concerns ospf database exchange mtu: An MTU mismatch can prevent OSPF database description exchange from completing.
Question 329
During a scheduled validation at the Raleigh hospital campus, packets for 192.168.10.0/24 reach the wrong tenant after two enterprises with identical subnets are onboarded. Engineers must restore a monitored campus segment without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Check ingress VRF assignment, VRF route table, and imported route targets for tenant overlap.
- Check how the PE constructs VPNv4 routes and whether each VRF uses a distinct route distinguisher.
- Check the outer transport LSP label and inner VPN service label purpose for the traffic.
- Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation.
Explanation
Correct Answer
A:Check ingress VRF assignment, VRF route table, and imported route targets for tenant overlap. Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership.
Incorrect Answers
B:Check how the PE constructs VPNv4 routes and whether each VRF uses a distinct route distinguisher. This is an investigation for a different failure condition (MPLS VPN route distinguisher), where A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports. Here the evidence instead concerns customer overlapping addresses: Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership.
C:Check the outer transport LSP label and inner VPN service label purpose for the traffic. This is an investigation for a different failure condition (MPLS L3VPN label stack), where In MPLS L3VPN, the transport label carries packets across the core and the VPN label identifies the service at the egress PE. Here the evidence instead concerns customer overlapping addresses: Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership.
D:Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation. This is an investigation for a different failure condition (MPLS penultimate hop popping), where Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC. Here the evidence instead concerns customer overlapping addresses: Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership.
Question 330
During a scheduled validation at the Raleigh hospital campus, packets for 192.168.10.0/24 reach the wrong tenant after two enterprises with identical subnets are onboarded. Engineers must restore a monitored campus segment 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.
- Bind the tunnel to the correct reachable underlay source and update dependent NBMA mapping as needed.
- Correct the interface-to-VRF mapping and route-target isolation rather than renumbering both tenants.
- Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud.
Explanation
Correct Answer
C:Correct the interface-to-VRF mapping and route-target isolation rather than renumbering both tenants. Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership.
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 customer overlapping addresses: Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership.
B: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 customer overlapping addresses: Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership.
D: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 customer overlapping addresses: Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership.