Cisco 300-410 Practice Test 40
Question 390
Following a production change at the Bend distribution campus, a previously working IPv6 host is blocked by first-hop security after moving between access ports. The incident is affecting remote-site route stability; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Refresh supported binding learning or correct static bindings before enforcing dependent guard policies.
- Configure a controlled local fallback method for server unavailability on the intended lines.
- Rate-limit management traffic in a dedicated class sized for approved operations rather than the default drop class.
- Apply an appropriately scoped IPv6 access list in the correct direction without relying on IPv4 ACL behavior.
Explanation
Correct Answer
A:Refresh supported binding learning or correct static bindings before enforcing dependent guard policies. Several IPv6 first-hop security features rely on accurate host address and port bindings.
Incorrect Answers
B:Configure a controlled local fallback method for server unavailability on the intended lines. This is a configuration change for a different root cause (RADIUS AAA fallback), where AAA method lists try subsequent methods for server errors, not necessarily for a definitive authentication rejection. Here the evidence instead concerns ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
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 ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
D:Apply an appropriately scoped IPv6 access list in the correct direction without relying on IPv4 ACL behavior. This is a configuration change for a different root cause (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 ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
Question 391
Following a production change at the Bend distribution campus, a previously working IPv6 host is blocked by first-hop security after moving between access ports. The incident is affecting remote-site route stability; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Confirm the current binding exists and legitimate IPv6 packets pass the guard.
- Simulate RADIUS unreachability and confirm designated local break-glass login succeeds without bypassing normal rejects.
- Send test RAs from both authorized and unauthorized ports and verify only the authorized default gateway is learned.
- Confirm a controlled test login uses local authentication only under the designed fallback condition.
Explanation
Correct Answer
A:Confirm the current binding exists and legitimate IPv6 packets pass the guard. Several IPv6 first-hop security features rely on accurate host address and port bindings.
Incorrect Answers
B:Simulate RADIUS unreachability and confirm designated local break-glass login succeeds without bypassing normal rejects. This is a validation for another mechanism (RADIUS AAA fallback), where AAA method lists try subsequent methods for server errors, not necessarily for a definitive authentication rejection. Here the evidence instead concerns ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
C:Send test RAs from both authorized and unauthorized ports and verify only the authorized default gateway is learned. This is a validation for another mechanism (IPv6 Router Advertisement Guard), where RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments. Here the evidence instead concerns ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
D:Confirm a controlled test login uses local authentication only under the designed fallback condition. This is a validation for another mechanism (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 ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
Question 392
Following a production change at the Bend distribution campus, a previously working IPv6 host is blocked by first-hop security after moving between access ports. The incident is affecting remote-site route stability; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Restore the old learning configuration if the change pollutes binding state or affects other ports.
- Restore the previous source-validation mode if spoofed traffic unexpectedly passes.
- Remove the new exception if it allows unauthorized management probes.
- Remove the maintenance permit if clocks or schedules cannot be trusted.
Explanation
Correct Answer
A:Restore the old learning configuration if the change pollutes binding state or affects other ports. Several IPv6 first-hop security features rely on accurate host address and port bindings.
Incorrect Answers
B:Restore the previous source-validation mode if spoofed traffic unexpectedly passes. This is a rollback for a different component (Strict uRPF asymmetric routing), where Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress. Here the evidence instead concerns ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
C: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 ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
D:Remove the maintenance permit if clocks or schedules cannot be trusted. This is a rollback for a different component (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 ipv6 address binding table: Several IPv6 first-hop security features rely on accurate host address and port bindings.
Question 393
During a scheduled validation at the Austin distribution campus, routers produce correct syslog messages but timestamps differ by several minutes, making incident correlation unreliable. Engineers must restore remote-site route stability without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect NTP synchronization, time zone representation, and logging timestamp precision.
- Inspect the authoritative engine ID and how user keys are localized to it.
- Inspect flow record, flow monitor, and whether the monitor is attached in the intended interface direction.
- Inspect IP SLA UDP-jitter measurements for one-way or round-trip delay variation and loss.
Explanation
Correct Answer
A:Inspect NTP synchronization, time zone representation, and logging timestamp precision. Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
Incorrect Answers
B: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 time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
C:Inspect flow record, flow monitor, and whether the monitor is attached in the intended interface direction. This is an investigation for a different failure condition (Flexible NetFlow monitor attachment), where Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
D:Inspect IP SLA UDP-jitter measurements for one-way or round-trip delay variation and loss. This is an investigation for a different failure condition (IP SLA UDP jitter monitoring), where Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
Question 394
During a scheduled validation at the Austin distribution campus, routers produce correct syslog messages but timestamps differ by several minutes, making incident correlation unreliable. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Set the intended reachable source-interface and VRF context for remote syslog traffic.
- Repair synchronization to approved NTP sources and use consistent timestamp settings.
- Attach the compatible Flexible NetFlow monitor to the correct traffic-facing interface and direction.
- Configure the correct ip helper-address on the client-facing routed interface.
Explanation
Correct Answer
B:Repair synchronization to approved NTP sources and use consistent timestamp settings. Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
Incorrect Answers
A:Set the intended reachable source-interface and VRF context for remote syslog traffic. This is a configuration change for a different root cause (Syslog source interface), where Syslog transport can fail when its source or VRF does not match collector reachability and access rules. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
C:Attach the compatible Flexible NetFlow monitor to the correct traffic-facing interface and direction. This is a configuration change for a different root cause (Flexible NetFlow monitor attachment), where Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
D:Configure the correct ip helper-address on the client-facing routed interface. This is a configuration change for a different root cause (IPv4 DHCP relay), where IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
Question 395
During a scheduled validation at the Austin distribution campus, routers produce correct syslog messages but timestamps differ by several minutes, making incident correlation unreliable. Engineers must restore remote-site route stability without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Compare event timestamps across devices after a known simultaneous test event.
- Repeat path trace and an application-level test to confirm the failing segment is corrected.
- Verify the SSH service accepts an encrypted login from the management network.
- Capture a relay-generated request and verify the server replies with a lease for the client's subnet.
Explanation
Correct Answer
A:Compare event timestamps across devices after a known simultaneous test event. Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
Incorrect Answers
B: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 time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
C:Verify the SSH service accepts an encrypted login from the management network. This is a validation for another mechanism (SSH prerequisites), where A Cisco IOS SSH server needs valid crypto key material and compatible session settings. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
D:Capture a relay-generated request and verify the server replies with a lease for the client's subnet. This is a validation for another mechanism (IPv4 DHCP relay), where IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
Question 396
During a scheduled validation at the Austin distribution campus, routers produce correct syslog messages but timestamps differ by several minutes, making incident correlation unreliable. 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 approved NTP peers if a replacement time source produces unstable clock shifts.
- Disable the newly enabled SCP service if authorization permits unapproved file access.
- Restore the VTY method list if remote access becomes unusable after the change.
- Restore earlier remote logging limits if the new level floods the collector.
Explanation
Correct Answer
A:Restore approved NTP peers if a replacement time source produces unstable clock shifts. Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
Incorrect Answers
B:Disable the newly enabled SCP service if authorization permits unapproved file access. This is a rollback for a different component (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
C:Restore the VTY method list if remote access becomes unusable after the change. This is a rollback for a different component (Console versus VTY authentication), where Console and VTY lines can use different authentication and authorization methods. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
D:Restore earlier remote logging limits if the new level floods the collector. This is a rollback for a different component (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns time synchronization for logs: Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps.
Question 397
During a scheduled validation at the Norman remote operations location, a classless /27 connected subnet fails to appear as an external OSPF route after a broad redistribution change. Engineers must restore an operations uplink without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Check whether the EIGRP redistribution policy supplies a usable seed metric.
- Compare summary reachability with the actual set of component subnets and the summary discard route.
- Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27.
- Trace route tags and redistribution points to identify reintroduction of the same route.
Explanation
Correct Answer
C:Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27. Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Incorrect Answers
A:Check whether the EIGRP redistribution policy supplies a usable seed metric. This is an investigation for a different failure condition (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
B:Compare summary reachability with the actual set of component subnets and the summary discard route. This is an investigation for a different failure condition (Summary route black hole), where An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Question 398
During a scheduled validation at the Norman remote operations location, a classless /27 connected subnet fails to appear as an external OSPF route after a broad redistribution change. Engineers must restore an operations uplink without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- 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.
- Tag routes on first redistribution and deny that tag when importing them back into the source domain.
- Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage.
Explanation
Correct Answer
B:Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything. Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Incorrect Answers
A: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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
C:Tag routes on first redistribution and deny that tag when importing them back into the source domain. This is a configuration change for a different root cause (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
D:Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage. This is a configuration change for a different root cause (Summary route black hole), where An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Question 399
During a scheduled validation at the Norman remote operations location, a classless /27 connected subnet fails to appear as an external OSPF route after a broad redistribution change. Engineers must restore an operations uplink without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears.
- Verify reimported tagged routes are blocked while fresh authorized external prefixes remain visible.
- Confirm a Type 5 or appropriate Type 7 external LSA represents only the authorized prefix.
- Verify the external EIGRP route and plausible composite metric appear in neighbor tables.
Explanation
Correct Answer
C:Confirm a Type 5 or appropriate Type 7 external LSA represents only the authorized prefix. Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Incorrect Answers
A:Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears. This is a validation for another mechanism (Administrative distance), where For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
B: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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
D:Verify the external EIGRP route and plausible composite metric appear in neighbor tables. This is a validation for another mechanism (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Question 400
During a scheduled validation at the Norman remote operations location, a classless /27 connected subnet fails to appear as an external OSPF route after a broad redistribution change. 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 ordered route-map clauses if the permitted set becomes too broad.
- Restore prior filtering and tag actions if production reaches previously excluded routes.
- Restore the previously recorded distances and route source if the intended failover changes.
- Undo the new redistribution scope if unexpected external routes appear.
Explanation
Correct Answer
D:Undo the new redistribution scope if unexpected external routes appear. Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
Incorrect Answers
A:Restore the previous ordered route-map clauses if the permitted set becomes too broad. This is a rollback for a different component (Route-map permit sequence), where Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action. Here the evidence instead concerns ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.
C: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 ospf classless redistribution: Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage.