Cisco 300-410 Practice Test 48
Question 470
During a scheduled validation at the Lubbock regional hub, adjacent OSPF routers remain in Down or Init after a template change despite working IPv4 reachability. Engineers must restore a tenant service without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Make stub-area settings consistent across the area, including its ABRs.
- Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes.
- Assign a unique stable router ID to the conflicting router and restart the process in a controlled window if necessary.
- Align the OSPF timer pair and compatible network type for the shared segment.
Explanation
Correct Answer
D:Align the OSPF timer pair and compatible network type for the shared segment. OSPF timer compatibility is necessary for adjacency formation on a common segment.
Incorrect Answers
A:Make stub-area settings consistent across the area, including its ABRs. This is a configuration change for a different root cause (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
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 hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
C:Assign a unique stable router ID to the conflicting router and restart the process in a controlled window if necessary. This is a configuration change for a different root cause (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns ospf hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
Question 471
During a scheduled validation at the Lubbock regional hub, adjacent OSPF routers remain in Down or Init after a template change despite working IPv4 reachability. Engineers must restore a tenant service without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Confirm database exchange completes and the neighbor progresses to Full without dropped DBD packets.
- Observe the neighbor reach Full state with stable hellos after correction.
- Confirm the external prefix appears as Type 7 within NSSA and translated Type 5 where required.
- Verify virtual adjacency and restored backbone LSA connectivity without unintended topology loops.
Explanation
Correct Answer
B:Observe the neighbor reach Full state with stable hellos after correction. OSPF timer compatibility is necessary for adjacency formation on a common segment.
Incorrect Answers
A:Confirm database exchange completes and the neighbor progresses to Full without dropped DBD packets. This is a validation for another mechanism (OSPF database exchange MTU), where An MTU mismatch can prevent OSPF database description exchange from completing. Here the evidence instead concerns ospf hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
C:Confirm the external prefix appears as Type 7 within NSSA and translated Type 5 where required. This is a validation for another mechanism (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 hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
D:Verify virtual adjacency and restored backbone LSA connectivity without unintended topology loops. This is a validation for another mechanism (OSPF backbone continuity), where An OSPF virtual link extends backbone connectivity through a suitable transit area; it is not built across a stub area. Here the evidence instead concerns ospf hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
Question 472
During a scheduled validation at the Lubbock regional hub, adjacent OSPF routers remain in Down or Init after a template change despite working IPv4 reachability. Engineers must restore a tenant service without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the last valid area configuration if routes leak across unintended boundaries.
- Restore previous timers if the change disrupts other point-to-point peers.
- Remove the virtual link after a direct backbone repair, or restore its last known endpoints if the change fails.
- Return to the previous common MTU if larger packets fail elsewhere on the path.
Explanation
Correct Answer
B:Restore previous timers if the change disrupts other point-to-point peers. OSPF timer compatibility is necessary for adjacency formation on a common segment.
Incorrect Answers
A:Restore the last valid area configuration if routes leak across unintended boundaries. This is a rollback for a different component (OSPF area mismatch), where OSPF neighbors must agree on the local link's area ID. Here the evidence instead concerns ospf hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
C:Remove the virtual link after a direct backbone repair, or restore its last known endpoints if the change fails. This is a rollback for a different component (OSPF backbone continuity), where An OSPF virtual link extends backbone connectivity through a suitable transit area; it is not built across a stub area. Here the evidence instead concerns ospf hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
D:Return to the previous common MTU if larger packets fail elsewhere on the path. This is a rollback for a different component (OSPF database exchange MTU), where An MTU mismatch can prevent OSPF database description exchange from completing. Here the evidence instead concerns ospf hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
Question 473
Following a production change at the Spokane regional hub, a provider router sees an IP route for a customer prefix but no corresponding label forwarding entry on an expected MPLS path. 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 LDP neighbor state, label bindings, and the forwarding table for the forwarding equivalence class.
- Inspect NHRP redirect generation on the hub and shortcut handling on spokes.
- Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB.
- Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation.
Explanation
Correct Answer
A:Inspect LDP neighbor state, label bindings, and the forwarding table for the forwarding equivalence class. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Incorrect Answers
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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
C:Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB. This is an investigation for a different failure condition (MPLS incoming versus outgoing labels), where An LSR switches labels using its label forwarding information base, not the customer IP prefix alone. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Question 474
Following a production change at the Spokane regional hub, a provider router sees an IP route for a customer prefix but no corresponding label forwarding entry on an expected MPLS path. 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?
- 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.
- Assign appropriate distinct RDs so overlapping customer prefixes become unique VPN address-family entries.
- Repair LDP adjacency or label distribution for the intended core path while keeping IGP reachability intact.
Explanation
Correct Answer
D:Repair LDP adjacency or label distribution for the intended core path while keeping IGP reachability intact. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
C:Assign appropriate distinct RDs so overlapping customer prefixes become unique VPN address-family entries. This is a configuration change for a different root cause (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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Question 475
Following a production change at the Spokane regional hub, a provider router sees an IP route for a customer prefix but no corresponding label forwarding entry on an expected MPLS path. 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?
- Capture ingress and egress label operations and confirm the egress PE selects the intended customer VRF.
- Compare control-plane bindings with the LFIB and verify labeled packets reach the next-hop router.
- Verify VPN NLRI and extended communities are received and imported into the correct VRFs.
- Verify IPsec SAs form and protected DMVPN traffic increments encapsulation/decapsulation counters.
Explanation
Correct Answer
B:Compare control-plane bindings with the LFIB and verify labeled packets reach the next-hop router. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Incorrect Answers
A:Capture ingress and egress label operations and confirm the egress PE selects the intended customer VRF. This is a validation for another mechanism (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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
C:Verify VPN NLRI and extended communities are received and imported into the correct VRFs. This is a validation for another mechanism (MP-BGP VPNv4 address family), where MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
D: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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Question 476
Following a production change at the Spokane regional hub, a provider router sees an IP route for a customer prefix but no corresponding label forwarding entry on an expected MPLS path. The incident is affecting a business-critical application; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Revert any change that strips the VPN label before the egress PE can identify the target VRF.
- Remove unintended RT imports and restore prior VRF bindings if customer isolation is breached.
- Restore the prior multicast map if the change floods routing hellos to unintended endpoints.
- Restore the previous LDP transport or interface configuration if label forwarding becomes inconsistent.
Explanation
Correct Answer
D:Restore the previous LDP transport or interface configuration if label forwarding becomes inconsistent. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Incorrect Answers
A:Revert any change that strips the VPN label before the egress PE can identify the target VRF. This is a rollback for a different component (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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
B:Remove unintended RT imports and restore prior VRF bindings if customer isolation is breached. This is a rollback for a different component (Customer overlapping addresses), where Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
C: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 mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Question 477
Following a production change at the Roanoke service-provider handoff, a spoke's NHRP adjacency worked until the IPsec proposal changed, after which GRE-over-IPsec traffic stops. 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?
- Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces.
- Compare IKE/IPsec negotiation output, transform proposals, key lifetimes, and peer reachability.
- 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 Answer
B:Compare IKE/IPsec negotiation output, transform proposals, key lifetimes, and peer reachability. DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
Incorrect Answers
A:Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces. This is an investigation for a different failure condition (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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
D:Inspect the routing protocol's next-hop handling, EIGRP split-horizon, and DMVPN phase architecture. This is an investigation for a different failure condition (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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
Question 478
Following a production change at the Roanoke service-provider handoff, a spoke's NHRP adjacency worked until the IPsec proposal changed, after which GRE-over-IPsec traffic stops. 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?
- Bind the tunnel to the correct reachable underlay source and update dependent NBMA mapping as needed.
- Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud.
- Align supported IPsec proposals and tunnel protection profiles on both endpoints without downgrading policy.
- Update the authorized peer authentication mapping or identity policy to match the new underlay endpoint.
Explanation
Correct Answer
C:Align supported IPsec proposals and tunnel protection profiles on both endpoints without downgrading policy. DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
Incorrect Answers
A: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 dmvpn ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
B: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 dmvpn ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
D: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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
Question 479
Following a production change at the Roanoke service-provider handoff, a spoke's NHRP adjacency worked until the IPsec proposal changed, after which GRE-over-IPsec traffic stops. 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?
- Verify a spoke obtains a shortcut mapping and subsequent traffic uses a direct spoke-to-spoke tunnel.
- Observe multicast routing hello exchange and stable protocol neighbors across the overlay.
- 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.
Explanation
Correct Answer
D:Verify IPsec SAs form and protected DMVPN traffic increments encapsulation/decapsulation counters. DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
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 dmvpn ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
B: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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
C: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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
Question 480
Following a production change at the Roanoke service-provider handoff, a spoke's NHRP adjacency worked until the IPsec proposal changed, after which GRE-over-IPsec traffic stops. The incident is affecting a business-critical application; 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 prior multicast map if the change floods routing hellos to unintended endpoints.
- 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.
Explanation
Correct Answer
D:Roll back the IPsec proposal atomically on both sides if secure tunnel establishment fails. DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
Incorrect Answers
A:Disable the shortcut change if dynamic mappings direct traffic to an untrusted or unreachable NBMA address. This is a rollback for a different component (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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
C: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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.