Cisco 300-410 Practice Test 21
Question 200
During a scheduled validation at the Chandler warehouse network, iPv6 clients receive DNS options from an unauthorized DHCPv6 responder on a user access switch port. Engineers must restore an operations uplink without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the previous server command set if the change unintentionally expands administrator access.
- Restore the former ACL order if the specific permit unintentionally opens additional sources.
- Revert transport restriction only under controlled emergency access if SSH setup breaks all management.
- Restore a legitimately trusted uplink role if authorized DHCPv6 replies stop reaching clients.
Explanation
Correct Answer
D:Restore a legitimately trusted uplink role if authorized DHCPv6 replies stop reaching clients. DHCPv6 Guard helps prevent rogue DHCPv6 server messages from untrusted switch ports.
Incorrect Answers
A:Restore the previous server command set if the change unintentionally expands administrator access. This is a rollback for a different component (TACACS+ command authorization), where TACACS+ can authorize individual CLI commands separately from successful login authentication. Here the evidence instead concerns dhcpv6 server guard: DHCPv6 Guard helps prevent rogue DHCPv6 server messages from untrusted switch ports.
B: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 dhcpv6 server guard: DHCPv6 Guard helps prevent rogue DHCPv6 server messages from untrusted switch ports.
C:Revert transport restriction only under controlled emergency access if SSH setup breaks all management. This is a rollback for a different component (Router SSH hardened management), where SSH provides encrypted remote CLI transport; Telnet sends sessions without encryption. Here the evidence instead concerns dhcpv6 server guard: DHCPv6 Guard helps prevent rogue DHCPv6 server messages from untrusted switch ports.
Question 201
Following a production change at the Madison distribution campus, a routed link loses forwarding while the physical interface remains up; the routing protocol withdraws the failed adjacency too slowly. The incident is affecting a monitored campus segment; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Check BFD session state, neighbor association, timers, and whether both peers support it.
- Inspect logged EIGRP parameter mismatch messages and the K-values in neighbor hellos.
- Compare OSPF stub flags and area type on every router participating in the area.
- Trace route tags and redistribution points to identify reintroduction of the same route.
Explanation
Correct Answer
A:Check BFD session state, neighbor association, timers, and whether both peers support it. Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
Incorrect Answers
B:Inspect logged EIGRP parameter mismatch messages and the K-values in neighbor hellos. This is an investigation for a different failure condition (EIGRP K-value mismatch), where Traditional EIGRP neighbor adjacency requires compatible metric K-values. Here the evidence instead concerns bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
C:Compare OSPF stub flags and area type on every router participating in the area. This is an investigation for a different failure condition (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
D:Trace route tags and redistribution points to identify reintroduction of the same route. This is an investigation for a different failure condition (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
Question 202
Following a production change at the Madison distribution campus, a routed link loses forwarding while the physical interface remains up; the routing protocol withdraws the failed adjacency too slowly. The incident is affecting a monitored campus segment; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Set a higher local preference for the preferred egress using a scoped inbound policy at the edge.
- Enable compatible BFD detection for the routing adjacency with realistic interval and multiplier settings.
- Correct the BGP neighbor remote-as and related peer policy for the intended eBGP or iBGP relationship.
- Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes.
Explanation
Correct Answer
B:Enable compatible BFD detection for the routing adjacency with realistic interval and multiplier settings. Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
Incorrect Answers
A: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 bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
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 bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
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 bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
Question 203
Following a production change at the Madison distribution campus, a routed link loses forwarding while the physical interface remains up; the routing protocol withdraws the failed adjacency too slowly. The incident is affecting a monitored campus segment; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Simulate forwarding loss and confirm BFD signals the routing neighbor quickly without flapping.
- Confirm secure neighbors form and authentication-related logs stop appearing.
- Verify the external EIGRP route and plausible composite metric appear in neighbor tables.
- Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation.
Explanation
Correct Answer
A:Simulate forwarding loss and confirm BFD signals the routing neighbor quickly without flapping. Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
Incorrect Answers
B:Confirm secure neighbors form and authentication-related logs stop appearing. This is a validation for another mechanism (EIGRP neighbor authentication), where Routing authentication mismatches prevent EIGRP neighbors from exchanging trusted updates. Here the evidence instead concerns bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
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 bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
D:Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation. This is a validation for another mechanism (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
Question 204
Following a production change at the Madison distribution campus, a routed link loses forwarding while the physical interface remains up; the routing protocol withdraws the failed adjacency too slowly. The incident is affecting a monitored campus segment; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Enable compatible BFD detection for the routing adjacency with realistic interval and multiplier settings.
- Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub.
- Check BFD session state, neighbor association, timers, and whether both peers support it.
- Assign a unique stable router ID to the conflicting router and restart the process in a controlled window if necessary.
Explanation
Correct Answers
A:Enable compatible BFD detection for the routing adjacency with realistic interval and multiplier settings. Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
C:Check BFD session state, neighbor association, timers, and whether both peers support it. Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
Incorrect Answers
B: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 bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
D:Assign a unique stable router ID to the conflicting router and restart the process in a controlled window if necessary. This is a configuration change for a different root cause (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns bfd fast-failure detection: Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers.
Question 205
Following a production change at the Austin hospital campus, wireless clients report high application latency at one campus, but switch interfaces show no sustained errors. The incident is affecting management access; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Inspect the authoritative engine ID and how user keys are localized to it.
- Run the supported Cisco Catalyst Center Assurance path trace and examine hop-by-hop forwarding evidence.
- Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals.
- Check RA managed-config flag, DHCPv6 relay destination, and routed reachability to the service.
Explanation
Correct Answer
C:Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Incorrect Answers
A:Inspect the authoritative engine ID and how user keys are localized to it. This is an investigation for a different failure condition (SNMPv3 engine identity), where SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
B: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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
D:Check RA managed-config flag, DHCPv6 relay destination, and routed reachability to the service. This is an investigation for a different failure condition (DHCPv6 relay), where DHCPv6 relaying transports client messages to a remote server; Router Advertisements still convey default-router details. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Question 206
Following a production change at the Austin hospital campus, wireless clients report high application latency at one campus, but switch interfaces show no sustained errors. 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?
- Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites.
- Correct the VTY AAA binding for remote access while preserving console emergency management.
- Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route.
- Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue.
Explanation
Correct Answer
D:Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Incorrect Answers
A:Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites. This is a configuration change for a different root cause (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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
B:Correct the VTY AAA binding for remote access while preserving console emergency management. This is a configuration change for a different root cause (Console versus VTY authentication), where Console and VTY lines can use different authentication and authorization methods. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
C:Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route. This is a configuration change for a different root cause (IP SLA object tracking failover), where IP SLA probes detect beyond-interface reachability, and object tracking can control static route installation. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Question 207
Following a production change at the Austin hospital campus, wireless clients report high application latency at one campus, but switch interfaces show no sustained errors. The incident is affecting management access; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Repeat path trace and an application-level test to confirm the failing segment is corrected.
- Flap a test interface and confirm an event notification reaches the NMS promptly.
- Confirm client health improves for the affected population rather than relying only on global device uptime.
- Confirm successful SNMPv3 authentication to the new engine ID after credential repair.
Explanation
Correct Answer
C:Confirm client health improves for the affected population rather than relying only on global device uptime. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Incorrect Answers
A:Repeat path trace and an application-level test to confirm the failing segment is corrected. This is a validation for another mechanism (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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
B:Flap a test interface and confirm an event notification reaches the NMS promptly. This is a validation for another mechanism (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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
D:Confirm successful SNMPv3 authentication to the new engine ID after credential repair. This is a validation for another mechanism (SNMPv3 engine identity), where SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Question 208
Following a production change at the Austin hospital campus, wireless clients report high application latency at one campus, but switch interfaces show no sustained errors. 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?
- Correct the exporter's receiver, source, and transport settings without changing the flow record unnecessarily.
- Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals.
- Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue.
- Run the supported Cisco Catalyst Center Assurance path trace and examine hop-by-hop forwarding evidence.
Explanation
Correct Answers
B:Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
C:Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Incorrect Answers
A:Correct the exporter's receiver, source, and transport settings without changing the flow record unnecessarily. This is a configuration change for a different root cause (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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Question 209
During a scheduled validation at the Roswell branch site, a new eBGP policy inadvertently exports internal-only subnets to an external provider. Engineers must restore a business-critical application without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect outbound prefix filters and route-map hit counts for unauthorized advertisements.
- Check BFD session state, neighbor association, timers, and whether both peers support it.
- Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27.
- Inspect route-map sequence order, each match condition, and hit counts against the missing prefixes.
Explanation
Correct Answer
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.
Incorrect Answers
B:Check BFD session state, neighbor association, timers, and whether both peers support it. This is an investigation for a different failure condition (BFD fast-failure detection), where Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers. 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: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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
D:Inspect route-map sequence order, each match condition, and hit counts against the missing prefixes. This is an investigation for a different failure condition (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 bgp prefix leak prevention: BGP outbound prefix policies are the control point for which routes are advertised to an external neighbor.
Question 210
During a scheduled validation at the Roswell branch site, a new eBGP policy inadvertently exports internal-only subnets to an external provider. Engineers must restore a business-critical application without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Apply an explicit allowlist prefix policy outbound to the external BGP peer.
- Set a higher local preference for the preferred egress using a scoped inbound policy at the edge.
- 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.
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: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 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.