Cisco 300-410 Practice Test 26
Question 250
During a scheduled validation at the Tempe data center, a small leaf branch receives EIGRP queries for destinations it could never provide, increasing convergence time. Engineers must restore a business-critical application without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate.
- Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes.
- Choose a variance that admits only loop-free feasible routes and does not exceed capacity constraints.
- Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link.
Explanation
Correct Answer
B:Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes. EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Incorrect Answers
A: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 eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
C:Choose a variance that admits only loop-free feasible routes and does not exceed capacity constraints. This is a configuration change for a different root cause (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 stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
D:Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link. This is a configuration change for a different root cause (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 stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Question 251
During a scheduled validation at the Tempe data center, a small leaf branch receives EIGRP queries for destinations it could never provide, increasing convergence time. Engineers must restore a business-critical application without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- 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.
- Check both peers appear in the EIGRP neighbor table and routes converge.
- Confirm core routers stop querying the stub for unrelated destinations while branch routes remain reachable.
Explanation
Correct Answer
D:Confirm core routers stop querying the stub for unrelated destinations while branch routes remain reachable. EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Incorrect Answers
A: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 stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
B:Check whether the reported distance is strictly less than the feasible distance before declaring it feasible. This is a validation for another mechanism (EIGRP feasible successor), where The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance. Here the evidence instead concerns eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
C:Check both peers appear in the EIGRP neighbor table and routes converge. This is a validation for another mechanism (EIGRP AS mismatch), where EIGRP neighbors for an address family need compatible autonomous-system association and interface settings. Here the evidence instead concerns eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Question 252
During a scheduled validation at the Tempe data center, a small leaf branch receives EIGRP queries for destinations it could never provide, increasing convergence time. 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 manual metric manipulation if it introduces loops or inconsistent forwarding.
- Restore the recorded K-values on both ends if metric recalculation disrupts path preferences.
- Remove the stub limitation if the router is subsequently used as a real transit path.
- Restore the earlier variance when unstable links or excessive alternate load emerges.
Explanation
Correct Answer
C:Remove the stub limitation if the router is subsequently used as a real transit path. EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Incorrect Answers
A:Revert manual metric manipulation if it introduces loops or inconsistent forwarding. This is a rollback for a different component (EIGRP feasible successor), where The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance. Here the evidence instead concerns eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
B: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 stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
D: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 stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Question 253
Following a production change at the Tempe branch site, an eBGP neighbor configured to use loopbacks cannot establish even though both loopback IPs are reachable. The incident is affecting a tenant service; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Inspect the received BGP next-hop address and its reachability in the IGP or VRF.
- Check the client's reflector-client configuration, session state, and cluster metadata.
- Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor.
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
Explanation
Correct Answer
D:Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Incorrect Answers
A:Inspect the received BGP next-hop address and its reachability in the IGP or VRF. This is an investigation for a different failure condition (BGP iBGP next-hop reachability), where An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
B:Check the client's reflector-client configuration, session state, and cluster metadata. This is an investigation for a different failure condition (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
C:Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor. This is an investigation for a different failure condition (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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Question 254
Following a production change at the Tempe branch site, an eBGP neighbor configured to use loopbacks cannot establish even though both loopback IPs are reachable. 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?
- Apply an explicit allowlist prefix policy outbound to the external BGP peer.
- Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability.
- Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship.
- Configure a consistent loopback update source and sufficient eBGP multihop hop limit.
Explanation
Correct Answer
D:Configure a consistent loopback update source and sufficient eBGP multihop hop limit. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
B:Use next-hop-self at the correct iBGP advertising boundary or repair the actual next-hop reachability. This is a configuration change for a different root cause (BGP iBGP next-hop reachability), where An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
C:Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship. This is a configuration change for a different root cause (BGP peer remote AS), where BGP neighbors must agree on configured peer AS identity and establish a TCP session. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Question 255
Following a production change at the Tempe branch site, an eBGP neighbor configured to use loopbacks cannot establish even though both loopback IPs are reachable. The incident is affecting a tenant service; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify the BGP session establishes and receives only authorized prefixes.
- Verify externally observed paths show the intended extra AS hops without losing prefix reachability.
- Verify TCP 179 establishment using the loopback source and an Established BGP session.
- Confirm the BGP next hop resolves and received routes become installable in the RIB.
Explanation
Correct Answer
C:Verify TCP 179 establishment using the loopback source and an Established BGP session. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Incorrect Answers
A:Verify the BGP session establishes and receives only authorized prefixes. This is a validation for another mechanism (BGP peer remote AS), where BGP neighbors must agree on configured peer AS identity and establish a TCP session. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
B: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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
D:Confirm the BGP next hop resolves and received routes become installable in the RIB. This is a validation for another mechanism (BGP iBGP next-hop reachability), where An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Question 256
Following a production change at the Tempe branch site, an eBGP neighbor configured to use loopbacks cannot establish even though both loopback IPs are reachable. 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?
- Remove unsupported multihop changes and restore the original direct-peering source if needed.
- Restore the original neighbor statement if the AS migration must be backed out.
- Undo reflector-client assignment if it creates an unintended reflection topology.
- Remove AS-path prepending if transit providers ignore it or connectivity degrades.
Explanation
Correct Answer
A:Remove unsupported multihop changes and restore the original direct-peering source if needed. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Incorrect Answers
B:Restore the original neighbor statement if the AS migration must be backed out. This is a rollback for a different component (BGP peer remote AS), where BGP neighbors must agree on configured peer AS identity and establish a TCP session. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
C:Undo reflector-client assignment if it creates an unintended reflection topology. This is a rollback for a different component (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
D:Remove AS-path prepending if transit providers ignore it or connectivity degrades. This is a rollback for a different component (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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Question 257
During a scheduled validation at the Norman remote operations location, a network operator can log in to a router but receives authorization failures for permitted show commands after a TACACS+ policy update. Engineers must restore remote-site route stability without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect AAA command-authorization method lists, server response attributes, and privilege level for the operator.
- Inspect VTY transport modes, SSH readiness, and AAA bindings for authorized administrators.
- Inspect the endpoint's learned IPv6 binding and whether source guard is applied to the untrusted port.
- Check whether the IPv6 binding table reflects the host's current VLAN, port and address.
Explanation
Correct Answer
A:Inspect AAA command-authorization method lists, server response attributes, and privilege level for the operator. TACACS+ can authorize individual CLI commands separately from successful login authentication.
Incorrect Answers
B:Inspect VTY transport modes, SSH readiness, and AAA bindings for authorized administrators. This is an investigation for a different failure condition (Router SSH hardened management), where SSH provides encrypted remote CLI transport; Telnet sends sessions without encryption. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
C:Inspect the endpoint's learned IPv6 binding and whether source guard is applied to the untrusted port. This is an investigation for a different failure condition (IPv6 source guard), where IPv6 source guard can filter source addresses against approved binding information. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
D:Check whether the IPv6 binding table reflects the host's current VLAN, port and address. This is an investigation for a different failure condition (IPv6 address binding table), where Several IPv6 first-hop security features rely on accurate host address and port bindings. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
Question 258
During a scheduled validation at the Norman remote operations location, a network operator can log in to a router but receives authorization failures for permitted show commands after a TACACS+ policy update. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Enable supported ND inspection and guard policies on the affected access segment with proper trust boundaries.
- Correct the scoped TACACS+ command set or method-list binding without granting unrestricted administrative privilege.
- Enable appropriate source-reachability validation with an explicit exception policy if required by design.
- Tie the SSH permit to a correctly defined time range and synchronize device time.
Explanation
Correct Answer
B:Correct the scoped TACACS+ command set or method-list binding without granting unrestricted administrative privilege. TACACS+ can authorize individual CLI commands separately from successful login authentication.
Incorrect Answers
A:Enable supported ND inspection and guard policies on the affected access segment with proper trust boundaries. This is a configuration change for a different root cause (IPv6 Neighbor Discovery inspection), where IPv6 ND inspection uses neighbor state and filtering to mitigate neighbor-discovery spoofing. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
C:Enable appropriate source-reachability validation with an explicit exception policy if required by design. This is a configuration change for a different root cause (Loose uRPF source validation), where Loose uRPF primarily verifies that some acceptable reverse route exists instead of demanding the same ingress interface. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
D:Tie the SSH permit to a correctly defined time range and synchronize device time. This is a configuration change for a different root cause (Time-based ACL), where Time-based ACL entries depend on correct local time and an actively applied time-range definition. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
Question 259
During a scheduled validation at the Norman remote operations location, a network operator can log in to a router but receives authorization failures for permitted show commands after a TACACS+ policy update. Engineers must restore remote-site route stability without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Test unroutable spoofed sources and valid externally routed sources with counters.
- Confirm the current binding exists and legitimate IPv6 packets pass the guard.
- Verify monitoring traffic is permitted and nonapproved sources remain blocked.
- Confirm permitted commands execute while prohibited configuration commands are still rejected and logged.
Explanation
Correct Answer
D:Confirm permitted commands execute while prohibited configuration commands are still rejected and logged. TACACS+ can authorize individual CLI commands separately from successful login authentication.
Incorrect Answers
A:Test unroutable spoofed sources and valid externally routed sources with counters. This is a validation for another mechanism (Loose uRPF source validation), where Loose uRPF primarily verifies that some acceptable reverse route exists instead of demanding the same ingress interface. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
B:Confirm the current binding exists and legitimate IPv6 packets pass the guard. This is a validation for another mechanism (IPv6 address binding table), where Several IPv6 first-hop security features rely on accurate host address and port bindings. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
C: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 tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
Question 260
During a scheduled validation at the Norman remote operations location, a network operator can log in to a router but receives authorization failures for permitted show commands after a TACACS+ policy update. Engineers must restore remote-site route stability without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the former ACL order if the specific permit unintentionally opens additional sources.
- Restore the previous server command set if the change unintentionally expands administrator access.
- Restore the prior accounting configuration if new statements overwhelm the server or expose secrets.
- Reinstate the old management exception if remote administration is lost.
Explanation
Correct Answer
B:Restore the previous server command set if the change unintentionally expands administrator access. TACACS+ can authorize individual CLI commands separately from successful login authentication.
Incorrect Answers
A:Restore the former ACL order if the specific permit unintentionally opens additional sources. This is a rollback for a different component (Extended ACL first-match semantics), where Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
C: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 tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
D:Reinstate the old management exception if remote administration is lost. This is a rollback for a different component (CoPP management access), where Management packets destined to the router's CPU are subject to control-plane policing. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.