Cisco 300-410 Practice Test 10
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.
Question 91
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 verification result would provide the most relevant acceptance evidence?
- Verify virtual adjacency and restored backbone LSA connectivity without unintended topology loops.
- Check routing-table next hops across sites to verify preferred external exit selection.
- 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.
Explanation
Correct Answer
C: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: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.
B:Check routing-table next hops across sites to verify preferred external exit selection. This is a validation for another mechanism (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 hello and dead timers: OSPF timer compatibility is necessary for adjacency formation on a common segment.
D: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.
Question 92
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. The new configuration worsens service. Which controlled rollback should the team perform?
- Revert translation policy if external routes leak into areas that should not receive them.
- Restore earlier external metric policy if traffic shifts to a constrained circuit.
- Remove the virtual link after a direct backbone repair, or restore its last known endpoints if the change fails.
- Restore previous timers if the change disrupts other point-to-point peers.
Explanation
Correct Answer
D: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:Revert translation policy if external routes leak into areas that should not receive them. This is a rollback for a different component (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.
B:Restore earlier external metric policy if traffic shifts to a constrained circuit. This is a rollback for a different component (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 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.
Question 93
Following a production change at the Savannah branch site, two VPN customers use the same 10.1.0.0/16 space and their routes collide in a shared provider VPN control-plane design. 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?
- Inspect route-target extended communities on exported VPN routes and VRF import policy at the receiver.
- Check the outer transport LSP label and inner VPN service label purpose for the traffic.
- Inspect whether the VPNv4 or VPNv6 address family is activated and whether route targets travel as extended communities.
- Check how the PE constructs VPNv4 routes and whether each VRF uses a distinct route distinguisher.
Explanation
Correct Answer
D:Check how the PE constructs VPNv4 routes and whether each VRF uses a distinct route distinguisher. A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Incorrect Answers
A:Inspect route-target extended communities on exported VPN routes and VRF import policy at the receiver. This is an investigation for a different failure condition (MPLS VPN route target import), where Route targets control which VPNv4 routes a VRF imports and exports; an RD provides uniqueness rather than membership. Here the evidence instead concerns mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
B: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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
C:Inspect whether the VPNv4 or VPNv6 address family is activated and whether route targets travel as extended communities. This is an investigation for a different failure condition (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 vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Question 94
Following a production change at the Savannah branch site, two VPN customers use the same 10.1.0.0/16 space and their routes collide in a shared provider VPN control-plane design. 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?
- Assign appropriate distinct RDs so overlapping customer prefixes become unique VPN address-family entries.
- Align the intended export and import route targets while avoiding broader import of unrelated tenants.
- Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE.
- Update the authorized peer authentication mapping or identity policy to match the new underlay endpoint.
Explanation
Correct Answer
A:Assign appropriate distinct RDs so overlapping customer prefixes become unique VPN address-family entries. A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Incorrect Answers
B:Align the intended export and import route targets while avoiding broader import of unrelated tenants. This is a configuration change for a different root cause (MPLS VPN route target import), where Route targets control which VPNv4 routes a VRF imports and exports; an RD provides uniqueness rather than membership. Here the evidence instead concerns mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
C:Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE. This is a configuration change for a different root cause (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 vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Question 95
Following a production change at the Savannah branch site, two VPN customers use the same 10.1.0.0/16 space and their routes collide in a shared provider VPN control-plane design. 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?
- Check tunnel counters and NHRP registration after restoring matched encapsulation settings.
- Verify distinct VPNv4 prefixes appear with their corresponding RDs without cross-tenant forwarding.
- Confirm only approved VPN routes appear in the destination VRF with expected next-hop reachability.
- Check show ip nhrp and tunnel state for successful registration after the correction.
Explanation
Correct Answer
B:Verify distinct VPNv4 prefixes appear with their corresponding RDs without cross-tenant forwarding. A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Incorrect Answers
A:Check tunnel counters and NHRP registration after restoring matched encapsulation settings. This is a validation for another mechanism (DMVPN tunnel key consistency), where A GRE tunnel key mismatch can prevent compatible overlay traffic from being accepted. Here the evidence instead concerns mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
C:Confirm only approved VPN routes appear in the destination VRF with expected next-hop reachability. This is a validation for another mechanism (MPLS VPN route target import), where Route targets control which VPNv4 routes a VRF imports and exports; an RD provides uniqueness rather than membership. Here the evidence instead concerns mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
D:Check show ip nhrp and tunnel state for successful registration after the correction. This is a validation for another mechanism (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 vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Question 96
Following a production change at the Savannah branch site, two VPN customers use the same 10.1.0.0/16 space and their routes collide in a shared provider VPN control-plane design. The incident is affecting a voice service path; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Restore the earlier RD design if route updates unexpectedly withdraw active customer prefixes.
- Remove the new RT imports if other customers' routes become visible.
- Restore known-good LDP IDs if a migration introduces transport reachability failures.
- Restore the original network ID if the change merges previously separated DMVPN clouds.
Explanation
Correct Answer
A:Restore the earlier RD design if route updates unexpectedly withdraw active customer prefixes. A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Incorrect Answers
B:Remove the new RT imports if other customers' routes become visible. This is a rollback for a different component (MPLS VPN route target import), where Route targets control which VPNv4 routes a VRF imports and exports; an RD provides uniqueness rather than membership. Here the evidence instead concerns mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
C:Restore known-good LDP IDs if a migration introduces transport reachability failures. This is a rollback for a different component (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 vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Question 97
Following a production change at the Plano enterprise edge, a summarizing edge advertises 10.60.0.0/16 although one component /24 has been withdrawn, and traffic to that /24 is discarded. The incident is affecting an operations uplink; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Inspect route-map sequence order, each match condition, and hit counts against the missing prefixes.
- Trace route tags and redistribution points to identify reintroduction of the same route.
- Compare summary reachability with the actual set of component subnets and the summary discard route.
- Check whether the EIGRP redistribution policy supplies a usable seed metric.
Explanation
Correct Answer
C:Compare summary reachability with the actual set of component subnets and the summary discard route. An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
Incorrect Answers
A:Inspect route-map sequence order, each match condition, and hit counts against the missing prefixes. This is an investigation for a different failure condition (Route-map permit sequence), where Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action. Here the evidence instead concerns summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
B:Trace route tags and redistribution points to identify reintroduction of the same route. This is an investigation for a different failure condition (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
D: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 summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
Question 98
Following a production change at the Plano enterprise edge, a summarizing edge advertises 10.60.0.0/16 although one component /24 has been withdrawn, and traffic to that /24 is discarded. The incident is affecting an operations uplink; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Raise the static route's distance above the intended OSPF route or remove the unwanted override.
- Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything.
- Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage.
- Put the intended permit conditions before the catch-all deny or narrow the deny match.
Explanation
Correct Answer
C:Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage. An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
Incorrect Answers
A: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 summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
B:Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything. This is a configuration change for a different root cause (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
D:Put the intended permit conditions before the catch-all deny or narrow the deny match. This is a configuration change for a different root cause (Route-map permit sequence), where Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action. Here the evidence instead concerns summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
Question 99
Following a production change at the Plano enterprise edge, a summarizing edge advertises 10.60.0.0/16 although one component /24 has been withdrawn, and traffic to that /24 is discarded. The incident is affecting an operations uplink; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Probe each component prefix and examine forwarding to ensure the summary does not attract unreachable traffic.
- Confirm a Type 5 or appropriate Type 7 external LSA represents only the authorized prefix.
- Check resulting redistributed prefixes and route-map matches after refreshing policy application.
- Use a destination-specific forwarding lookup to confirm which most-specific route is selected.
Explanation
Correct Answer
A:Probe each component prefix and examine forwarding to ensure the summary does not attract unreachable traffic. An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
Incorrect Answers
B: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 summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
C:Check resulting redistributed prefixes and route-map matches after refreshing policy application. This is a validation for another mechanism (Route-map permit sequence), where Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action. Here the evidence instead concerns summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
D: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 summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
Question 100
Following a production change at the Plano enterprise edge, a summarizing edge advertises 10.60.0.0/16 although one component /24 has been withdrawn, and traffic to that /24 is discarded. The incident is affecting an operations uplink; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Restore the previously recorded distances and route source if the intended failover changes.
- Restore the last verified summary boundary and component advertisements if reachability worsens.
- Restore the previous ordered route-map clauses if the permitted set becomes too broad.
- Reapply the former metric and route-map configuration if new routes displace stable paths.
Explanation
Correct Answer
B:Restore the last verified summary boundary and component advertisements if reachability worsens. An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
Incorrect Answers
A:Restore the previously recorded distances and route source if the intended failover changes. This is a rollback for a different component (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 summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
C:Restore the previous ordered route-map clauses if the permitted set becomes too broad. This is a rollback for a different component (Route-map permit sequence), where Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action. Here the evidence instead concerns summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.
D:Reapply the former metric and route-map configuration if new routes displace stable paths. This is a rollback for a different component (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns summary route black hole: An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks.