Cisco 300-410 Practice Test 9
Question 80
Following a production change at the Eugene service-provider handoff, pE routers have an Established base BGP session, but no VPNv4 customer routes are exchanged. The incident is affecting a customer routing segment; 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.
- Revert the address-family change if unrelated VPN route exchanges begin unexpectedly.
- Restore the old PE-CE route policy if the new exchange advertises unintended customer networks.
- Remove unintended RT imports and restore prior VRF bindings if customer isolation is breached.
Explanation
Correct Answer
B:Revert the address-family change if unrelated VPN route exchanges begin unexpectedly. MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
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 mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
C:Restore the old PE-CE route policy if the new exchange advertises unintended customer networks. This is a rollback for a different component (PE-to-CE routing separation), where PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
D: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 mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Question 81
Following a production change at the Peoria enterprise edge, a transit label-switch router receives labeled packets but forwards them using an unexpected outgoing label after a core change. 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 the downstream-advertised implicit-null binding and the penultimate router's label operation.
- Check NHRP multicast mapping and the GRE mode used to carry multicast routing hellos.
- Compare GRE tunnel keys and tunnel modes between the affected DMVPN endpoints.
- Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB.
Explanation
Correct Answer
D:Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB. An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
Incorrect Answers
A: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 incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
B:Check NHRP multicast mapping and the GRE mode used to carry multicast routing hellos. This is an investigation for a different failure condition (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 incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
C: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 mpls incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
Question 82
Following a production change at the Peoria enterprise edge, a transit label-switch router receives labeled packets but forwards them using an unexpected outgoing label after a core change. 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?
- Correct the spoke's NHRP next-hop server and hub tunnel-to-NBMA map for its reachable hub.
- Retain the intended PHP behavior unless the architecture explicitly requires explicit-null handling.
- Repair the NHRP multicast map or dynamic mapping appropriate to hub/spoke roles.
- Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly.
Explanation
Correct Answer
D:Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly. An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
Incorrect Answers
A:Correct the spoke's NHRP next-hop server and hub tunnel-to-NBMA map for its reachable hub. This is a configuration change for a different root cause (DMVPN NHS mapping), where A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration. Here the evidence instead concerns mpls incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
B:Retain the intended PHP behavior unless the architecture explicitly requires explicit-null handling. This is a configuration change for a different root cause (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 incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
C: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 mpls incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
Question 83
Following a production change at the Peoria enterprise edge, a transit label-switch router receives labeled packets but forwards them using an unexpected outgoing label after a core change. 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?
- Trace each tenant's probe in its own VRF and verify distinct forwarding outcomes for identical destination prefixes.
- Verify IPsec SAs form and protected DMVPN traffic increments encapsulation/decapsulation counters.
- Verify the label stack operation at each hop and the expected egress reachability.
- Observe multicast routing hello exchange and stable protocol neighbors across the overlay.
Explanation
Correct Answer
C:Verify the label stack operation at each hop and the expected egress reachability. An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
Incorrect Answers
A:Trace each tenant's probe in its own VRF and verify distinct forwarding outcomes for identical destination prefixes. This is a validation for another mechanism (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 incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
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 mpls incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
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 mpls incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
Question 84
Following a production change at the Peoria enterprise edge, a transit label-switch router receives labeled packets but forwards them using an unexpected outgoing label after a core change. 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?
- Examine the selected LDP transport address and TCP reachability between LDP identifiers.
- Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB.
- Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly.
- Repair LDP adjacency or label distribution for the intended core path while keeping IGP reachability intact.
Explanation
Correct Answers
B:Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB. An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
C:Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly. An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
Incorrect Answers
A:Examine the selected LDP transport address and TCP reachability between LDP identifiers. This is an investigation for a different failure condition (LDP router-ID transport reachability), where LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable. Here the evidence instead concerns mpls incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
D:Repair LDP adjacency or label distribution for the intended core path while keeping IGP reachability intact. This is a configuration change for a different root cause (MPLS label assignment), where MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path. Here the evidence instead concerns mpls incoming versus outgoing labels: An LSR switches labels using its label forwarding information base, not the customer IP prefix alone.
Question 85
Following a production change at the Trenton data center, a prefix redistributed from OSPF into EIGRP is later imported back into OSPF at a second boundary and oscillates. 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 the redistribution source, subnets handling, and whether a match or prefix filter excludes /27.
- Compare the destination's matching prefixes and their lengths, not merely route-source preference.
- Check whether the EIGRP redistribution policy supplies a usable seed metric.
- Trace route tags and redistribution points to identify reintroduction of the same route.
Explanation
Correct Answer
D:Trace route tags and redistribution points to identify reintroduction of the same route. Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
Incorrect Answers
A:Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27. This is an investigation for a different failure condition (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
B:Compare the destination's matching prefixes and their lengths, not merely route-source preference. This is an investigation for a different failure condition (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
C:Check whether the EIGRP redistribution policy supplies a usable seed metric. This is an investigation for a different failure condition (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
Question 86
Following a production change at the Trenton data center, a prefix redistributed from OSPF into EIGRP is later imported back into OSPF at a second boundary and oscillates. 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?
- Tag routes on first redistribution and deny that tag when importing them back into the source domain.
- Provide the required EIGRP seed metric through redistribution or a route map for the intended source.
- Raise the static route's distance above the intended OSPF route or remove the unwanted override.
- Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance.
Explanation
Correct Answer
A:Tag routes on first redistribution and deny that tag when importing them back into the source domain. Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
Incorrect Answers
B:Provide the required EIGRP seed metric through redistribution or a route map for the intended source. This is a configuration change for a different root cause (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
C:Raise the static route's distance above the intended OSPF route or remove the unwanted override. This is a configuration change for a different root cause (Administrative distance), where For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
D:Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance. This is a configuration change for a different root cause (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
Question 87
Following a production change at the Trenton data center, a prefix redistributed from OSPF into EIGRP is later imported back into OSPF at a second boundary and oscillates. 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 a Type 5 or appropriate Type 7 external LSA represents only the authorized prefix.
- Verify reimported tagged routes are blocked while fresh authorized external prefixes remain visible.
- Use a destination-specific forwarding lookup to confirm which most-specific route is selected.
- Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears.
Explanation
Correct Answer
B:Verify reimported tagged routes are blocked while fresh authorized external prefixes remain visible. Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
Incorrect Answers
A:Confirm a Type 5 or appropriate Type 7 external LSA represents only the authorized prefix. This is a validation for another mechanism (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
C:Use a destination-specific forwarding lookup to confirm which most-specific route is selected. This is a validation for another mechanism (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
D:Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears. This is a validation for another mechanism (Administrative distance), where For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
Question 88
Following a production change at the Trenton data center, a prefix redistributed from OSPF into EIGRP is later imported back into OSPF at a second boundary and oscillates. 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?
- Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27.
- Trace route tags and redistribution points to identify reintroduction of the same route.
- Tag routes on first redistribution and deny that tag when importing them back into the source domain.
- Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage.
Explanation
Correct Answers
B:Trace route tags and redistribution points to identify reintroduction of the same route. Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
C:Tag routes on first redistribution and deny that tag when importing them back into the source domain. Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
Incorrect Answers
A:Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27. This is an investigation for a different failure condition (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
D:Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage. This is a configuration change for a different root cause (Summary route black hole), where An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks. Here the evidence instead concerns redistribution loop prevention tags: Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains.
Question 89
Following a production change at the Tacoma remote operations location, adjacent OSPF routers remain in Down or Init after a template change despite working IPv4 reachability. 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?
- Compare effective OSPF hello and dead timers and interface network types on both ends.
- Inspect the OSPF process router IDs and compare them across the affected area.
- Inspect the ABR's area range and confirm the source subnets actually belong to the summarized area.
- Compare interface MTUs and DBD packet handling rather than changing OSPF cost.
Explanation
Correct Answer
A:Compare effective OSPF hello and dead timers and interface network types on both ends. OSPF timer compatibility is necessary for adjacency formation on a common segment.
Incorrect Answers
B: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 hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
C:Inspect the ABR's area range and confirm the source subnets actually belong to the summarized area. This is an investigation for a different failure condition (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 hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
D:Compare interface MTUs and DBD packet handling rather than changing OSPF cost. This is an investigation for a different failure condition (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 90
Following a production change at the Tacoma remote operations location, adjacent OSPF routers remain in Down or Init after a template change despite working IPv4 reachability. 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?
- Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area.
- Align the effective IP MTU values on both interfaces before considering platform-specific workarounds.
- Apply the correct OSPF area-range summary at the ABR instead of an ASBR-only summary command.
- 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:Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area. This is a configuration change for a different root cause (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.
B:Align the effective IP MTU values on both interfaces before considering platform-specific workarounds. This is a configuration change for a different root cause (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: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 hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.