Cisco 300-410 Practice Test 15
Question 140
During a scheduled validation at the Fresno data center, administrative logins authenticate successfully, but the audit system receives no reliable command or session records. 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?
- Remove the new exception if it allows unauthorized management probes.
- 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.
- Temporarily revert the guard if legitimate static-address hosts lack registered bindings.
Explanation
Correct Answer
B:Restore the prior accounting configuration if new statements overwhelm the server or expose secrets. AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events.
Incorrect Answers
A:Remove the new exception if it allows unauthorized management probes. This is a rollback for a different component (ACL implicit deny), where IP access lists implicitly deny traffic that matches no explicit permit statement. Here the evidence instead concerns aaa accounting records: AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events.
C:Remove temporary fallback users and reinstate previous line bindings if the recovery test fails. This is a rollback for a different component (AAA local user authentication), where A local fallback requires valid local users and an AAA login method list that actually references the local database. Here the evidence instead concerns aaa accounting records: AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events.
D:Temporarily revert the guard if legitimate static-address hosts lack registered bindings. This is a rollback for a different component (IPv6 source guard), where IPv6 source guard can filter source addresses against approved binding information. Here the evidence instead concerns aaa accounting records: AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events.
Question 141
During a scheduled validation at the Savannah data center, a BGP session remains Idle or Active after the neighbor router's autonomous-system assignment changes. Engineers must restore a tenant service without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect local preference distributed in iBGP along with route selection results.
- Inspect TCP reachability and confirm the neighbor's configured remote-as matches its new AS.
- Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor.
- Check the client's reflector-client configuration, session state, and cluster metadata.
Explanation
Correct Answer
B:Inspect TCP reachability and confirm the neighbor's configured remote-as matches its new AS. BGP neighbors must agree on configured peer AS identity and establish a TCP session.
Incorrect Answers
A:Inspect local preference distributed in iBGP along with route selection results. This is an investigation for a different failure condition (BGP outbound path local preference), where Within an AS, higher BGP local preference normally wins before AS-path length and MED. Here the evidence instead concerns bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
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 bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
D: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 bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
Question 142
During a scheduled validation at the Savannah data center, a BGP session remains Idle or Active after the neighbor router's autonomous-system assignment changes. Engineers must restore a tenant service without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Configure a consistent loopback update source and sufficient eBGP multihop hop limit.
- Prepend the local AS on selected backup advertisements if permitted by upstream routing policy.
- Apply an explicit allowlist prefix policy outbound to the external BGP peer.
- Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship.
Explanation
Correct Answer
D:Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship. BGP neighbors must agree on configured peer AS identity and establish a TCP session.
Incorrect Answers
A: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 bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
B:Prepend the local AS on selected backup advertisements if permitted by upstream routing policy. This is a configuration change for a different root cause (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 bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
C: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 bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
Question 143
During a scheduled validation at the Savannah data center, a BGP session remains Idle or Active after the neighbor router's autonomous-system assignment changes. Engineers must restore a tenant service without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify the BGP session establishes and receives only authorized prefixes.
- Confirm internal BGP speakers consistently choose the preferred exit while backup remains available.
- Verify TCP 179 establishment using the loopback source and an Established BGP session.
- Verify client-learned routes are reflected to other clients with correct originator and cluster attributes.
Explanation
Correct Answer
A:Verify the BGP session establishes and receives only authorized prefixes. BGP neighbors must agree on configured peer AS identity and establish a TCP session.
Incorrect Answers
B:Confirm internal BGP speakers consistently choose the preferred exit while backup remains available. This is a validation for another mechanism (BGP outbound path local preference), where Within an AS, higher BGP local preference normally wins before AS-path length and MED. Here the evidence instead concerns bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
C:Verify TCP 179 establishment using the loopback source and an Established BGP session. This is a validation for another mechanism (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 bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
D:Verify client-learned routes are reflected to other clients with correct originator and cluster attributes. This is a validation for another mechanism (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
Question 144
During a scheduled validation at the Savannah data center, a BGP session remains Idle or Active after the neighbor router's autonomous-system assignment changes. Engineers must restore a tenant service without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Inspect TCP reachability and confirm the neighbor's configured remote-as matches its new AS.
- Inspect local preference distributed in iBGP along with route selection results.
- Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship.
- Mark the intended iBGP neighbors as route-reflector clients under the correct address family.
Explanation
Correct Answers
A:Inspect TCP reachability and confirm the neighbor's configured remote-as matches its new AS. BGP neighbors must agree on configured peer AS identity and establish a TCP session.
C:Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship. BGP neighbors must agree on configured peer AS identity and establish a TCP session.
Incorrect Answers
B:Inspect local preference distributed in iBGP along with route selection results. This is an investigation for a different failure condition (BGP outbound path local preference), where Within an AS, higher BGP local preference normally wins before AS-path length and MED. Here the evidence instead concerns bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
D:Mark the intended iBGP neighbors as route-reflector clients under the correct address family. This is a configuration change for a different root cause (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns bgp peer remote as: BGP neighbors must agree on configured peer AS identity and establish a TCP session.
Question 145
Following a production change at the Denver warehouse network, a new eBGP policy inadvertently exports internal-only subnets to an external provider. The incident is affecting management access; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
- Inspect the received BGP next-hop address and its reachability in the IGP or VRF.
- Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor.
- Inspect outbound prefix filters and route-map hit counts for unauthorized advertisements.
Explanation
Correct Answer
D:Inspect outbound prefix filters and route-map hit counts for unauthorized advertisements. BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Incorrect Answers
A:Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology. This is an investigation for a different failure condition (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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
B: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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Question 146
Following a production change at the Denver warehouse network, a new eBGP policy inadvertently exports internal-only subnets to an external provider. The incident is affecting management access; 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.
- Set a higher local preference for the preferred egress using a scoped inbound policy at the edge.
- Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship.
- Prepend the local AS on selected backup advertisements if permitted by upstream routing policy.
Explanation
Correct Answer
A:Apply an explicit allowlist prefix policy outbound to the external BGP peer. BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Incorrect Answers
B:Set a higher local preference for the preferred egress using a scoped inbound policy at the edge. This is a configuration change for a different root cause (BGP outbound path local preference), where Within an AS, higher BGP local preference normally wins before AS-path length and MED. Here the evidence instead concerns bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
D:Prepend the local AS on selected backup advertisements if permitted by upstream routing policy. This is a configuration change for a different root cause (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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Question 147
Following a production change at the Denver warehouse network, a new eBGP policy inadvertently exports internal-only subnets to an external provider. The incident is affecting management access; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Confirm the BGP next hop resolves and received routes become installable in the RIB.
- Verify only authorized aggregate prefixes are advertised and the private/internal prefixes are absent.
- Confirm internal BGP speakers consistently choose the preferred exit while backup remains available.
- Verify externally observed paths show the intended extra AS hops without losing prefix reachability.
Explanation
Correct Answer
B:Verify only authorized aggregate prefixes are advertised and the private/internal prefixes are absent. BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Incorrect Answers
A: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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
C:Confirm internal BGP speakers consistently choose the preferred exit while backup remains available. This is a validation for another mechanism (BGP outbound path local preference), where Within an AS, higher BGP local preference normally wins before AS-path length and MED. Here the evidence instead concerns bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Question 148
Following a production change at the Denver warehouse network, a new eBGP policy inadvertently exports internal-only subnets to an external provider. The incident is affecting management access; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Inspect outbound prefix filters and route-map hit counts for unauthorized advertisements.
- Inspect the received BGP next-hop address and its reachability in the IGP or VRF.
- Prepend the local AS on selected backup advertisements if permitted by upstream routing policy.
- Apply an explicit allowlist prefix policy outbound to the external BGP peer.
Explanation
Correct Answers
A:Inspect outbound prefix filters and route-map hit counts for unauthorized advertisements. BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
D:Apply an explicit allowlist prefix policy outbound to the external BGP peer. BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Incorrect Answers
B: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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
C:Prepend the local AS on selected backup advertisements if permitted by upstream routing policy. This is a configuration change for a different root cause (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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Question 149
During a scheduled validation at the Portland branch site, an EIGRP neighbor keeps resetting even though both interfaces share a valid subnet and multicast reaches the link. Engineers must restore a voice service path without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Compare the configured EIGRP autonomous-system numbers and active interface participation.
- Inspect outstanding EIGRP queries, stub boundaries, and slow or unreachable neighbors.
- Inspect logged EIGRP parameter mismatch messages and the K-values in neighbor hellos.
- Check feasibility, variance multiplier, traffic-share policy, and the actual metric ratio.
Explanation
Correct Answer
C:Inspect logged EIGRP parameter mismatch messages and the K-values in neighbor hellos. Traditional EIGRP neighbor adjacency requires compatible metric K-values.
Incorrect Answers
A: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 k-value mismatch: Traditional EIGRP neighbor adjacency requires compatible metric K-values.
B:Inspect outstanding EIGRP queries, stub boundaries, and slow or unreachable neighbors. This is an investigation for a different failure condition (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 k-value mismatch: Traditional EIGRP neighbor adjacency requires compatible metric K-values.
D:Check feasibility, variance multiplier, traffic-share policy, and the actual metric ratio. This is an investigation for a different failure condition (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 k-value mismatch: Traditional EIGRP neighbor adjacency requires compatible metric K-values.
Question 150
During a scheduled validation at the Portland branch site, an EIGRP neighbor keeps resetting even though both interfaces share a valid subnet and multicast reaches the link. Engineers must restore a voice service path without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link.
- Make metric-weight K-values consistent on both neighbors without changing unrelated routing policy.
- Align the EIGRP authentication key chain and active key lifetime across the peers.
- Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes.
Explanation
Correct Answer
B:Make metric-weight K-values consistent on both neighbors without changing unrelated routing policy. Traditional EIGRP neighbor adjacency requires compatible metric K-values.
Incorrect Answers
A: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 k-value mismatch: Traditional EIGRP neighbor adjacency requires compatible metric K-values.
C:Align the EIGRP authentication key chain and active key lifetime across the peers. This is a configuration change for a different root cause (EIGRP neighbor authentication), where Routing authentication mismatches prevent EIGRP neighbors from exchanging trusted updates. Here the evidence instead concerns eigrp k-value mismatch: Traditional EIGRP neighbor adjacency requires compatible metric K-values.
D: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 k-value mismatch: Traditional EIGRP neighbor adjacency requires compatible metric K-values.