Cisco 300-410 Practice Test 30
Question 290
Following a production change at the Salem regional hub, a classless /27 connected subnet fails to appear as an external OSPF route after a broad redistribution change. The incident is affecting a tenant service; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything.
- Align the EIGRP process or named address-family AS number across the peers.
- Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate.
- Configure a consistent loopback update source and sufficient eBGP multihop hop limit.
Explanation
Correct Answer
A:Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything. Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Incorrect Answers
B:Align the EIGRP process or named address-family AS number across the peers. This is a configuration change for a different root cause (EIGRP AS mismatch), where EIGRP neighbors for an address family need compatible autonomous-system association and interface settings. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
C:Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate. This is a configuration change for a different root cause (EIGRP feasible successor), where The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
D:Configure a consistent loopback update source and sufficient eBGP multihop hop limit. This is a configuration change for a different root cause (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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Question 291
Following a production change at the Salem regional hub, a classless /27 connected subnet fails to appear as an external OSPF route after a broad redistribution change. The incident is affecting a tenant service; 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.
- Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears.
- Verify the external EIGRP route and plausible composite metric appear in neighbor tables.
Explanation
Correct Answer
B:Confirm a Type 5 or appropriate Type 7 external LSA represents only the authorized prefix. Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Incorrect Answers
A:Probe each component prefix and examine forwarding to ensure the summary does not attract unreachable traffic. This is a validation for another mechanism (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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
C: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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
D:Verify the external EIGRP route and plausible composite metric appear in neighbor tables. This is a validation for another mechanism (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Question 292
Following a production change at the Salem regional hub, a classless /27 connected subnet fails to appear as an external OSPF route after a broad redistribution change. The incident is affecting a tenant service; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Reapply the former metric and route-map configuration if new routes displace stable paths.
- Reinstate the prior specific route advertisement if the change redirects unrelated subnets.
- Undo the new redistribution scope if unexpected external routes appear.
- Restore the previous ordered route-map clauses if the permitted set becomes too broad.
Explanation
Correct Answer
C:Undo the new redistribution scope if unexpected external routes appear. Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Incorrect Answers
A: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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
B:Reinstate the prior specific route advertisement if the change redirects unrelated subnets. This is a rollback for a different component (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
D: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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Question 293
During a scheduled validation at the Toledo manufacturing plant, a redistribution route map includes a deny clause followed by a permit clause, and some authorized prefixes never reach the next routing process. Engineers must restore a business-critical application without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27.
- Inspect the route's selected source, prefix length, and administrative distance in the routing table.
- Inspect route-map sequence order, each match condition, and hit counts against the missing prefixes.
- Compare the destination's matching prefixes and their lengths, not merely route-source preference.
Explanation
Correct Answer
C:Inspect route-map sequence order, each match condition, and hit counts against the missing prefixes. Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
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 route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
B:Inspect the route's selected source, prefix length, and administrative distance in the routing table. This is an investigation for a different failure condition (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 route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
D: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 route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
Question 294
During a scheduled validation at the Toledo manufacturing plant, a redistribution route map includes a deny clause followed by a permit clause, and some authorized prefixes never reach the next routing process. Engineers must restore a business-critical application without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance.
- 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.
- Put the intended permit conditions before the catch-all deny or narrow the deny match.
Explanation
Correct Answer
D:Put the intended permit conditions before the catch-all deny or narrow the deny match. Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
Incorrect Answers
A: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 route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
B:Tag routes on first redistribution and deny that tag when importing them back into the source domain. This is a configuration change for a different root cause (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
C: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 route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
Question 295
During a scheduled validation at the Toledo manufacturing plant, a redistribution route map includes a deny clause followed by a permit clause, and some authorized prefixes never reach the next routing process. Engineers must restore a business-critical application without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Check resulting redistributed prefixes and route-map matches after refreshing policy application.
- Verify the external EIGRP route and plausible composite metric appear in neighbor tables.
- Verify reimported tagged routes are blocked while fresh authorized external prefixes remain visible.
- Probe each component prefix and examine forwarding to ensure the summary does not attract unreachable traffic.
Explanation
Correct Answer
A:Check resulting redistributed prefixes and route-map matches after refreshing policy application. Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
Incorrect Answers
B:Verify the external EIGRP route and plausible composite metric appear in neighbor tables. This is a validation for another mechanism (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
C:Verify reimported tagged routes are blocked while fresh authorized external prefixes remain visible. This is a validation for another mechanism (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
D:Probe each component prefix and examine forwarding to ensure the summary does not attract unreachable traffic. This is a validation for another mechanism (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 route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
Question 296
During a scheduled validation at the Toledo manufacturing plant, a redistribution route map includes a deny clause followed by a permit clause, and some authorized prefixes never reach the next routing process. 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?
- 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.
- Undo the new redistribution scope if unexpected external routes appear.
- Restore the last verified summary boundary and component advertisements if reachability worsens.
Explanation
Correct Answer
A:Restore the previous ordered route-map clauses if the permitted set becomes too broad. Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
Incorrect Answers
B: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 route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
C:Undo the new redistribution scope if unexpected external routes appear. This is a rollback for a different component (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
D:Restore the last verified summary boundary and component advertisements if reachability worsens. This is a rollback for a different component (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 route-map permit sequence: Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action.
Question 297
Following a production change at the Peoria enterprise edge, syslog messages from a router stop arriving after a management VRF change although the collector remains reachable from the correct source. 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 configured logging source-interface, VRF-aware transport, and collector allowlists.
- Inspect configured trap destination, trap enablement, notification type, and UDP transport.
- Compare local logging buffer settings with remote trap severity and collector-side filtering.
- Run the supported Cisco Catalyst Center Assurance path trace and examine hop-by-hop forwarding evidence.
Explanation
Correct Answer
A:Inspect configured logging source-interface, VRF-aware transport, and collector allowlists. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Incorrect Answers
B:Inspect configured trap destination, trap enablement, notification type, and UDP transport. This is an investigation for a different failure condition (SNMP traps versus polling), where SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
C:Compare local logging buffer settings with remote trap severity and collector-side filtering. This is an investigation for a different failure condition (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
D:Run the supported Cisco Catalyst Center Assurance path trace and examine hop-by-hop forwarding evidence. This is an investigation for a different failure condition (Catalyst Center path trace), where Assurance path-trace capabilities can isolate the segment traversed by traffic and support focused troubleshooting. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Question 298
Following a production change at the Peoria enterprise edge, syslog messages from a router stop arriving after a management VRF change although the collector remains reachable from the correct source. 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?
- Enable the intended interface-event SNMP notifications to the approved NMS recipient.
- Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue.
- Set the appropriate remote logging level and destination for the intended operational events.
- Set the intended reachable source-interface and VRF context for remote syslog traffic.
Explanation
Correct Answer
D:Set the intended reachable source-interface and VRF context for remote syslog traffic. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Incorrect Answers
A:Enable the intended interface-event SNMP notifications to the approved NMS recipient. This is a configuration change for a different root cause (SNMP traps versus polling), where SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
B:Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue. This is a configuration change for a different root cause (Catalyst Center client assurance), where Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
C:Set the appropriate remote logging level and destination for the intended operational events. This is a configuration change for a different root cause (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Question 299
Following a production change at the Peoria enterprise edge, syslog messages from a router stop arriving after a management VRF change although the collector remains reachable from the correct source. 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 only target events appear in the captured output without excessive CPU impact.
- Verify a test message reaches the collector from the approved router identity.
- Trigger a known test event and verify the message arrives with expected severity and facility.
- Generate known flows and verify cache entries and corresponding exported records.
Explanation
Correct Answer
B:Verify a test message reaches the collector from the approved router identity. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Incorrect Answers
A:Verify only target events appear in the captured output without excessive CPU impact. This is a validation for another mechanism (Conditional debugging), where Conditional debugs reduce diagnostic impact by restricting runtime detail to a relevant context. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
C:Trigger a known test event and verify the message arrives with expected severity and facility. This is a validation for another mechanism (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
D:Generate known flows and verify cache entries and corresponding exported records. This is a validation for another mechanism (Flexible NetFlow monitor attachment), where Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Question 300
Following a production change at the Peoria enterprise edge, syslog messages from a router stop arriving after a management VRF change although the collector remains reachable from the correct source. 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 earlier remote logging limits if the new level floods the collector.
- Revert the source-interface change if network policy rejects the replacement source address.
- Detach the monitor if it consumes excessive resources on an unsupported interface.
- Restore the previous exporter path if exports accidentally reach an external untrusted collector.
Explanation
Correct Answer
B:Revert the source-interface change if network policy rejects the replacement source address. Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
Incorrect Answers
A:Restore earlier remote logging limits if the new level floods the collector. This is a rollback for a different component (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
C:Detach the monitor if it consumes excessive resources on an unsupported interface. This is a rollback for a different component (Flexible NetFlow monitor attachment), where Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.
D:Restore the previous exporter path if exports accidentally reach an external untrusted collector. This is a rollback for a different component (NetFlow exporter destination), where Flow collection and export are distinct: valid local cache entries do not imply successful export transport. Here the evidence instead concerns syslog source interface: Syslog transport can fail when its source or VRF does not match collector reachability and access rules.