Cisco 300-410 Practice Test 80
Question 790
Following a production change at the Roanoke service-provider handoff, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. The incident is affecting a customer routing segment; 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.
- Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance.
- Put the intended permit conditions before the catch-all deny or narrow the deny match.
- Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything.
Explanation
Correct Answer
B:Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance. A longer matching prefix is selected before administrative distance is compared among equal-length routes.
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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
C: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
D: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Question 791
Following a production change at the Roanoke service-provider handoff, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. The incident is affecting a customer routing segment; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Use a destination-specific forwarding lookup to confirm which most-specific route is selected.
- 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.
Explanation
Correct Answer
A:Use a destination-specific forwarding lookup to confirm which most-specific route is selected. A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Incorrect Answers
B: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
C: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
D: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Question 792
Following a production change at the Roanoke service-provider handoff, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. 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?
- Reinstate the prior specific route advertisement if the change redirects unrelated subnets.
- Restore prior filtering and tag actions if production reaches previously excluded routes.
- Restore the previous ordered route-map clauses if the permitted set becomes too broad.
- Restore the previously recorded distances and route source if the intended failover changes.
Explanation
Correct Answer
A:Reinstate the prior specific route advertisement if the change redirects unrelated subnets. A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Incorrect Answers
B: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
D: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Question 793
Following a production change at the Naperville manufacturing plant, new VTY lines use the default AAA method list but all break-glass local users fail to authenticate. The incident is affecting a customer routing segment; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Check AAA accounting method lists, TACACS+ reachability, and whether the relevant lines/commands apply accounting.
- Inspect the separate IPv6 ACL and IPv6 traffic-filter binding on the intended interface and direction.
- Inspect the applied control-plane policy and classify actual OSPF packet counters versus default-class drops.
- Inspect local username/secret presence and effective AAA method list applied to the VTY lines.
Explanation
Correct Answer
D:Inspect local username/secret presence and effective AAA method list applied to the VTY lines. A local fallback requires valid local users and an AAA login method list that actually references the local database.
Incorrect Answers
A:Check AAA accounting method lists, TACACS+ reachability, and whether the relevant lines/commands apply accounting. This is an investigation for a different failure condition (AAA accounting records), where AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
B:Inspect the separate IPv6 ACL and IPv6 traffic-filter binding on the intended interface and direction. This is an investigation for a different failure condition (IPv6 traffic-filter placement), where IPv4 ACLs do not filter IPv6 packets; IPv6 traffic filters require their own attachment and careful ICMPv6 treatment. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
C:Inspect the applied control-plane policy and classify actual OSPF packet counters versus default-class drops. This is an investigation for a different failure condition (CoPP misclassification), where CoPP class maps and their policing rates determine which control-plane packets are forwarded to the CPU. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
Question 794
Following a production change at the Naperville manufacturing plant, new VTY lines use the default AAA method list but all break-glass local users fail to authenticate. The incident is affecting a customer routing segment; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Enable the appropriate AAA exec and command accounting to the authorized accounting server.
- Install a secure locally defined fallback credential with the correct AAA authentication binding.
- Rate-limit management traffic in a dedicated class sized for approved operations rather than the default drop class.
- Apply DHCPv6 guard to untrusted client ports and permit only the authorized server-facing path.
Explanation
Correct Answer
B:Install a secure locally defined fallback credential with the correct AAA authentication binding. A local fallback requires valid local users and an AAA login method list that actually references the local database.
Incorrect Answers
A:Enable the appropriate AAA exec and command accounting to the authorized accounting server. This is a configuration change for a different root cause (AAA accounting records), where AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
C:Rate-limit management traffic in a dedicated class sized for approved operations rather than the default drop class. This is a configuration change for a different root cause (CoPP management access), where Management packets destined to the router's CPU are subject to control-plane policing. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
D:Apply DHCPv6 guard to untrusted client ports and permit only the authorized server-facing path. This is a configuration change for a different root cause (DHCPv6 server guard), where DHCPv6 Guard helps prevent rogue DHCPv6 server messages from untrusted switch ports. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
Question 795
Following a production change at the Naperville manufacturing plant, new VTY lines use the default AAA method list but all break-glass local users fail to authenticate. The incident is affecting a customer routing segment; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Confirm a controlled test login uses local authentication only under the designed fallback condition.
- Verify monitoring traffic is permitted and nonapproved sources remain blocked.
- Confirm BGP keepalives and updates remain stable while excess unsolicited control traffic is limited.
- Perform a tagged test session and confirm complete accounting records reach the collector.
Explanation
Correct Answer
A:Confirm a controlled test login uses local authentication only under the designed fallback condition. A local fallback requires valid local users and an AAA login method list that actually references the local database.
Incorrect Answers
B:Verify monitoring traffic is permitted and nonapproved sources remain blocked. This is a validation for another mechanism (ACL implicit deny), where IP access lists implicitly deny traffic that matches no explicit permit statement. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
C:Confirm BGP keepalives and updates remain stable while excess unsolicited control traffic is limited. This is a validation for another mechanism (CoPP BGP class treatment), where CoPP can protect the route processor but over-restrictive classes can starve essential routing protocol traffic. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
D:Perform a tagged test session and confirm complete accounting records reach the collector. This is a validation for another mechanism (AAA accounting records), where AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
Question 796
Following a production change at the Naperville manufacturing plant, new VTY lines use the default AAA method list but all break-glass local users fail to authenticate. 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?
- Restore the earlier CoPP class or rate if BGP continues to flap.
- Restore the prior accounting configuration if new statements overwhelm the server or expose secrets.
- Remove temporary fallback users and reinstate previous line bindings if the recovery test fails.
- Restore prior ACL placement if unrelated production flows become blocked.
Explanation
Correct Answer
C:Remove temporary fallback users and reinstate previous line bindings if the recovery test fails. A local fallback requires valid local users and an AAA login method list that actually references the local database.
Incorrect Answers
A:Restore the earlier CoPP class or rate if BGP continues to flap. This is a rollback for a different component (CoPP BGP class treatment), where CoPP can protect the route processor but over-restrictive classes can starve essential routing protocol traffic. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
B:Restore the prior accounting configuration if new statements overwhelm the server or expose secrets. This is a rollback for a different component (AAA accounting records), where AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
D:Restore prior ACL placement if unrelated production flows become blocked. This is a rollback for a different component (Standard IPv4 ACL placement), where Standard IPv4 ACLs match source addresses, so placement can cause unintended broad filtering. Here the evidence instead concerns aaa local user authentication: A local fallback requires valid local users and an AAA login method list that actually references the local database.
Question 797
During a scheduled validation at the Albany service-provider handoff, a router sees an alternate EIGRP path in topology but cannot use it immediately as a feasible successor. Engineers must restore a customer routing segment without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Compare the alternate neighbor's reported distance with the current successor's feasible distance.
- Compare the configured EIGRP autonomous-system numbers and active interface participation.
- Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub.
- Check key IDs, configured authentication mode, key validity, and key strings at both ends.
Explanation
Correct Answer
A:Compare the alternate neighbor's reported distance with the current successor's feasible distance. The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
Incorrect Answers
B:Compare the configured EIGRP autonomous-system numbers and active interface participation. This is an investigation for a different failure condition (EIGRP AS mismatch), where EIGRP neighbors for an address family need compatible autonomous-system association and interface settings. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
C:Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub. This is an investigation for a different failure condition (EIGRP stub branch), where EIGRP stub limits query scope and is appropriate only where the device is not needed as transit. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
D:Check key IDs, configured authentication mode, key validity, and key strings at both ends. This is an investigation for a different failure condition (EIGRP neighbor authentication), where Routing authentication mismatches prevent EIGRP neighbors from exchanging trusted updates. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
Question 798
During a scheduled validation at the Albany service-provider handoff, a router sees an alternate EIGRP path in topology but cannot use it immediately as a feasible successor. Engineers must restore a customer routing segment without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Align the EIGRP process or named address-family AS number across the peers.
- Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes.
- Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate.
- Make metric-weight K-values consistent on both neighbors without changing unrelated routing policy.
Explanation
Correct Answer
C:Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate. The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
Incorrect Answers
A: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 eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
B:Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes. This is a configuration change for a different root cause (EIGRP stub branch), where EIGRP stub limits query scope and is appropriate only where the device is not needed as transit. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
D:Make metric-weight K-values consistent on both neighbors without changing unrelated routing policy. This is a configuration change for a different root cause (EIGRP K-value mismatch), where Traditional EIGRP neighbor adjacency requires compatible metric K-values. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
Question 799
During a scheduled validation at the Albany service-provider handoff, a router sees an alternate EIGRP path in topology but cannot use it immediately as a feasible successor. Engineers must restore a customer routing segment 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.
- Confirm a Type 5 or appropriate Type 7 external LSA represents only the authorized prefix.
- Inspect installed EIGRP paths and live forwarding distribution to verify expected sharing.
- Check whether the reported distance is strictly less than the feasible distance before declaring it feasible.
Explanation
Correct Answer
D:Check whether the reported distance is strictly less than the feasible distance before declaring it feasible. The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
Incorrect Answers
A: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 eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
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 eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
C:Inspect installed EIGRP paths and live forwarding distribution to verify expected sharing. This is a validation for another mechanism (EIGRP unequal-cost load balancing), where EIGRP variance enables unequal-cost traffic sharing only for qualifying loop-free candidates. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
Question 800
During a scheduled validation at the Albany service-provider handoff, a router sees an alternate EIGRP path in topology but cannot use it immediately as a feasible successor. 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?
- Undo new stub restrictions if required transit routes vanish.
- Restore the earlier variance when unstable links or excessive alternate load emerges.
- Restore the recorded K-values on both ends if metric recalculation disrupts path preferences.
- Revert manual metric manipulation if it introduces loops or inconsistent forwarding.
Explanation
Correct Answer
D:Revert manual metric manipulation if it introduces loops or inconsistent forwarding. The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
Incorrect Answers
A:Undo new stub restrictions if required transit routes vanish. This is a rollback for a different component (EIGRP stuck-in-active), where EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
B:Restore the earlier variance when unstable links or excessive alternate load emerges. This is a rollback for a different component (EIGRP unequal-cost load balancing), where EIGRP variance enables unequal-cost traffic sharing only for qualifying loop-free candidates. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.
C:Restore the recorded K-values on both ends if metric recalculation disrupts path preferences. This is a rollback for a different component (EIGRP K-value mismatch), where Traditional EIGRP neighbor adjacency requires compatible metric K-values. Here the evidence instead concerns eigrp feasible successor: The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance.