Cisco 300-410 Practice Test 42
Question 410
During a scheduled validation at the Fresno data center, a route map is defined for steering finance traffic to a backup next hop, but packets still follow the normal routing table. Engineers must restore a customer routing segment without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Apply an explicit allowlist prefix policy outbound to the external BGP peer.
- Select the appropriate external metric type and cost policy to reflect the enterprise exit preference.
- Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage.
- Apply the correct policy route map inbound on the ingress interface after verifying its match scope.
Explanation
Correct Answer
D:Apply the correct policy route map inbound on the ingress interface after verifying its match scope. Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Incorrect Answers
A:Apply an explicit allowlist prefix policy outbound to the external BGP peer. This is a configuration change for a different root cause (BGP prefix leak prevention), where BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
B: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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
C: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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Question 411
During a scheduled validation at the Fresno data center, a route map is defined for steering finance traffic to a backup next hop, but packets still follow the normal routing table. Engineers must restore a customer routing segment without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Use interface policy statistics and controlled test flows to prove matching packets take the alternate next hop.
- Simulate forwarding loss and confirm BFD signals the routing neighbor quickly without flapping.
- Confirm database exchange completes and the neighbor progresses to Full without dropped DBD packets.
- Verify externally observed paths show the intended extra AS hops without losing prefix reachability.
Explanation
Correct Answer
A:Use interface policy statistics and controlled test flows to prove matching packets take the alternate next hop. Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Incorrect Answers
B:Simulate forwarding loss and confirm BFD signals the routing neighbor quickly without flapping. This is a validation for another mechanism (BFD fast-failure detection), where Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
C: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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
D:Verify externally observed paths show the intended extra AS hops without losing prefix reachability. This is a validation for another mechanism (BGP inbound traffic engineering), where AS-path prepending can make an advertised path less attractive to remote BGP networks, but cannot guarantee inbound routing. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Question 412
During a scheduled validation at the Fresno data center, a route map is defined for steering finance traffic to a backup next hop, but packets still follow the normal routing table. Engineers must restore a customer routing segment without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore prior filtering and tag actions if production reaches previously excluded routes.
- Remove the new inbound policy from the interface if nonfinance traffic is diverted.
- Remove unsupported multihop changes and restore the original direct-peering source if needed.
- Restore the last valid area configuration if routes leak across unintended boundaries.
Explanation
Correct Answer
B:Remove the new inbound policy from the interface if nonfinance traffic is diverted. Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Incorrect Answers
A:Restore prior filtering and tag actions if production reaches previously excluded routes. This is a rollback for a different component (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
C:Remove unsupported multihop changes and restore the original direct-peering source if needed. This is a rollback for a different component (Loopback-sourced eBGP session), where Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
D: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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Question 413
During a scheduled validation at the Fargo service-provider handoff, an ASBR in an NSSA injects external routes that never become visible as Type 5 LSAs outside the area. Engineers must restore a business-critical application without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect the ABR's area range and confirm the source subnets actually belong to the summarized area.
- Inspect the OSPF process router IDs and compare them across the affected area.
- Compare OSPF stub flags and area type on every router participating in the area.
- Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior.
Explanation
Correct Answer
D:Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior. An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
Incorrect Answers
A: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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
C:Compare OSPF stub flags and area type on every router participating in the area. This is an investigation for a different failure condition (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
Question 414
During a scheduled validation at the Fargo service-provider handoff, an ASBR in an NSSA injects external routes that never become visible as Type 5 LSAs outside the area. Engineers must restore a business-critical application 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.
- Make stub-area settings consistent across the area, including its ABRs.
- Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes.
- Align the effective IP MTU values on both interfaces before considering platform-specific workarounds.
Explanation
Correct Answer
C:Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes. An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
B: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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
D: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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
Question 415
During a scheduled validation at the Fargo service-provider handoff, an ASBR in an NSSA injects external routes that never become visible as Type 5 LSAs outside the area. Engineers must restore a business-critical application 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.
- 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 the external prefix appears as Type 7 within NSSA and translated Type 5 where required.
Explanation
Correct Answer
D:Confirm the external prefix appears as Type 7 within NSSA and translated Type 5 where required. An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
B: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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
C: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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
Question 416
During a scheduled validation at the Fargo service-provider handoff, an ASBR in an NSSA injects external routes that never become visible as Type 5 LSAs outside the area. Engineers must restore a business-critical application without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Revert translation policy if external routes leak into areas that should not receive them.
- Remove the virtual link after a direct backbone repair, or restore its last known endpoints if the change fails.
- Roll back the area-type change across all affected routers if the design requires external LSAs.
- Return to the previous common MTU if larger packets fail elsewhere on the path.
Explanation
Correct Answer
A:Revert translation policy if external routes leak into areas that should not receive them. An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
Incorrect Answers
B: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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
C:Roll back the area-type change across all affected routers if the design requires external LSAs. This is a rollback for a different component (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
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 nssa external route translation: An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR.
Question 417
Following a production change at the Bend distribution campus, an access router was moved to area 20 while its adjacent distribution interface is still in area 0; no OSPF adjacency forms. 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?
- Compare external LSA metric types E1/E2 and internal cost to each ASBR.
- Inspect the OSPF process router IDs and compare them across the affected area.
- Check ABR topology and ensure the proposed transit area can support an OSPF virtual link.
- Check the area ID on the actual peering interfaces on both sides.
Explanation
Correct Answer
D:Check the area ID on the actual peering interfaces on both sides. OSPF neighbors must agree on the local link's area ID. The reported event is: Following a production change at the Bend distribution campus, an access router was moved to area 20 while its adjacent distribution interface is still in area 0; no OSPF adjacency forms. The incident is affecting an operations uplink; the response team has a rollback window.
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 area mismatch: OSPF neighbors must agree on the local link's area ID.
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 area mismatch: OSPF neighbors must agree on the local link's area ID.
C:Check ABR topology and ensure the proposed transit area can support an OSPF virtual link. This is an investigation for a different failure condition (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 area mismatch: OSPF neighbors must agree on the local link's area ID.
Question 418
Following a production change at the Bend distribution campus, an access router was moved to area 20 while its adjacent distribution interface is still in area 0; no OSPF adjacency forms. 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?
- 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.
- Place both ends of the adjacency into the intended same area, leaving other area boundaries untouched.
- Apply the correct OSPF area-range summary at the ABR instead of an ASBR-only summary command.
Explanation
Correct Answer
C:Place both ends of the adjacency into the intended same area, leaving other area boundaries untouched. OSPF neighbors must agree on the local link's area ID.
Incorrect Answers
A: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 area mismatch: OSPF neighbors must agree on the local link's area ID.
B: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 area mismatch: OSPF neighbors must agree on the local link's area ID.
D: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 area mismatch: OSPF neighbors must agree on the local link's area ID.
Question 419
Following a production change at the Bend distribution campus, an access router was moved to area 20 while its adjacent distribution interface is still in area 0; no OSPF adjacency forms. The incident is affecting an operations uplink; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify adjacency reaches Full and LSAs are exchanged in the expected area.
- Check routing-table next hops across sites to verify preferred external exit selection.
- Confirm the external prefix appears as Type 7 within NSSA and translated Type 5 where required.
- Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation.
Explanation
Correct Answer
A:Verify adjacency reaches Full and LSAs are exchanged in the expected area. OSPF neighbors must agree on the local link's area ID. The reported event is: Following a production change at the Bend distribution campus, an access router was moved to area 20 while its adjacent distribution interface is still in area 0; no OSPF adjacency forms. The incident is affecting an operations uplink; the response team has a rollback window.
Incorrect Answers
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 area mismatch: OSPF neighbors must agree on the local link's area ID.
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 area mismatch: OSPF neighbors must agree on the local link's area ID.
D: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 area mismatch: OSPF neighbors must agree on the local link's area ID.
Question 420
Following a production change at the Bend distribution campus, an access router was moved to area 20 while its adjacent distribution interface is still in area 0; no OSPF adjacency forms. 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 last valid area configuration if routes leak across unintended boundaries.
- Revert translation policy if external routes leak into areas that should not receive them.
- Roll back the area-type change across all affected routers if the design requires external LSAs.
- Restore previous timers if the change disrupts other point-to-point peers.
Explanation
Correct Answer
A:Restore the last valid area configuration if routes leak across unintended boundaries. OSPF neighbors must agree on the local link's area ID.
Incorrect Answers
B: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 area mismatch: OSPF neighbors must agree on the local link's area ID.
C:Roll back the area-type change across all affected routers if the design requires external LSAs. This is a rollback for a different component (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf area mismatch: OSPF neighbors must agree on the local link's area ID.
D:Restore previous timers if the change disrupts other point-to-point peers. This is a rollback for a different component (OSPF hello and dead timers), where OSPF timer compatibility is necessary for adjacency formation on a common segment. Here the evidence instead concerns ospf area mismatch: OSPF neighbors must agree on the local link's area ID.